Difference between revisions of "Maintenance expectations not met"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 16px">Please select what you think is the main reason for the maintenance expectations not b...") |
m |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
# <span style="font-size: 16px"><span style="font-size: 16px">[[Maintenance costs too high]]. </span>Maintenance of the automation is (considered) too expensive.</span> | # <span style="font-size: 16px"><span style="font-size: 16px">[[Maintenance costs too high]]. </span>Maintenance of the automation is (considered) too expensive.</span> | ||
| − | # <span style="font-size: 16px">[[ Not | + | # <span style="font-size: 16px">[[ Not reusing existing data]] or other problems with test data.</span> |
# <span style="font-size: 16px">Other people have trouble understanding what the tests are, what the scripts do, how the automation works etc. The issue to look at is ''[[INADEQUATE DOCUMENTATION]]''.</span> | # <span style="font-size: 16px">Other people have trouble understanding what the tests are, what the scripts do, how the automation works etc. The issue to look at is ''[[INADEQUATE DOCUMENTATION]]''.</span> | ||
# <span style="font-size: 16px">You have written all your scripts in the language and structure of your current tool, but that tool is no longer appropriate for you. The issue you should look up is ''[[TOOL DEPENDENCY]]''.</span> | # <span style="font-size: 16px">You have written all your scripts in the language and structure of your current tool, but that tool is no longer appropriate for you. The issue you should look up is ''[[TOOL DEPENDENCY]]''.</span> | ||
# <span style="font-size: 16px">Documentation is non-existent, so only the developer of the automation can work with it. The issue ''[[OBSCURE TESTS]]'' will give you a good start on how to solve this problem.</span> | # <span style="font-size: 16px">Documentation is non-existent, so only the developer of the automation can work with it. The issue ''[[OBSCURE TESTS]]'' will give you a good start on how to solve this problem.</span> | ||
# <span style="font-size: 16px">It's difficult to pair the automated scripts to the correct release of the Software Under Test (SUT). Look up the issue ''[[INADEQUATE REVISION CONTROL]]'' for suggestions.</span> | # <span style="font-size: 16px">It's difficult to pair the automated scripts to the correct release of the Software Under Test (SUT). Look up the issue ''[[INADEQUATE REVISION CONTROL]]'' for suggestions.</span> | ||
| − | <br /> <br /> <span style="background-color: #ffffff; color: #000000; font-size: 16px">Return to [[Improve or revive test | + | <br /> <br /> <span style="background-color: #ffffff; color: #000000; font-size: 16px">Return to [[Improve or revive test automation]]</span></div> |
Latest revision as of 10:36, 27 September 2018
Please select what you think is the main reason for the maintenance expectations not being met:
Return to Improve or revive test automation
- Maintenance costs too high. Maintenance of the automation is (considered) too expensive.
- Not reusing existing data or other problems with test data.
- Other people have trouble understanding what the tests are, what the scripts do, how the automation works etc. The issue to look at is INADEQUATE DOCUMENTATION.
- You have written all your scripts in the language and structure of your current tool, but that tool is no longer appropriate for you. The issue you should look up is TOOL DEPENDENCY.
- Documentation is non-existent, so only the developer of the automation can work with it. The issue OBSCURE TESTS will give you a good start on how to solve this problem.
- It's difficult to pair the automated scripts to the correct release of the Software Under Test (SUT). Look up the issue INADEQUATE REVISION CONTROL for suggestions.
Return to Improve or revive test automation