Difference between revisions of "SCRIPT CREEP"
Jump to navigation
Jump to search
m (Topic titles in capital letters) |
|||
| Line 12: | Line 12: | ||
=<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 recommended:</span><br /> | <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> | ||
| − | * <span style="font-family: Arial; font-size: 16px">[[GOOD PROGRAMMING PRACTICES]]</span> | + | * <span style="font-family: Arial; font-size: 16px">[[GOOD PROGRAMMING PRACTICES]]: you should have been using this pattern from the very beginning</span> |
| − | * <span style="font-size: 16px">[[MAINTAINABLE TESTWARE]]</span> | + | * <span style="font-size: 16px">[[MAINTAINABLE TESTWARE]]: this pattern will help you write maintainable testware</span> |
| − | * <span style="font-size: 16px">[[MAINTAIN THE TESTWARE]]</span> | + | * <span style="font-size: 16px">[[MAINTAIN THE TESTWARE]]: you should already use this pattern</span> |
* <span style="font-size: 16px">[[MANAGEMENT SUPPORT]]: You will need this pattern to be able to change the current bad behaviour</span> | * <span style="font-size: 16px">[[MANAGEMENT SUPPORT]]: You will need this pattern to be able to change the current bad behaviour</span> | ||
| − | * <span style="font-size: 16px">[[REFACTOR THE TESTWARE]]</span> | + | * <span style="font-size: 16px">[[REFACTOR THE TESTWARE]]: you should already use this pattern</span> |
<span style="font-family: Arial; font-size: 16px">You should already be applying these patterns. If not, do it!</span><br /> <br /> <span style="font-size: 16px">Other useful Patterns:</span><br /> | <span style="font-family: Arial; font-size: 16px">You should already be applying these patterns. If not, do it!</span><br /> <br /> <span style="font-size: 16px">Other useful Patterns:</span><br /> | ||
* <span style="font-size: 16px">[[GOOD DEVELOPMENT PROCESS]]: apply this pattern if you don't have a process for developing test automation. Apply it also if your process lives only on paper (nobody cares)</span> | * <span style="font-size: 16px">[[GOOD DEVELOPMENT PROCESS]]: apply this pattern if you don't have a process for developing test automation. Apply it also if your process lives only on paper (nobody cares)</span> | ||
Revision as of 14:24, 27 June 2018
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
Issue Summary
There are too many scripts and it is not clear if they are still in use or not.
Category
Process
Examples
- It takes so much time to check if a script is already available that testers or automators would rather write a new one instead. This means that there are a lot of very similar scripts.
- Nobody "refactors" the scripts so that after a time some fail consistently and are not executed any longer.
- It isn't possible to check which scripts are actually in use.
Questions
How are scripts documented?
Are there standards regarding naming and documentation?
Who writes the scripts? Who uses them?
Is anyone charged with reviewing the relevance and usefulness of the scripts at regular intervals?
Resolving Patterns
Most recommended:
- GOOD PROGRAMMING PRACTICES: you should have been using this pattern from the very beginning
- MAINTAINABLE TESTWARE: this pattern will help you write maintainable testware
- MAINTAIN THE TESTWARE: you should already use this pattern
- MANAGEMENT SUPPORT: You will need this pattern to be able to change the current bad behaviour
- REFACTOR THE TESTWARE: you should already use this pattern
You should already be applying these patterns. If not, do it!
Other useful Patterns:
- GOOD DEVELOPMENT PROCESS: apply this pattern if you don't have a process for developing test automation. Apply it also if your process lives only on paper (nobody cares)
- LEARN FROM MISTAKES: apply this pattern to turn mistakes into useful experiences
- KILL THE ZOMBIES: Apply this pattern for a start
- DOCUMENT THE TESTWARE: you should be already applying this pattern. Retrofixing documentation is quite an effort. Do it in the future for all new projects and everytime you have to update something old
- KEEP IT SIMPLE: Always apply this pattern!
- SET STANDARDS: apply this pattern so that team members “speak the same language” and hence can efficiently share their work
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues