This is part four of the mini series "Magic principles in test automation". Forcing has multiple meaning in magic as well as software development - in this article I will try to explain both.
There are different ways to monitor a system to ensure its performance, stability, reliability and resilience. Along with the "usual suspects", we also use end to end tests for this purpose.
Today I had a discussion with Michael Bolton on Twitter about software releases. As I felt that my point did not come across correctly in the condensed tweet format, I decided to write an article instead.
This is a new entry in the series "Magic principles in test automation". Today, I will cover the topic of repetition. To read the last one, please check out Magic principles in test automation: Misdirection.
Our current test automation setup for end to end testing is using Maven for preparing the test data, running our test scenarios and creating a test report. Recently, I wanted to refactor the way we use Maven's lifecycles and found a surprisingly easy way to do just that.