Difference between revisions of "SUT REMAKE"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
m (Topic titles in capital letters) |
||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">................................................................................................................[[Main Page]] / Back to [[ Management Issues]] / Back to [[Test Automation Issues]]</span> | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">................................................................................................................[[Main Page]] / Back to [[ Management 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">'''Issue Summary'''</span>= |
| − | + | <span style="font-size: 16px">Substantial changes are being made to the SUT or it is to be rewritten from scratch</span> | |
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
| − | + | <span style="font-size: 16px">Management</span> | |
| − | =<span style="font-family: Arial; font-size: 16px">Examples</span>= | + | =<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>= |
| − | + | <span style="font-size: 16px">Changes to the SUT can be for instance:</span><br /> | |
| − | |||
# <span style="font-size: 16px">New development technology</span> | # <span style="font-size: 16px">New development technology</span> | ||
# <span style="font-size: 16px">Substitution of known components with new ones</span> | # <span style="font-size: 16px">Substitution of known components with new ones</span> | ||
| Line 12: | Line 11: | ||
# <span style="font-size: 16px">Changed database structure</span> | # <span style="font-size: 16px">Changed database structure</span> | ||
# <span style="font-size: 16px">Localization</span> | # <span style="font-size: 16px">Localization</span> | ||
| − | + | =<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>= | |
| − | =<span style="font-family: Arial; font-size: 16px">Questions</span>= | + | <span style="font-family: Arial; font-size: 16px">Are the current tools still usable?</span><br /> <span style="font-family: Arial; font-size: 16px">Does development communicate what is being changed?</span><br /> |
| − | + | =<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>= | |
| − | =<span style="font-family: Arial; font-size: 16px">Resolving Patterns</span>= | + | <span style="font-family: Arial; font-size: 16px">Most recomended:</span><br /> |
| − | |||
| − | |||
* <span style="font-size: 16px">[[DO A PILOT]]: Use this pattern to find out if the current tools and automation strategies are still valid (recommended if your issue is similar to Example 1). </span> | * <span style="font-size: 16px">[[DO A PILOT]]: Use this pattern to find out if the current tools and automation strategies are still valid (recommended if your issue is similar to Example 1). </span> | ||
* <span style="font-family: Arial; font-size: 16px">[[WHOLE TEAM APPROACH]]: If you have to automate a completely new SUT (Example 1) and the development team has adopted an agile process this is the pattern of choice. </span> | * <span style="font-family: Arial; font-size: 16px">[[WHOLE TEAM APPROACH]]: If you have to automate a completely new SUT (Example 1) and the development team has adopted an agile process this is the pattern of choice. </span> | ||
* <span style="font-size: 16px">[[ABSTRACTION LEVELS]]: if you have to substantially rework your scripts, use this pattern on all the scripts you have to touch: you will have much less work when such changes happen again.</span> | * <span style="font-size: 16px">[[ABSTRACTION LEVELS]]: if you have to substantially rework your scripts, use this pattern on all the scripts you have to touch: you will have much less work when such changes happen again.</span> | ||
<br /> <span style="font-family: Arial; font-size: 16px">Other useful Patterns:</span><br /> | <br /> <span style="font-family: Arial; font-size: 16px">Other useful Patterns:</span><br /> | ||
| − | |||
* <span style="font-size: 16px">[[LEARN FROM MISTAKES]]: this pattern helps you learn from your current experience how to do better.</span> | * <span style="font-size: 16px">[[LEARN FROM MISTAKES]]: this pattern helps you learn from your current experience how to do better.</span> | ||
* <span style="font-size: 16px">[[MANAGEMENT SUPPORT]]: Apply this pattern to get the support you need in order to use other patterns.</span> | * <span style="font-size: 16px">[[MANAGEMENT SUPPORT]]: Apply this pattern to get the support you need in order to use other patterns.</span> | ||
* <span style="font-size: 16px">[[SHARE INFORMATION]] to learn what will be changed and to inform development when changes disrupt automation scripts</span> | * <span style="font-size: 16px">[[SHARE INFORMATION]] to learn what will be changed and to inform development when changes disrupt automation scripts</span> | ||
<br /> <span style="font-size: 14px">................................................................................................................[[Main Page]] / Back to [[ Management Issues]] / Back to [[Test Automation Issues]]</span></div> | <br /> <span style="font-size: 14px">................................................................................................................[[Main Page]] / Back to [[ Management Issues]] / Back to [[Test Automation Issues]]</span></div> | ||
Latest revision as of 14:29, 1 May 2018
................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
Issue Summary
Substantial changes are being made to the SUT or it is to be rewritten from scratch
Category
Management
Examples
Changes to the SUT can be for instance:
- New development technology
- Substitution of known components with new ones
- Changed navigation
- Changed database structure
- Localization
Questions
Are the current tools still usable?
Does development communicate what is being changed?
Resolving Patterns
Most recomended:
- DO A PILOT: Use this pattern to find out if the current tools and automation strategies are still valid (recommended if your issue is similar to Example 1).
- WHOLE TEAM APPROACH: If you have to automate a completely new SUT (Example 1) and the development team has adopted an agile process this is the pattern of choice.
- ABSTRACTION LEVELS: if you have to substantially rework your scripts, use this pattern on all the scripts you have to touch: you will have much less work when such changes happen again.
Other useful Patterns:
- LEARN FROM MISTAKES: this pattern helps you learn from your current experience how to do better.
- MANAGEMENT SUPPORT: Apply this pattern to get the support you need in order to use other patterns.
- SHARE INFORMATION to learn what will be changed and to inform development when changes disrupt automation scripts
................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues