Difference between revisions of "Ivan Indispensible"
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | <div id="content_view" class="wiki" style="display: block"> | + | '''<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 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. | 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. | ||
| Line 7: | Line 7: | ||
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.<br /> <br /> | 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.<br /> <br /> | ||
| − | |||
| − | + | <span style="font-size: 16px"> | |
| + | Exercises:</span><br /> | ||
| − | </span></span><br /> <br /> <span style="font-size: 16px">Back to [[Exercises]]</span><br/ ></ | + | <span style="font-size: 16px"> |
| + | 1) Go to [[Test Automation Issues Mind Map]] or [https://atlas.mindmup.com/testautomationpattern/test_automation_issues_https_testautom/index.html Test Automation Issues Mind map with clickable links]. Look through the Issue names and see if one stands out as Ivan's main problem. | ||
| + | </span></span><br /> <br />''' | ||
| + | |||
| + | <span style="font-size: 16px"> | ||
| + | 2) Go to [[Test Automation Patterns Mind Map]] or [https://atlas.mindmup.com/testautomationpattern/test_automation_patterns/index.html Test Automation Patterns Mind Map with clickable links]. Look through the Pattern names and see which stand out as possible solutions for Ivan. | ||
| + | </span><br /> <br /> | ||
| + | |||
| + | <span style="font-size: 16px"> | ||
| + | 3) Go to the [[Diagnostic]]. Answer the questions on Ivan's behalf and see if you find the same issues and patterns. | ||
| + | </span><br /> <br /> | ||
| + | |||
| + | |||
| + | <br /> <span style="font-size: 16px">Back to [[Exercises]]</span><br/ ><br /> | ||
Latest revision as of 09:04, 3 April 2019
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.
Exercises:
1) Go to Test Automation Issues Mind Map or Test Automation Issues Mind map with clickable links. Look through the Issue names and see if one stands out as Ivan's main problem.
2) Go to Test Automation Patterns Mind Map or Test Automation Patterns Mind Map with clickable links. Look through the Pattern names and see which stand out as possible solutions for Ivan.
3) Go to the Diagnostic. Answer the questions on Ivan's behalf and see if you find the same issues and patterns.
Back to Exercises