Solution to Freddie Frustrated

From Test Automation Patterns
Jump to navigation Jump to search

When building the automation, things seemed to go well. Freddie thought about the test architecture and designing the tests for ease of maintenance, and at first, the tests ran smoothly, giving them useful information about the system they were testing.

But after a while, it seems to be taking more and more time to find out what’s going on when automated tests fail. At first, just a few tests began to fail in the overnight run, but when they were re-run in the morning, they would pass. This is happening more often now. Since the automation is seen as successful and useful, more and more people are using automated tests, but sometimes, they leave the test data in a state that isn’t what someone else’s test was expecting, so their tests fail, even though they should have passed. When the developers change the names of some objects, lots of tests fail even though the system still works fine.

People are complaining that the automation is no longer fit for purpose, because there are so many problems with failing tests, and they are losing faith in all the the automation.

1) Go to Test Automation Issues Mind Map or Test Automation Issues Mind map with clickable links. Look through the Issue names and see if one stands out as Freddie's main problem. See which patterns would solve it

2) Go to Test Automation Patterns Mind Map or Test Automation Patterns Mind Map with clickable links. Look through the Pattern names and see which stand out as possible solutions for Freddie.

3) Go to the Diagnostic. Answer the questions on Freddie's behalf and see if you find the same issues and patterns.


It is important to address the problem of flaky tests, as this can undermine everyone’s confidence in all of the results from automated tests.