Difference between revisions of "Ursula Unfocused"

From Test Automation Patterns
Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<div id="content_view" class="wiki" style="display: block"> Ursula has recently begun automation and is trying to structure the tests in a good way using good programming principles. She has a developer background so is happy working with automation code. What Ursula struggles with is deciding what tests should be automated. She started out by just picking a few that seemed a good idea, some smoke tests that were run often. But then she decided to automate some that were easy to automate, because that made her “look good” for making progress on the automation. Now there are complaints that some of the most important parts of the application have no automation, and there is still lots of manual testing that needs to be done, even though a lot of tests have been automated.
+
<div id="content_view" class="wiki" style="display: block"><span style="display: block; text-align: left"><span style="font-size: 16px">
  
What Issue(s) is Ursula suffering from, and what Pattern(s) would be helpful to her? Use any two approaches to the wiki to try to find the answer - mind-maps or lists of Issues or Patterns or the Diagnostic. </div>
+
 
 +
Ursula has recently begun automation and is trying to structure the tests in a good way using good programming principles. She has a developer background so is happy working with automation code.
 +
 
 +
</span></span> <span style="display: block; text-align: left"><span style="font-size: 16px">
 +
 
 +
 
 +
What Ursula struggles with is deciding what tests should be automated. She started out by just picking a few that seemed a good idea, some smoke tests that were run often. But then she decided to automate some that were easy to automate, because that made her “look good” for making progress on the automation. Now there are complaints that some of the most important parts of the application have no automation, and there is still lots of manual testing that needs to be done, even though a lot of tests have been automated.
 +
 
 +
<span style="font-size: 16px">
 +
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 Ursula's main problem. See which patterns would solve it
 +
</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 Ursula.
 +
</span><br /> <br />
 +
 
 +
<span style="font-size: 16px">
 +
3) Go to the [[Diagnostic]]. Answer the questions on Ursula'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 08:47, 3 April 2019


Ursula has recently begun automation and is trying to structure the tests in a good way using good programming principles. She has a developer background so is happy working with automation code.


What Ursula struggles with is deciding what tests should be automated. She started out by just picking a few that seemed a good idea, some smoke tests that were run often. But then she decided to automate some that were easy to automate, because that made her “look good” for making progress on the automation. Now there are complaints that some of the most important parts of the application have no automation, and there is still lots of manual testing that needs to be done, even though a lot of tests have been automated.

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 Ursula'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 Ursula.

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



Back to Exercises