Difference between revisions of "MIX APPROACHES"
| (5 intermediate revisions by 2 users not shown) | |||
| Line 13: | Line 13: | ||
* <span style="font-size: 16px">[[PREFER FAMILIAR SOLUTIONS]]: if possible chose tools that are already in use in your organization and that are well known</span> | * <span style="font-size: 16px">[[PREFER FAMILIAR SOLUTIONS]]: if possible chose tools that are already in use in your organization and that are well known</span> | ||
* <span style="font-size: 16px">[[AUTOMATE WHAT'S NEEDED]]: decide individually for each application if it’s better to use test automation, manual tests or a mixture of both</span> | * <span style="font-size: 16px">[[AUTOMATE WHAT'S NEEDED]]: decide individually for each application if it’s better to use test automation, manual tests or a mixture of both</span> | ||
| + | =<span style="font-size: 16px">'''Potential problems'''</span>= | ||
| + | <span style="font-size: 16px"> <span style="font-size: 16px">Make sure that the approaches you choose to mix are able to work together. You could waste a lot of time trying to get incompatible tools to work together, which wouldn't be worth the effort. </span> | ||
=<span style="font-size: 16px">'''Issues addressed with this pattern'''</span>= | =<span style="font-size: 16px">'''Issues addressed with this pattern'''</span>= | ||
<span style="font-size: 16px">''[[INADEQUATE TOOLS]]''</span>''<br /> ''<span style="font-size: 16px">''[[MANUAL INTERVENTIONS]]''</span>'' | <span style="font-size: 16px">''[[INADEQUATE TOOLS]]''</span>''<br /> ''<span style="font-size: 16px">''[[MANUAL INTERVENTIONS]]''</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:48, 21 August 2018
Pattern summary
Don’t be afraid to use different tools or approaches
Category
Management
Context
This pattern is appropriate when you want to automate as efficiently as possible
Description
Use a variety of different tools or approaches, as they can complement each other and give you much better results than if you stick to just one tool or approach
Implementation
- For every task, use the tool that fits best
- Freeware tools can be just as effective as expensive commercial ones
- PREFER FAMILIAR SOLUTIONS: if possible chose tools that are already in use in your organization and that are well known
- AUTOMATE WHAT'S NEEDED: decide individually for each application if it’s better to use test automation, manual tests or a mixture of both
Potential problems
Make sure that the approaches you choose to mix are able to work together. You could waste a lot of time trying to get incompatible tools to work together, which wouldn't be worth the effort.
Issues addressed with this pattern
INADEQUATE TOOLS
MANUAL INTERVENTIONS
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