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!
Writing good bug reports
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.
The Little Tester – Stories in Testing #28
Better Test Code Principles: Use proper naming, for everything
Naming is one of those underrated things when it comes to test automation code. Many times, when you look at variable or even test method names, they are not very suggestive and you have a hard time figuring out what their purpose is. In this post you will find a few reasons why it is… Read More
The Automated Regression Suite. Part 3 of 3. How to run the suite
Once you have a regression suite set up, you will need to run it. When you have a smaller number of tests that need to be run on a specified day, that won’t be a problem, and the tests will successfully finish running within the allocated time period. However, as the suite becomes larger and… Read More
The Automated Regression Suite. Part 2 of 3. When to run the tests.
Once you have your automated regression suite in place, you can create a scheduler to run them periodically, without any manual intervention. Mostly you will use Jenkins jobs (or some similar CI tool) to trigger them and have them running on an environment of your choice. Just because they are called “regression tests” it does… Read More
The Automated Regression Suite. Part 1 of 3. When to create the tests for regression
What do I mean by “automated regression testing”? I am not one for debating for hours what this means, so let me give you my interpretation (not definition), so that we are on the same page: whenever you are performing a new release, you need to make sure the features you released some time ago… Read More
Refactoring is allowed
Writing automated tests means writing code. It means going through processes that regular code goes through. Like code review, and refactoring. I see a lot of hesitation when it comes to refactoring one’s own code, possibly because we feel that if our code needs correction, we did a crappy job writing it the first time.… Read More
A bug is still a bug
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?
The tester and the code review
Code review, although very important and frequent in the software development world, is not as frequent in the automation testing world. Normally, it would be part of the whole process: someone writes code, reviews it, makes it available to the rest of the team, they review it, and if changes are needed they will be… Read More
