In this second post of the ‘browser unaware Selenium tests’ series, i will show what the methods that start Chrome and Firefox look like, based on the selected OSs from the previous post.
Browser unaware Selenium tests. STEP 1: Identify OSs on which to run tests + choose browsers to support
In this blog post series, i want to show how i normally set up my browsers and my Selenium code, in order to enable writing ‘cross-OS’, ‘cross-browser’, ‘browser-unaware’ tests. What this means: my tests can run on any OS i set up seamlessly; each test can be run on multiple browsers seamlessly; the tests do… Read More
As a tester i should not find THESE bugs in the system
I’m not saying this JUST because creating a new entry in Jira for the bug takes a lot of time (due to making sure you typed the correct steps, in the correct order, grabbing screenshots, downloading logs, and so on). And no, i’m not referring to not finding any bug at all. But instead…
Why using branches is good for your tests
Branches are beautiful, on trees. Branches in the code are not what many testers like to work with. The whole branching process appears to be very cumbersome: creating the branch, keeping it up to date with the main branch, deleting it once the work is done, these all seem to take a lot of time… Read More
My IntelliJ course is now available
Have you heard? My course “IntelliJ for Test Automation Engineers” is now available for free on Test Automation University: https://testautomationu.applitools.com/intellij/. It is meant for testers who want to learn how to use this IDE, and it covers concepts from installation, setup, to creating and running test, to performing static code analysis. Enjoy!
Bugs and reproducing them
Whenever a new bug is found, the tester will need to create a defect in the defect tracking system they work with. This defect needs to contain clear steps to reproduce the problem, so that developers can identify the root cause of the issue. Here are some tips regarding bugs and reproducing them.
Java naming conventions revisited
Let’s go way back to basics for a second: Java naming conventions. I wrote a post a while back regarding how to compose the name for various Java items, like classes or variables. In this post i want to emphasize the naming conventions, which relate to the use of upper/lower/camel cases when naming things.
Using HashMaps in automated tests
HashMaps are one of those Java concepts that can be very useful in automation testing, but are not widely used, because they seem to be too complicated. A HashMap is nothing more than a collection of key/value pairs, where you can store test related data to access later in the tests. In this post i… Read More
Removing duplicates from a List
When working with lists, sometimes you only want them to contain distinct elements. There are two options to create lists without duplicates: either to not add these from the start, or, if that is not possible or too difficult, to remove the duplicates from the list later on. Let’s see how you can do both… Read More
Checkout the first article i wrote for TestProject’s blog
Checkout the first article i wrote for TestProject’s blog: https://blog.testproject.io/2019/10/24/using-java-objects-for-comparing-api-db-test-data/. It is about how to easily compare test data gathered from an API to the test data gathered from the DB, using Java Objects.
