Ivan Indispensible

From Test Automation Patterns
Revision as of 14:34, 20 April 2018 by Cathal (talk | contribs) (Created page with "<div id="content_view" class="wiki" style="display: block"> Ivan is the test architect and test automator for the project. He designed the automation using good programming pr...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Ivan is the test architect and test automator for the project. He designed the automation using good programming practices, since he has a good background as a developer. His scripts are well-structured, and there is little if any duplication because he knows to create a new script with the common code which is called by each test that needs to do whatever is in that common script. The automation is a great success, with more and more tests being automated. But the company has recently merged with a company that doesn’t have any automation, so they want to apply the automation to the applications that have recently been acquired. The new company has assigned Ramesh to find out about Ivan’s automation and apply it to their own systems. This is being done remotely, as the acquired company is in a different country (and time-zone). However, Ramesh is struggling to know what is going on, because Ivan hasn’t written much (if any) documentation or comments about the automation. To be honest, Ivan considered it a waste of time, as he was the only person using the automation at the time, but he now recognises that if the automation is to be more widely used, he may need to do things differently.


1) Look at the mind map of Test Automation Patterns. Which Pattern(s) would best represent the solution to Ivan’s current problem?

2) Using the Diagnostic, what Issue(s) describe Ivan’s current problem and what Pattern(s) would be most beneficial?