Difference between revisions of "Maintenance costs too high"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"> =<span style="font-size: 16px">What costs too much when maintaining test automation?</span>= <br /> <span style="fo...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 6: | Line 6: | ||
# <span style="background-color: #ffffff; font-size: 16px">[[Refactoring the automation scripts]] in order to improve them or re-design them structurally.</span> | # <span style="background-color: #ffffff; font-size: 16px">[[Refactoring the automation scripts]] in order to improve them or re-design them structurally.</span> | ||
# <span style="background-color: #ffffff; font-size: 16px">[[Creation or maintenance of test data]], where the data used in the automated tests has become "out of step" with the SUT and needs to be updated, or needs to be generated from some other source.</span> | # <span style="background-color: #ffffff; font-size: 16px">[[Creation or maintenance of test data]], where the data used in the automated tests has become "out of step" with the SUT and needs to be updated, or needs to be generated from some other source.</span> | ||
| − | # <span style="background-color: #ffffff; font-size: 16px">[[People costs ]]have not been budgeted at all or not correctly.</span> | + | # <span style="background-color: #ffffff; font-size: 16px">[[People costs]] have not been budgeted at all or not correctly.</span> |
# <span style="background-color: #ffffff; color: #000000; font-size: 16px">[[Other costs ]](hardware, software, Networks etc. ) for maintaining automated tests have not been budgeted for or are higher than expected.</span> | # <span style="background-color: #ffffff; color: #000000; font-size: 16px">[[Other costs ]](hardware, software, Networks etc. ) for maintaining automated tests have not been budgeted for or are higher than expected.</span> | ||
# <span style="background-color: #ffffff; font-size: 16px">Changing to a new tool means that we can't use any of our existing tests without major effort. See the issue ''[[TOOL DEPENDENCY]].''</span> | # <span style="background-color: #ffffff; font-size: 16px">Changing to a new tool means that we can't use any of our existing tests without major effort. See the issue ''[[TOOL DEPENDENCY]].''</span> | ||
| − | <br /> <br /> <span style="font-size: 16px">Return to [[Maintenance expectations not met]]</span | + | <br /> <br /> <span style="font-size: 16px">Return to [[Maintenance expectations not met]]</span> |
Latest revision as of 11:12, 12 August 2019
What costs too much when maintaining test automation?
Please select the answer that describes best where you see the highest expense.
- Updating the automation scripts after changes have been made to the Software Under Test (SUT) and the existing tests either no longer run or give incorrect results. It takes more effort to adapt the existing scripts than to start again.
- Refactoring the automation scripts in order to improve them or re-design them structurally.
- Creation or maintenance of test data, where the data used in the automated tests has become "out of step" with the SUT and needs to be updated, or needs to be generated from some other source.
- People costs have not been budgeted at all or not correctly.
- Other costs (hardware, software, Networks etc. ) for maintaining automated tests have not been budgeted for or are higher than expected.
- Changing to a new tool means that we can't use any of our existing tests without major effort. See the issue TOOL DEPENDENCY.
Return to Maintenance expectations not met