View source for BRITTLE SCRIPTS

<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span> 
=<span style="font-family: Arial; font-size: 16px">'''Issue Summary'''</span>=
<span style="font-family: Arial; font-size: 16px">Automation scripts have to be reworked for any small change to the Software Under Test (SUT)</span> 
=<span style="font-size: 16px">'''Category'''</span>=
<span style="font-size: 16px">Design</span> 
=<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>=
<span style="font-size: 16px">Scripts are created using the capture functionality of an automation tool. If in the meantime something has been changed in the application, the tests will break unless recorded anew.</span><br /> <span style="font-size: 16px">A small change to the application (such as moving something to a different screen, or changing the text of a button) causes many scripts to fail because this information is embedded in the scripts for many tests.</span> 
=<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>=
<span style="font-size: 16px">How do you develop automation scripts? (Capture is not good long-term though ok for short complex actions.)</span><br /> <span style="font-size: 16px">Is there repeated code in any scripts? (Keep your automation code DRY - Don't' Repeat Yourself - put common code and actions into scripts called by other scripts.)</span><br /> <span style="font-size: 16px">What kinds of changes are most likely to happen to the application? (Make your automation most flexible for those changes.)</span> 
=<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>=
<span style="font-size: 16px">Most recommended:</span><br /> 
* <span style="font-size: 16px">[[TESTWARE ARCHITECTURE]]: This pattern encompasses the overall approach to the automation artefacts, and is best thought about right from the start of automation so that you can avoid having this issue. This pattern is implemented using:</span>
* <span style="font-size: 16px"><span style="font-size: 16px">[[ABSTRACTION LEVELS]]: This is the pattern to apply if you want to delegate some of the maintenance effort</span> to the testers. It will enable you to write test cases that are both independent from the SUT and from the technical implementation of the automation (including the tools(s)).</span>
* <span style="font-size: 16px">[[MAINTAINABLE TESTWARE]]: This is the pattern to apply if you want to get rid of the issue once and for all. If you haven't implemented it yet, you may want to apply at least some aspects of this pattern.</span>
* <span style="font-size: 16px">[[ MANAGEMENT SUPPORT]]: This is the pattern to apply if you are missing support or resources that you need in order to develop [[MAINTAINABLE TESTWARE]].</span>
* <span style="font-size: 16px">[[MODEL-BASED TESTING]]: This pattern involves considerable effort at the beginning, but is the most efficient in the long run. Using a test model, the test cases can be cleanly separated from the technical details. Frequently used sequences of test steps can be defined as reusable and parametrisable building blocks. If the SUT changes, usually only a few building blocks need to be adapted while the test scripts are updated automatically.</span>
* <span style="font-size: 16px"><span style="font-size: 16px">[[COMPARISON DESIGN]]: </span>Design the comparison of test results to be as efficient as possible, balancing Dynamic and Post-Execution Comparison, and using a mixture of Sensitive and Robust/Specific comparisons.</span>
<br /> <span style="font-size: 16px">Other useful patterns:</span><br /> 
* <span style="font-size: 16px">[[GOOD PROGRAMMING PRACTICES]]: This pattern should already be in use! If not, you should apply it for all new automation efforts. Apply it also every time you have to change current testware.</span>
<br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span>