This September was quite productive, as i had 4 test automation related articles published, which i recommend reading:
Enjoy.
We are quite familiar with the concept of randomly failing automated tests. Those are the tests that even though there is no change in the feature they are testing, they either fail randomly at the same step, or they fail at random steps. Handling the results of such tests can be tricky, and some teams choose to simply retry a test if it failed. But is that the best option? Here are my thoughts. Continue reading Using Retries in tests can hide the bugs
As you have probably seen, my new course on JUnit 5 is now available at Test Automation University. It’s an introduction to all the amazing features of this framework that you can use in your automated tests, with, of course, plenty of examples.
Continue reading About my JUnit 5 course
Read all about how to configure your test environment specific data in property files with Spring, to help run your automated TestNG and JUnit tests on any test environment you need: https://blog.testproject.io/2021/02/09/using-spring-to-switch-environments-in-automated-tests/. Enjoy.
If in your tests you need to generate date values representing, let’s say, today’s date, or yesterday’s, or one year from today, or the last day of the current month, this post will help you do just that. Using Java’s LocalDate, you will be able to generate the date (meaning year, month, day) your tests require easily. Continue reading Generating useful date values for testing purposes
In your tests you might encounter specialized popups, which are generated via Javascript, and which are called ‘user prompts’. These are very basic in functionality, and they come in three variants: an ‘alert’ which only displays an informational message and an ‘OK’ button; a ‘confirm’ which displays an informational message, together with an ‘OK’ and ‘Cancel’ button; a ‘prompt’ which displays an informational message, possibly an input field for typing into, and an ‘OK’ and ‘Cancel’ button. Continue reading Working with user prompts in Selenium
When testing requires you to work with multiple open windows or tabs, Selenium is here to help. A new window or tab usually opens when a user clicks on a button or link which triggers the new page that loads to be open in a new window or tab. Whether it is a window or tab that opens depends on the browser you are using. No matter whether you have a new tab or a new window that opens, the methods presented in this post for working with them behave exactly the same. They make no distinctions in regards to what was open (a tab or window). Continue reading Working with windows/tabs in Selenium
So, now that you are an expert in writing CSS selectors to identify your WebElements (possible because of my older webinar on this topic), you want to write some new tests. You are inspecting the page you will test, identifying what WebElements you will need, and start writing the selectors. Once you have them, and the test contains all the necessary interactions with those WebElements, you run the test, confident it will pass. But instead, surprise. You get a NoSuchElementException. You double, triple, quadruple check the page, and by the looks of it, the selector is correctly written. And that is true. However, when you inspect the page further, you notice that your element is actually contained within an <iframe> tag (<iframe>…</iframe>). Continue reading Iframes, switchTo() and default content with Selenium
Read the article i wrote for the TestProject blog on general tips for why and how we can achieve clean code in our automation: https://blog.testproject.io/2020/04/22/clean-code-in-tests-what-why-and-how/
In case you haven’t already, read the article i wrote for QALead on how i prepare and test for releases: https://theqalead.com/topics/release-management-how-i-prepare-and-test-for-my-releases/. Enjoy.
imalittletester 