INADEQUATE TOOLS

From Test Automation Patterns
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
.................................................................................................................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

  1. The test automation tool that you are currently using is not supported any longer.
  2. Development has implemented in the SUT components that are not supported (well) by your current tool
  3. The only person that could use the current tool left the company
  4. 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