Difference between revisions of "Solution to Owen Optimistic"
| (2 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
<span style="font-size: 16px"><br /> <br />Solutions:<br /> | <span style="font-size: 16px"><br /> <br />Solutions:<br /> | ||
1) There are a couple of possible issues in Owen’s case. | 1) There are a couple of possible issues in Owen’s case. | ||
| − | + | * [[HIGH ROI EXPECTATIONS]] (Management Issue) may be the most appropriate issue for Owen, since he clearly expected to get more benefits for his investment by now. | |
| − | + | * [[UNREALISTIC EXPECTATIONS]] (Management Issue) may also be a relevant issue, since Owen’s expectations were not realistic. | |
| − | 2) Using the Diagnostic | + | 2) Using the Diagnostic Owen could select: |
| − | + | * [[NO PREVIOUS TEST AUTOMATION]] (Management Issue) - there is lots of good advice here that Owen would have benefitted from looking at earlier! | |
| − | + | * Assuming that Owen wants to [[Improve or revive test automation]], the most appropriate heading is [[Management expectations for automation not met]]. Here we find both of the issues above ([[UNREALISTIC EXPECTATIONS]] and [[HIGH ROI EXPECTATIONS]]). Both of these are relevant and contain useful advice for Owen. | |
<br />For example, let’s look at [[UNREALISTIC EXPECTATIONS]]: | <br />For example, let’s look at [[UNREALISTIC EXPECTATIONS]]: | ||
* The list of expectations matches a lot of Owen’s ideas, so this is probably the most appropriate issue for him. | * The list of expectations matches a lot of Owen’s ideas, so this is probably the most appropriate issue for him. | ||
(Note that the next step would be to look at the recommended Patterns, but that is not part of this exercise.) | (Note that the next step would be to look at the recommended Patterns, but that is not part of this exercise.) | ||
| − | |||
| − | |||
Latest revision as of 11:20, 12 August 2019
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?
Solutions:
1) There are a couple of possible issues in Owen’s case.
- HIGH ROI EXPECTATIONS (Management Issue) may be the most appropriate issue for Owen, since he clearly expected to get more benefits for his investment by now.
- UNREALISTIC EXPECTATIONS (Management Issue) may also be a relevant issue, since Owen’s expectations were not realistic.
2) Using the Diagnostic Owen could select:
- NO PREVIOUS TEST AUTOMATION (Management Issue) - there is lots of good advice here that Owen would have benefitted from looking at earlier!
- Assuming that Owen wants to Improve or revive test automation, the most appropriate heading is Management expectations for automation not met. Here we find both of the issues above (UNREALISTIC EXPECTATIONS and HIGH ROI EXPECTATIONS). Both of these are relevant and contain useful advice for Owen.
For example, let’s look at UNREALISTIC EXPECTATIONS:
- The list of expectations matches a lot of Owen’s ideas, so this is probably the most appropriate issue for him.
(Note that the next step would be to look at the recommended Patterns, but that is not part of this exercise.)