Difference between revisions of "Ted Toolswitcher"
| 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 /> <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 /> | + | <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 /> <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 /> | ||
| + | |||
| + | <span style="display: block; font-size: 16px; text-align: left">Use the wiki to identify Ted's main Issue(s) and the Pattern(s) that would be most appropriate for him. (Hint: try entering "tool" in the search box.) | ||
| + | |||
| + | |||
| + | </span></span><br /> <br /> <span style="font-size: 16px">Back to [[Exercises]]</span><br/ ></div> | ||
Revision as of 08:28, 9 July 2018
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?
Use the wiki to identify Ted's main Issue(s) and the Pattern(s) that would be most appropriate for him. (Hint: try entering "tool" in the search box.)
Back to Exercises