Difference between revisions of "INADEQUATE TOOLS"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
m (Topic titles in capital letters) |
||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span> | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span> | ||
| − | =<span style="font-family: Arial; font-size: 16px">Issue summary</span>= | + | =<span style="font-family: Arial; font-size: 16px">'''Issue summary'''</span>= |
<span style="font-family: Arial; font-size: 16px">The tools that are currently used are not appropriate for the Software Under Test (SUT) or are not supported any longer or you still don't have adequate tools.</span><br /> <br /> | <span style="font-family: Arial; font-size: 16px">The tools that are currently used are not appropriate for the Software Under Test (SUT) or are not supported any longer or you still don't have adequate tools.</span><br /> <br /> | ||
| − | =<span style="font-family: Arial; font-size: 16px">Category</span>= | + | =<span style="font-family: Arial; font-size: 16px">'''Category'''</span>= |
<br /> <span style="font-family: Arial; font-size: 16px">Management</span><br /> <br /> | <br /> <span style="font-family: Arial; font-size: 16px">Management</span><br /> <br /> | ||
| − | =<span style="font-family: Arial; font-size: 16px">Examples</span>= | + | =<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>= |
<br /> | <br /> | ||
| Line 12: | Line 12: | ||
# <span style="font-family: Arial; font-size: 16px">You want to start with test automation and have to select one or more suitable tools</span> | # <span style="font-family: Arial; font-size: 16px">You want to start with test automation and have to select one or more suitable tools</span> | ||
<br /> | <br /> | ||
| − | =<span style="font-family: Arial; font-size: 16px">Questions</span>= | + | =<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>= |
<br /> <span style="font-family: Arial; font-size: 16px">Since how long are you using your current tool?</span><br /> <span style="font-family: Arial; font-size: 16px">Who is using the tool?</span><br /> <span style="font-family: Arial; font-size: 16px">What automation architecture are you using?</span> | <br /> <span style="font-family: Arial; font-size: 16px">Since how long are you using your current tool?</span><br /> <span style="font-family: Arial; font-size: 16px">Who is using the tool?</span><br /> <span style="font-family: Arial; font-size: 16px">What automation architecture are you using?</span> | ||
| − | =<span style="font-family: Arial; font-size: 16px">Resolving Patterns</span>= | + | =<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>= |
| − | <br /> <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> <span style="font-size: 16px">[[ | + | <br /> <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> <span style="font-size: 16px">[[MIX APPROACHES]]: This pattern helps you recognize what is best done with a tool and what not</span><br /> <span style="font-size: 16px">[[RIGHT TOOLS]]: Apply this pattern when you select a tool to start with test automation or when you want to change the currently used tool</span><br /> <span style="font-size: 16px">[[TEST AUTOMATION FRAMEWORK]]: consider this pattern when you need to coordinate the different tools that you are currently using</span><br /> <br /> <span style="font-family: Arial; font-size: 16px">Other useful patterns:</span><br /> <span style="font-size: 16px">[[LEARN FROM MISTAKES]]: this pattern helps you turn bad experiences into learning experiences</span><br /> <span style="font-size: 16px">[[MANAGEMENT SUPPORT]]: this pattern will help you get the necessary support to get the RIGHT TOOLS</span><br /> <span style="font-size: 16px">[[PREFER FAMILIAR SOLUTIONS]]: use this pattern if a possible tool is already used / known in your company</span><br /> <span style="font-size: 16px">[[SELL THE BENEFITS]]: use this pattern, when you have selected a tool to show it's advantages over other ones</span><br /> <span style="font-size: 16px">[[SIDE-BY-SIDE]]: This pattern helps when having to pick a tool from a larger selection</span><br /> <span style="font-size: 16px">[[TESTABLE SOFTWARE]]: apply this pattern when starting with test automation</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span></div> |
Revision as of 10:46, 29 April 2018
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
Most recommended:
MIX APPROACHES: This pattern helps you recognize what is best done with a tool and what not
RIGHT TOOLS: Apply this pattern when you select a tool to start with test automation or when you want to change the currently used tool
TEST AUTOMATION FRAMEWORK: consider this pattern when you need to coordinate the different tools that you are currently using
Other useful patterns:
LEARN FROM MISTAKES: this pattern helps you turn bad experiences into learning experiences
MANAGEMENT SUPPORT: this pattern will help you get the necessary support to get the RIGHT TOOLS
PREFER FAMILIAR SOLUTIONS: use this pattern if a possible tool is already used / known in your company
SELL THE BENEFITS: use this pattern, when you have selected a tool to show it's advantages over other ones
SIDE-BY-SIDE: This pattern helps when having to pick a tool from a larger selection
TESTABLE SOFTWARE: apply this pattern when starting with test automation
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
Issue summary
The tools that are currently used are not appropriate for the Software Under Test (SUT) or are not supported any longer or you still don't have adequate tools.
Category
Management
Examples
- The test automation tool that you are currently using is not supported any longer.
- Development has implemented in the SUT components that are not supported (well) by your current tool
- The only person that could use the current tool left the company
- You want to start with test automation and have to select one or more suitable tools
Questions
Since how long are you using your current tool?
Who is using the tool?
What automation architecture are you using?
Resolving Patterns
Most recommended:
MIX APPROACHES: This pattern helps you recognize what is best done with a tool and what not
RIGHT TOOLS: Apply this pattern when you select a tool to start with test automation or when you want to change the currently used tool
TEST AUTOMATION FRAMEWORK: consider this pattern when you need to coordinate the different tools that you are currently using
Other useful patterns:
LEARN FROM MISTAKES: this pattern helps you turn bad experiences into learning experiences
MANAGEMENT SUPPORT: this pattern will help you get the necessary support to get the RIGHT TOOLS
PREFER FAMILIAR SOLUTIONS: use this pattern if a possible tool is already used / known in your company
SELL THE BENEFITS: use this pattern, when you have selected a tool to show it's advantages over other ones
SIDE-BY-SIDE: This pattern helps when having to pick a tool from a larger selection
TESTABLE SOFTWARE: apply this pattern when starting with test automation
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues