Difference between revisions of "NO PREVIOUS TEST AUTOMATION"
Jump to navigation
Jump to search
m (Put topic titles in capital letters) |
m (Corrected link to automate what's needed) |
||
| Line 19: | Line 19: | ||
# <span style="font-size: 16px"> [[PLAN SUPPORT ACTIVITIES]]:Don't forget to apply this pattern if you want to be able to keep your schedules. Missing support from specialists can ground a project pretty effectively!</span> | # <span style="font-size: 16px"> [[PLAN SUPPORT ACTIVITIES]]:Don't forget to apply this pattern if you want to be able to keep your schedules. Missing support from specialists can ground a project pretty effectively!</span> | ||
# <span style="font-size: 16px"> [[MAINTAINABLE TESTWARE]]: Apply this pattern from the very beginning if you want your automation effort to be long lasting and your maintenance costs low</span> | # <span style="font-size: 16px"> [[MAINTAINABLE TESTWARE]]: Apply this pattern from the very beginning if you want your automation effort to be long lasting and your maintenance costs low</span> | ||
| − | # <span style="font-size: 16px"> [[AUTOMATE | + | # <span style="font-size: 16px"> [[AUTOMATE WHAT'S NEEDED]]:This pattern shows you how to select the features most worthy to be automated</span> |
# <span style="font-size: 16px"> [[TAKE SMALL STEPS]]:This pattern is especially important in the beginning, but it should always be kept in mind</span> | # <span style="font-size: 16px"> [[TAKE SMALL STEPS]]:This pattern is especially important in the beginning, but it should always be kept in mind</span> | ||
# <span style="font-size: 16px"> [[UNATTENDED TEST EXECUTION]]:This pattern gives you the last suggestions on how to get done with test automation</span> | # <span style="font-size: 16px"> [[UNATTENDED TEST EXECUTION]]:This pattern gives you the last suggestions on how to get done with test automation</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> | ||
Revision as of 09:06, 3 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
You are supposed to start automating tests, but neither you nor your team has any experience in test automation and it hasn’t ever been implemented in the company, or it was tried earlier and failed so you need to start again. The NO PREVIOUS TEST AUTOMATION Mind Map shows an overview of the resolving patterns for this issue.
Category
Management
Examples
You have never successfully got going with test automation.
You have tried in the past with test automation but it was abandoned.
You are wanting to automate in a way that you haven't done before (e.g. GUI level system testing if you have automated unit tests already).
Questions
What are the reasons for wanting to automate testing now?
What measurable objectives will determine success for the automation?
What resources and support will be given to this effort?
If automation has failed in the past, analyse what happened. Were the main reasons due to management issues or technical issues?
Talk to people who were around at the time. What would they do differently? What advice can they give you?
Resolving Patterns
We recommend doing these patterns in this order:
- SET CLEAR GOALS: This pattern is critical. It must be applied at the beginning of any big or small automation effort
- MANAGEMENT SUPPORT: Also critical. Automation efforts that are driven only by a lone hero are much more apt to stall because nobody else knows about it or can use and maintain what has been developed
- TEST AUTOMATION OWNER: appoint somebody not only to introduce test automation, but to keep it up and running also in the future
- DEDICATED RESOURCES: This pattern is especially important at the beginning of a new automation effort. Depending on the size of your automation you can later slacken its use
- RIGHT TOOLS:This pattern is essential not only for long lasting automation, but also for quick fixes
- AUTOMATION ROLES: Use this pattern to fill the roles you need to develop the automation testware. If possible use a WHOLE TEAM APPROACH and if needed GET TRAINING for your people
- PLAN SUPPORT ACTIVITIES:Don't forget to apply this pattern if you want to be able to keep your schedules. Missing support from specialists can ground a project pretty effectively!
- MAINTAINABLE TESTWARE: Apply this pattern from the very beginning if you want your automation effort to be long lasting and your maintenance costs low
- AUTOMATE WHAT'S NEEDED:This pattern shows you how to select the features most worthy to be automated
- TAKE SMALL STEPS:This pattern is especially important in the beginning, but it should always be kept in mind
- UNATTENDED TEST EXECUTION:This pattern gives you the last suggestions on how to get done with test automation
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues