Test Tools Purposes
- Improve the efficiency of test activities by automating repetitive tasks or tasks that require significant resources when done manually
- Improve the efficiency of test activities by supporting manual test activities throughout the test process
- Increase reliability of testing
Intrusive Tools
- May affect the actual outcome of the test
- The consequence of using intrusive tools is called the probe effect
Tool support for management of Testing
- ALM tools
- Defect Management Tools
- Configuration Management Tools
- Requirements Management Tools
- Configuration Integration Tools (D) → This means that this is a testing tool, but it is used by developers or designers
Tool support for Static Testing
- Static analysis tools
- Reviews tools
Benefits of Test Execution Tools
- Reduction in repetitive manual work, thus saving time
- Greater consistency and repeatability
- More objective assessment
- Easier access to information about testing
Risk of Test Execution Tools
- Unrealistic expectations of the tool
- Underestimating time, cost, and effort for the initial introduction of a tool and also to achieve significant benefit from it
- The tool may have relied on too much
- A new platform or technology may not be supported by the tool
- Relationships and interoperability issues between critical tools may be neglected
Capture Replay Tools
- Selenium IDE
- Katalon Recorder
- Capturing tests by recording the actions of a manual tester seems attractive, but this approach does not scale to large numbers of test scripts
- A captured script is a linear representation
Data-drive Testing
Approach separates out the test inputs and expected results, usually into a spreadsheet, and uses a more generic test script that can read the input data and execute the same tests script with different data
Keyword-driven Testing
- A generic script processes keywords describing the actions to be taken, which then calls keyword scripts to process the associated test data
- Testers can then define tests using the keywords and associated data.
Model-based Testing
- Flow chart
- Is generally performed by a system designer
Which of the following is one of the purposes for using “test tools”?
→ Increase the reliability of testing
Considerations for Tool Selection
- Consideration of whether or not the tool is available for a free trial period
- Evaluation of the vendor
- Identification of coaching, mentoring, and training needs
- Consideration of pros and cons of various licensing models
- Estimation a cost-benefit ratio
Pilot Project
- Introducing the selected tool into an organization generally starts with a pilot project
- Gaining knowledge about the tools
- Evaluating how the tool fits with existing processes and practices
Success Factors for Tools
- Rolling out the tool to the rest of the organization incrementally
- Adapting an improving process to fit with the use of the tool
- Providing training
- Defining guidelines for the use of the tool
You have just completed a pilot project for a regression testing tool. You understand the tool much better and have tailored your testing process to it. You have standardized an approach to using the tool and its associated work products.
Which of the following is a typical goal of test automation pilot project that remains to be carried out?
→ Assess whether the benefits will be achieved at reasonable cost
Which of the following is MOST likely a reason for using a pilot project to introduce a tool into an organization?
→ The need to evaluate how the tool fits with existing processes and practices and determining what would need to change.
