Which category BEST describes a tool used to generate test data based on rules?

Test data preparation tool — Test data preparation tools generate test data (for example, based on database structure or business rules) so tests can run against realistic data. (CTFL v4.0 – Section 6.1)

Continuous integration typically requires which of the following types of test tool?

Automated test execution and build/deployment tools — CI relies on automated builds, automated tests (unit, component, integration) and deployment automation, so changes are validated with every commit. (CTFL v4.0 – Section 6.1)

A potential RISK of introducing test automation is:

Unrealistic expectations of the tool's capabilities and underestimating maintenance effort — Common risks include unrealistic expectations about what a tool can do, underestimating the effort to maintain automated test assets, and over-reliance on the tool. (CTFL v4.0 – Section 6.2)

Before rolling out a new test tool organisation-wide, ISTQB recommends running a:

Pilot project to evaluate fit, benefits and effort — A pilot project evaluates the tool in a controlled setting: does it deliver expected benefits, integrate with existing processes, and what training/support is needed. (CTFL v4.0 – Section 6.2)

Which of the following is a benefit of using a test management tool?

It provides traceability between requirements, tests, and defects, plus reporting on progress — Test management tools provide traceability (requirements ↔ tests ↔ defects), track execution status, and produce metrics/reports on test progress. (CTFL v4.0 – Section 6.1)

Which of the following is a category of tools that support test design?

Model-based testing tools — Test design tools include model-based testing tools that generate tests from models, and tools that build tests from requirements/decision tables. (CTFL v4.0 – Section 6.1)

Test management tools primarily support:

Managing test cases, tracking execution status and providing metrics/traceability — Test management tools store test cases, track execution, link defects and requirements, and produce reports/metrics. (CTFL v4.0 – Section 6.1)

Which category BEST fits Selenium, Playwright and Cypress?

Test execution tools (UI automation) — Selenium, Playwright and Cypress are test execution (automation) tools that drive the application through its user interface. (CTFL v4.0 – Section 6.1)

Performance testing tools typically:

Generate load, measure response times and produce performance reports — Performance testing tools generate simulated load, measure throughput and response times, and produce performance/scaling reports. (CTFL v4.0 – Section 6.1)

Defect tracking tools support:

Recording defects, tracking their status, and reporting defect metrics — Defect tracking tools store defects, workflow their status, and produce reports (age, severity distribution, closure rates). (CTFL v4.0 – Section 6.1)

Continuous integration tools such as Jenkins or GitHub Actions primarily:

Automatically build, test and deploy code on every commit — CI tools trigger automated builds, tests and deployments on every source commit — enabling fast feedback. (CTFL v4.0 – Section 6.1)

A potential BENEFIT of test automation is:

Reduced repetitive manual test effort and faster feedback in the CI pipeline — Automation reduces repetitive manual effort, gives faster feedback on regressions and improves consistency of execution. (CTFL v4.0 – Section 6.2)

Which is a common RISK of over-relying on automation?

Automated tests may become brittle and require significant maintenance, and manual exploratory insights may be lost — Automation adds maintenance cost and cannot replace exploratory thinking; over-reliance can hide UX/usability issues. (CTFL v4.0 – Section 6.2)

When selecting a test tool, an organisation should:

Evaluate fit-for-purpose, vendor support, learning curve and integration with existing tooling — Tool selection should consider technical fit, cost of ownership, vendor support, learning curve, integrations and organisational maturity. (CTFL v4.0 – Section 6.2)

A pilot project for a new test tool is used to:

Test the tool in a limited, realistic context to assess benefits and effort before rollout — A pilot evaluates the tool in a limited but realistic environment, generating evidence for a broader rollout decision. (CTFL v4.0 – Section 6.2)

Which is a success factor for introducing a test tool?

Providing training and coaching, and integrating the tool into daily processes — Successful tool introduction requires training, coaching, incremental rollout, and integration with development/test processes. (CTFL v4.0 – Section 6.2)

Which tool category provides evidence of code coverage achieved during dynamic tests?

Coverage measurement tools — Coverage measurement tools instrument code (or run alongside tests) and report which statements, branches or paths were exercised. (CTFL v4.0 – Section 6.1)

Which of the following is a security testing tool category?

Static application security testing (SAST) and dynamic application security testing (DAST) tools — Security tooling includes SAST (analyses source code for security defects) and DAST (runs against a deployed system looking for exploitable weaknesses). (CTFL v4.0 – Section 6.1)

Test scripts stored in version control alongside application code is an example of:

Applying configuration management to testware — Storing testware (scripts, data) in version control alongside application code is a good application of configuration management to testing. (CTFL v4.0 – Section 6.2)

Which of the following BEST describes model-based testing tools?

Tools that generate test cases from a model of expected behaviour — Model-based testing tools generate test cases automatically from a model of expected system behaviour, ensuring systematic coverage. (CTFL v4.0 – Section 6.1)

ISTQB · CTFL v4.0 · Chapter 6

ISTQB Chapter 6 Sample Questions – Test Tools (CTFL v4.0 · 2026)

Chapter 6 covers tool support for testing: categories of test tools, potential benefits and risks of test automation, and the special considerations for successfully introducing a tool into an organisation (including running a pilot project).

Twenty CTFL v4.0-style questions below — tap any question to reveal the correct answer, a plain-English explanation and a syllabus reference. Key terms link through to the ISTQB glossary.

Test automation Test tool Test data preparation Continuous integration Pilot project