The tester’s daily dilemma: my automated tests fail because of the test environment. What can i do?

Automated tests. They are there, and they need to be run. On a test environment. By you. You wrote them in a way that they should be reliable, when the features under test work as designed. But each day you run the same tests on the same test environment, and they fail. Not because the… Read More

Extracting substrings with StringUtils from the Apache library

Following on from some of my earlier posts, where I described some of the useful utils from the apache.commons.lang3 library (like that very nice RandomStringUtils class), this time I will focus a bit on the StringUtils class.  As the name suggests, it provides developers and testers an easy way to deal with certain String related… Read More

SoftAssert – don’t make your test fail on the first assertion failure

When you have more than one assertion in your test, you might want one of two things: Have your tests fail once the first assertion failure is encountered. Have all your assertions run, no matter if they have passed or failed. Of course, after they are run, if there are failures, you want the test… Read More

How to identify the test scenarios you have to automate

Suppose you are starting work on a new piece of software that you will need to write automated tests for. Your goal is to cover the most relevant test scenarios that apply to the feature , without missing or forgetting one. Below are a few steps (guidelines) to help you achieve identifying those required scenarios… Read More