Solution to Sharon Stressed

From Test Automation Patterns
Revision as of 11:14, 12 August 2019 by Seretta (talk | contribs) (Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 16px"> Sharon started test automation for her company. She developed a lot of automated tes...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Sharon started test automation for her company. She developed a lot of automated tests and both testers and management have been really satisfied with her work.
But the problem is that Sharon is getting more and more busy working on more and more tests that people now want her to automate, and she has less and less time for script maintenance. There are some scripts that could do with being re-factored, some common areas that should now be made into common scripts, and some tests that are failing because the applications being tested have changed in ways that the scripts didn’t plan to cope with. Sharon is getting stressed! No one else has the technical expertise to do the maintenance, and she is too busy writing new automated tests.


Using the Diagnostic, what is Sharon’s main issue?

Solution:
Here are some possible ways to get to the issue using the Diagnostic: 1. Since Sharon is the only one with enough technical expertise, the first possibility is to look at the issue LIMITED EXPERIENCE. 2. From the Diagnostic, Improve or revive your test automation