Most of the times your automation code project travels around, from machine to machine, to where the tests inside it need to run. Sometimes it might be your colleague’s machine, who also wants to run/update/add tests, but other times it will be some CI/CD entities, like physical or virtual machines, containers, and so on.
Continue reading Artifacts to store in your test automation project
I will start with an example: say you have a page table with 2 columns. You want to check, in your UI testing, that the values in the second column are the expected ones. By looking at the table you see that the first 2 and the last 5 values are the same. You have to iterate the table values to compare to the expected ones, but what is the simplest way to do this? You could use 2 for loops to check for those identical values, but you would just be repeating the code inside those for loops, as you would be writing the exact same checks. Even if it’s calling a separate method, it would still be a code repeat. Let me exemplify solving this situation using ‘chained’ for loops. Continue reading Joining multiple for loops in Python with ‘chain’ for repeating the same check for multiple groups of indexes
Automated tests are supposed to help validate that the product under test is working as expected. For that, a key ingredient is required in your automation: the actual testing. Just as, when you are performing a test case yourself, you are visually inspecting that the expected behavior occurred, so does your automation need to have verification in place. And that verification needs to be implemented by you. Here are some thoughts on this.
Continue reading Adding testing to your test automation
Writing bug reports is a frequent task in the tester’s work. Here are my tips on how to write good and clear bug reports that properly underline: what issue can be observed, what behavior should have been observed instead, and how to reproduce it.
Continue reading Writing good bug reports
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.
Continue reading 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 appears in the system under test, whose root cause is not very obvious. I also encouraged testers to participate in the process of finding the root cause of this bug, by providing a few tips and techniques that can be used. Continue reading A matrix for when a bug only reproduces in one environment
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? Continue reading A bug is still a bug
imalittletester 