Automated tests are used to validate features in development environments but also in production. Whereas the classic approach of keeping all tests in the same code project is the most popular, it is not the best idea (and by code project i mean for example a Maven project). Continue reading Better Test Code Principles: #4 Keep your production tests separate from your dev environment ones
When i look at a test class, what i want to see is clean code. What i mean by that is, well a few things, but the most important one: i want the test class to hold the code for the tests, not the code for everything but the kitchen sink.
When we write tests we have a lot of data to prepare for them. Whether this is the ‘expected’ or the ‘actual’ data used in the tests, or some auxiliary code that we need, there always is some processing that needs to be done, apart from the actual asserts that a test should do. What the test class should contain is only the checking / asserting part, while having specialized classes generate all the data that is required in the test. A test class should only check the actual data against the expected data. This is the separation of concerns principle. Continue reading Write clean code for your tests by using the separation of concerns principle
So this year’s edition of RTC (Romania Testing Conference), held in Cluj-Napoca, has just concluded, and as a participant and speaker i had a great time attending the event. Therefore, here are some impressions and takeaways from a full day of presentations and meeting some really lovely folks. Continue reading Impressions after the Romania Testing Conference 2016
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 (a sort of ‘how i do it and it works for me’ guide). Continue reading How to identify the test scenarios you have to automate
Idea just released a major update to their IntelliJ IDE, which contains loads of fixes, enhancements and new features. The UI improvements on the testing side are quite interesting and useful (as they specify on their blog, this part has been completed rewritten, resulting in a much smoother and better working UI). Some examples of the interesting features this upgrade brings are presented below (for running TestNG tests): Continue reading IntelliJ 15 gets released with improved UI for testing