Freddie Frustrated

From Test Automation Patterns
Revision as of 08:35, 9 July 2018 by Dorothy (talk | contribs) (Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 16px"> When building the automation, things seemed to go well. Freddie thought about the te...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
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.



Use the wiki to identify Freddie's main Issue(s) and the Pattern(s) that would be most appropriate for him. (Hint: try entering "tool" in the search box.)



Back to Exercises