Owen Optimistic

From Test Automation Patterns
Jump to: navigation, search
Owen has recently been put in charge of the test group. He was formerly a development manager and is very keen to bring the test team along and get test automation going, as the testing has been mainly manual. So the first thing he did was to call the team together and announce that he had authorised the acquisition of a test tool, which he had heard glowing reports about from some friends in another company. He assured the team that he was 100% behind them in introducing the new tool, and had generously given them 3 months to “get up to speed”.


However, when the 3 months were up, Owen was very disappointed and frustrated. He had thought that by now all of the manual tests would be running automatically overnight and for every build, but it seems that there are still lots of manual tests that haven’t been automated yet. Even worse, the team are already complaining about software changes that are “breaking” the automation - he is sure this shouldn’t happen. But the worst thing of all is that he has just been told that a bug was found in something that had been tested by automated tests! How can this be? He feels that he has already invested time and money into automation but it hasn’t given him the benefits he was convinced would be there by now.

1) Look at the Test Automation Issues Mind Map or Test Automation Issues Mind map with clickable links. Which issue(s) would best represent the problem(s) Owen is currently facing?
2) Using the Diagnostic, what are the issues that best describe the problems that Owen is facing?



Back to Exercises