Debbie Disappointed Solution

1) Go to Test Automation Issues Mind Map or Test Automation Issues. Look through the Issue names and see if one stands out as Ivan's main problem.

• Looking through the Issues, the most relevant one is INADEQUATE DOCUMENTATION.

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

• Looking through the Patterns, DOCUMENT THE TESTWARE (Process Pattern) is the one that Ivan should have used, and is probably the best one for him now as well (even if he doesn’t like the idea!)
  
  
• DESIGN FOR REUSE (Design Pattern) may also be appropriate.

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

Using the Diagnostic, the following path is one possibility:

• The most appropriate choice is to “want to improve or revive your test automation”.
• At the next level, the most appropriate choice is “Maintenance expectations not met” (although some of the others may also apply).
• The best choice now is the one about other people not understanding what the automation is doing, so the issue is INADEQUATE DOCUMENTATION.
• There are three patterns listed in the Issue: DOCUMENT THE TESTWARE, DESIGN FOR REUSE and SET STANDARDS. All would be useful for Ivan.
• Looking at DOCUMENT THE TESTWARE, there is good advice for producing good automation documentation. One suggestion that may be very useful for Ivan is to let a “newbie” update the documentation, or in this case, get Ramesh to write documentation based on what he can glean from the scripts etc. Ivan can then review this and between them, they should come up with good documentation. Ramesh would gain familiarity with all the the automated testware by trying to write up what it does, and the discussions about this will help to bring him “up to speed” with Ivan’s work.
• It is important to SET STANDARDS for the documentation - and also to keep to them!

Back to Exercises