Difference between revisions of "SIDE-BY-SIDE"
m (Topic titles in capital letters) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
<span style="font-size: 16px">Use this pattern when you have to decide which tool or framework is best for testing your Software Under Test (SUT).</span> | <span style="font-size: 16px">Use this pattern when you have to decide which tool or framework is best for testing your Software Under Test (SUT).</span> | ||
=<span style="font-size: 16px">'''Description'''</span>= | =<span style="font-size: 16px">'''Description'''</span>= | ||
| − | <span style="font-size: 16px">If you have to select the tool that works best with the SUT and you have more than one candidate, the easiest way to chose is to try them out side by side. In this way it | + | <span style="font-size: 16px">If you have to select the tool that works best with the SUT and you have more than one candidate, the easiest way to chose is to try them out side by side. In this way it should become apparent which tool serves your needs best.</span><br /> <span style="font-size: 16px">Use this pattern also if you have to select a [[TEST AUTOMATION FRAMEWORK]].</span> |
=<span style="font-size: 16px">'''Implementation'''</span>= | =<span style="font-size: 16px">'''Implementation'''</span>= | ||
<span style="font-size: 16px">Automate a [[STEEL THREAD]] with all the relevant tools and compare the results:</span><br /> | <span style="font-size: 16px">Automate a [[STEEL THREAD]] with all the relevant tools and compare the results:</span><br /> | ||
| Line 14: | Line 14: | ||
* <span style="font-size: 16px">Which tool is easier to learn?</span> | * <span style="font-size: 16px">Which tool is easier to learn?</span> | ||
* <span style="font-size: 16px">Which tool is easier to use?</span> | * <span style="font-size: 16px">Which tool is easier to use?</span> | ||
| + | =<span style="font-size: 16px">'''Potential problems'''</span>= | ||
| + | <span style="font-size: 16px"> <span style="font-size: 16px">Make sure that both (or all) candidate tools are used in the same way. As you compare them, you may get ideas to try on previously tried tools, so go back and do that. Don't spend too much time comparing tools side by side; if a clear favourite isn't obvious within a few days, then any of them will work. The choice of tool is not the main determinator of success in automation. </span> | ||
=<span style="font-size: 16px">'''Issues addressed by this pattern'''</span>= | =<span style="font-size: 16px">'''Issues addressed by this pattern'''</span>= | ||
''<span style="font-size: 16px">[[INADEQUATE TOOLS]]</span>'' | ''<span style="font-size: 16px">[[INADEQUATE TOOLS]]</span>'' | ||
=<span style="font-size: 16px">'''Experiences'''</span>= | =<span style="font-size: 16px">'''Experiences'''</span>= | ||
| − | <span style="font-size: 16px">If you have used this pattern, please | + | |
| + | <span style="font-size: 16px">If you have used this pattern and would like to contribute your experience to the wiki, please go to [[Feedback]] to submit your experience or comment.</span><br /> <br /> | ||
| + | |||
| + | |||
| + | <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span> | ||
Latest revision as of 14:50, 21 August 2018
Pattern summary
Determine which automation tool is best for you by trying them side by side
Category
Management
Context
Use this pattern when you have to decide which tool or framework is best for testing your Software Under Test (SUT).
Description
If you have to select the tool that works best with the SUT and you have more than one candidate, the easiest way to chose is to try them out side by side. In this way it should become apparent which tool serves your needs best.
Use this pattern also if you have to select a TEST AUTOMATION FRAMEWORK.
Implementation
Automate a STEEL THREAD with all the relevant tools and compare the results:
- Which tool can drive the SUT better?
- Which tool is easier to learn?
- Which tool is easier to use?
Potential problems
Make sure that both (or all) candidate tools are used in the same way. As you compare them, you may get ideas to try on previously tried tools, so go back and do that. Don't spend too much time comparing tools side by side; if a clear favourite isn't obvious within a few days, then any of them will work. The choice of tool is not the main determinator of success in automation.
Issues addressed by this pattern
Experiences
If you have used this pattern and would like to contribute your experience to the wiki, please go to Feedback to submit your experience or comment.
.................................................................................................................Main Page / Back to Management Patterns / Back to Test Automation Patterns