Difference between revisions of "Ted Toolswitcher"
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 16px">Ted’s automation was going just great – lots of tests automated, regression suites...") |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 16px">Ted’s automation was going just great – lots of tests automated, regression suites run every night, scripts were well-structured, and Ted was really happy with the tool they have build their tests in. It was a well-established tool and they were confident if would be around for a long time – that’s why they went for it.</span><br /> | + | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 16px"> |
| + | |||
| + | Ted’s automation was going just great – lots of tests automated, regression suites run every night, scripts were well-structured, and Ted was really happy with the tool they have build their tests in. It was a well-established tool and they were confident if would be around for a long time – that’s why they went for it.</span><br /> | ||
| + | |||
| + | <span style="font-size: 16px">But now there is a problem. The tool development is headed in one direction, and the applications Ted is testing are going in a completely different direction. Ted has tried to convince the tool vendors to support their company, but they won’t do it. They will no longer support the version Ted is using, which is several releases out of date already, since the new features in the tool were not compatible with their tests. What should Ted do? Does he need to start again from scratch with a new tool? How can he make sure things will be better next time?</span><br /> <br /> <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 Ted's main problem. See which patterns would solve it | ||
| + | </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 Ted. | ||
| + | </span><br /> <br /> | ||
| + | |||
| + | <span style="font-size: 16px"> | ||
| + | 3) Go to the [[Diagnostic]]. Answer the questions on Ted'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 /> </div> | ||
Latest revision as of 14:14, 17 May 2019
Ted’s automation was going just great – lots of tests automated, regression suites run every night, scripts were well-structured, and Ted was really happy with the tool they have build their tests in. It was a well-established tool and they were confident if would be around for a long time – that’s why they went for it.
But now there is a problem. The tool development is headed in one direction, and the applications Ted is testing are going in a completely different direction. Ted has tried to convince the tool vendors to support their company, but they won’t do it. They will no longer support the version Ted is using, which is several releases out of date already, since the new features in the tool were not compatible with their tests. What should Ted do? Does he need to start again from scratch with a new tool? How can he make sure things will be better next time?
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 Ted's main problem. See which patterns would solve it
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 Ted.
3) Go to the Diagnostic. Answer the questions on Ted's behalf and see if you find the same issues and patterns.
Back to Exercises