Refactoring the automation scripts

From Test Automation Patterns
Revision as of 13:27, 24 April 2018 by Cathal (talk | contribs) (Created page with "<div id="content_view" class="wiki" style="display: block">'''<span style="font-size: 16px">Why do you need to refactor your automation scripts?</span>= <br /> <span style="fo...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Why do you need to refactor your automation scripts?=


Please select the main reason to refactor the scripts in the list below:

  1. The scripts have been generated using the capture feature of a tool. The issue TOOL-DRIVEN AUTOMATION gives you a list of the patterns that will help you solve it.
  2. The scripts are so complicated that nobody understands them.
  3. There are a lot of similar scripts and since it's not possible to check which scripts are actually in use, more refactoring work is done than is actually necessary. We call this issue SCRIPT CREEP: look it up in order to find out which patterns would help you solve it.
  4. The scripts work and you want to keep them that way. If you are trying to keep the code in your scripts clean and efficient, but your management thinks that it increases maintenance costs too much, you should look up the issue UNREALISTIC EXPECTATIONS. It will show you which patterns will help you most in such a case.

Return to Maintenance costs too high
Retrieved from ‘https://huddletalk.wpengine.com/wiki/index.php?title=Refactoring_the_automation_scripts&oldid=330’