Difference between revisions of "Process Patterns"
Jump to navigation
Jump to search
(Process patterns show how the test automation process should be set up or how it can be improved.) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-family: Arial; font-size: 16px">Process patterns show how the test automation process should be set up or how it can be improved. The table below gives a list of the Process patterns with a short description.</span><span style="font-size: 16px"> The [[Process Patterns Mind Map]] shows whi</span><span style="font-family: Arial; font-size: 16px">ch other patterns are used by the process patterns.</span><br /> <br /> <br /> | <div id="content_view" class="wiki" style="display: block"><span style="font-family: Arial; font-size: 16px">Process patterns show how the test automation process should be set up or how it can be improved. The table below gives a list of the Process patterns with a short description.</span><span style="font-size: 16px"> The [[Process Patterns Mind Map]] shows whi</span><span style="font-family: Arial; font-size: 16px">ch other patterns are used by the process patterns.</span><br /> <br /> <br /> | ||
| − | {| class="wiki_table" | + | {| class="wiki_table" border="1" style="border-collapse:collapse" |
! <span style="font-size: 16px">Pattern</span><br /> | ! <span style="font-size: 16px">Pattern</span><br /> | ||
! <span style="font-size: 16px">Description</span><br /> | ! <span style="font-size: 16px">Description</span><br /> | ||
| Line 23: | Line 23: | ||
|- | |- | ||
| <span style="font-size: 16px">[[GOOD DEVELOPMENT PROCESS]]</span><br /> | | <span style="font-size: 16px">[[GOOD DEVELOPMENT PROCESS]]</span><br /> | ||
| − | | <span style="font-size: 16px">Use good development practices for test code; the same as developers | + | | <span style="font-size: 16px">Use good development practices for test code; the same as developers (should) use for production code.</span><br /> |
|- | |- | ||
| <span style="font-size: 16px">[[GOOD PROGRAMMING PRACTICES]]</span><br /> | | <span style="font-size: 16px">[[GOOD PROGRAMMING PRACTICES]]</span><br /> | ||
| Line 70: | Line 70: | ||
| <span style="font-size: 16px">Testers, coders and other roles work together on one team to develop test automation along with production code.</span><br /> | | <span style="font-size: 16px">Testers, coders and other roles work together on one team to develop test automation along with production code.</span><br /> | ||
|} | |} | ||
| − | <br /> <span style="font-size: 16px">[[ | + | <br /> <span style="font-size: 16px">[[Main Page]] </span><br /> <span style="font-size: 16px">Back to [[Test Automation Patterns]]</span><br /> <span style="font-size: 16px">Forward to [[Management Patterns]]</span><br /> <br /> <br /> |
---- | ---- | ||
<span style="font-size: 16px">[1] Suggested by Lisa Crispin</span></div> | <span style="font-size: 16px">[1] Suggested by Lisa Crispin</span></div> | ||
Latest revision as of 16:51, 26 June 2018
Process patterns show how the test automation process should be set up or how it can be improved. The table below gives a list of the Process patterns with a short description. The Process Patterns Mind Map shows which other patterns are used by the process patterns.
[1] Suggested by Lisa Crispin
| Pattern |
Description |
|---|---|
| ASK FOR HELP |
Ask for help instead of wasting time trying to do everything yourself. |
| AUTOMATE WHAT'S NEEDED |
Automate what the developers or the testers need, even if it isn't tests! |
| CELEBRATE SUCCESS |
When you have reached an important milestone, it’s celebration time. |
| CHECK-TO-LEARN |
Let new team members learn by checking the health of the existing automation testware |
| DOCUMENT THE TESTWARE |
Document the automation scripts and the test data |
| FULL TIME JOB |
Arrange for the test automation team to be available full time. |
| GOOD DEVELOPMENT PROCESS |
Use good development practices for test code; the same as developers (should) use for production code. |
| GOOD PROGRAMMING PRACTICES |
Use the same good programming practices as in software development. |
| KILL THE ZOMBIES |
Regularly delete or archive test cases, scripts or test data that are not used. Make sure that tests are actually testing something. |
| LAZY AUTOMATOR |
Lazy people are the best automation engineers. |
| LEARN FROM MISTAKES |
Use mistakes to learn to do better next time. |
| LOOK AHEAD |
Keep in touch with the tester, automation and development community in order to stay informed about new tools, methods, patterns etc. |
| LOOK FOR TROUBLE |
Keep an eye on possible problems in order to solve them before they become unmanageable |
| MAINTAIN THE TESTWARE |
Maintain test automation scripts and test data regularly and from the very beginning. |
| PAIR UP |
Let less experienced team members pair up with more experienced team members. |
| REFACTOR THE TESTWARE |
Refactor your testware regularly |
| SET STANDARDS |
Set and follow standards for the automation artefacts. |
| SHARE INFORMATION |
Ask for and give information to managers, developers, other testers and customers. |
| SHORT ITERATIONS |
Develop test automation in short iterations. |
| TAKE SMALL STEPS |
Look for small increments of the work that will give you value. |
| TEST THE TESTS |
Test the scripts just as you would test production code. |
| WHOLE TEAM APPROACH [1] |
Testers, coders and other roles work together on one team to develop test automation along with production code. |
Main Page
Back to Test Automation Patterns
Forward to Management Patterns
[1] Suggested by Lisa Crispin