Testing. With Java, Selenium, TestNG, Maven, Spring, IntelliJ and friends.
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.
This year, at several conferences, i did a talk on troubleshooting tips and techniques. One slide in particular seemed to be very much of interest for the attendees, so i decided to elaborate on it with a blog post. In the talk, i was describing what to try to look for when an undesired behavior… Read More
Do you know this situation, when you implemented some automated tests based on a requirement, but a test has been failing for ages because a bug in the implementation was never fixed?
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
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
