Chapter 6 is the shortest chapter: 20 minutes of training and 2 exam questions. It explains the kinds of tools that support testing and the benefits and risks of test automation. Two easy marks if you learn the lists.
ISTQB CTFL › 6. Test Tools Syllabus v4.0.1 · updated 3 Nov 2026
| Exam weight | Questions | K-levels | Training time |
|---|---|---|---|
| 5% | 2 | 1 × K1, 1 × K2 | 20 minutes |
Keyword to remember (K1): test automation.
6.1 Tool support for testing (K2)
Tools support many test activities. The syllabus lists these categories:
| Tool type | How it supports testing | Examples you may know |
|---|---|---|
| Test management tools | Make the test process more efficient by managing the SDLC, requirements, tests, defects and configuration | Test case and defect trackers |
| Static testing tools | Support reviews and static analysis | Linters, code analysers, review tools |
| Test design and implementation tools | Help generate test cases, test data and test procedures | Test data generators, model-based test generators |
| Test execution and coverage tools | Run tests automatically and measure coverage | Selenium, Playwright, pytest, coverage tools |
| Non-functional testing tools | Make non-functional testing possible when it is difficult or impossible manually | Load and performance tools, security scanners |
| DevOps tools | Support the delivery pipeline, workflow tracking, automated builds and CI/CD | CI servers, pipeline runners |
| Collaboration tools | Make communication easier | Chat, wikis, shared boards |
| Scalability and deployment standardisation tools | Provide consistent, repeatable environments | Virtual machines, containers |
| Any other tool that assists testing | Even general tools count when used for testing | A spreadsheet used to track tests is a test tool |
K2 questions usually describe what a tool does and ask for its category, for example “a tool that simulates 5,000 concurrent users” → non-functional testing tool; “a tool that flags unused variables without running the code” → static testing tool.
6.2 Benefits and risks of test automation (K1)
Buying a tool does not guarantee success. Every tool needs effort to introduce, maintain and train people on, and its risks must be analysed and mitigated.
| Potential benefits | Potential risks |
|---|---|
| Saves time on repetitive manual work: running regression tests, re-entering the same test data, comparing expected and actual results, checking coding standards | Unrealistic expectations about what the tool can do and how easy it is |
| Prevents simple human errors through consistency and repeatability: tests derived consistently, test data created systematically, tests run in the same order and frequency | Inaccurate estimates of the time, cost and effort to introduce the tool, maintain scripts and change the manual process |
| More objective assessment (for example coverage) and measures too complex for humans to calculate | Using a tool when manual testing is more appropriate |
| Easier access to test information for management and reporting: statistics, graphs, aggregated progress, failure rates and execution times | Relying on the tool too much and ignoring human critical thinking |
| Faster test execution, giving earlier defect detection, faster feedback and faster time to market | Vendor dependency: the vendor may go out of business, retire or sell the tool, or give poor support |
| More time for testers to design new, deeper and more effective tests | Open-source risks: the project may be abandoned, or its components may need frequent updates |
| The tool is not compatible with the development platform | |
| The tool does not comply with regulatory or safety standards |
Benefits are about time, consistency, objectivity, information, speed and freeing testers. Risks are about expectations, estimates, wrong use, over-reliance, vendors, open source, compatibility and compliance.
Learning objectives checklist
| LO | Level | You should be able to… |
|---|---|---|
| FL-6.1.1 | K2 | Explain how different types of test tools support testing |
| FL-6.2.1 | K1 | Recall the benefits and risks of test automation |
Chapter 6 self-check (6 questions)
A team uses a tool to simulate thousands of users to measure response times. Which type of tool is this?
- A. Static testing tool
- B. Test management tool
- C. Non-functional testing tool
- D. Collaboration tool
Show answer
Answer: C. Non-functional testing tool
Non-functional testing tools allow testing that is difficult or impossible to do manually, such as load and performance testing.
Which type of tool supports reviews and static analysis?
- A. Test execution and coverage tools
- B. Static testing tools
- C. DevOps tools
- D. Test design and implementation tools
Show answer
Answer: B. Static testing tools
Static testing tools support the tester in performing reviews and static analysis.
Which tools help create consistent, repeatable test environments?
- A. Tools supporting scalability and deployment standardisation, such as containers
- B. Collaboration tools such as chat
- C. Static analysis tools
- D. Defect management tools
Show answer
Answer: A. Tools supporting scalability and deployment standardisation, such as containers
The syllabus lists virtual machines and containerisation tools as tools supporting scalability and deployment standardisation.
Which is a potential benefit of test automation?
- A. It removes the need for human critical thinking
- B. It reduces repetitive manual work such as re-running regression tests
- C. It always costs less than expected to introduce
- D. It makes vendor support unnecessary
Show answer
Answer: B. It reduces repetitive manual work such as re-running regression tests
Saving time on repetitive work is a listed benefit. Ignoring critical thinking and underestimating costs are listed risks.
Which is a potential risk of test automation?
- A. More objective coverage measurement
- B. Faster feedback on defects
- C. Unrealistic expectations about the tool’s functionality and ease of use
- D. More time for testers to design better tests
Show answer
Answer: C. Unrealistic expectations about the tool’s functionality and ease of use
Unrealistic expectations are a listed risk. The other options are listed benefits.
A team adopts an open-source automation library that stops receiving updates a year later. Which risk does this illustrate?
- A. Using a tool when manual testing is more appropriate
- B. Open-source software that may be abandoned
- C. Inaccurate estimation of the effort to introduce a tool
- D. Lack of compliance with safety standards
Show answer
Answer: B. Open-source software that may be abandoned
The syllabus lists the risk that open-source software may be abandoned, so no further updates are available.
You have finished the study material. Now test yourself with Sample paper 1, a full 40-question paper in the real exam split.