What it does
Classifies the need into an ISTQB tool category, scores 2–4 candidates against eight weighted criteria into a deterministic matrix, weighs benefits and risks, then recommends one option (or 'retain current tool') with a time-boxed pilot/PoC and numeric go/no-go success criteria. Uses web search for current candidates.
When to use it
When choosing a new testing tool or justifying the current toolchain. Feeds the Test Automation Strategy.
Prerequisites
qa.config.yml (run /qa:qa-init first) — paths, stack, tooling incl. ci.platform, gates, risk_areas. Uses WebSearch for current candidates.
Output
Tool Evaluation decision record (input to the Test Automation Strategy; no dedicated 29119-3 work product) -> <paths.docs_dir>/TOOL-EVALUATION-<category>.md.
Mechanics
How it works
- Config guard; resolve the need from args or default to the top tooling gap on risk_areas.critical
- Classify the need into one ISTQB tool category
- Define 8 weighted criteria (stack fit, language, CI/reporting, learning curve, cost, maintenance, community, lock-in)
- Survey 2–4 candidates (WebSearch); score each cell 1–5 and compute weighted totals
- Apply decision rules (≥10% lead, disqualify a 1 on a weight-5 criterion)
- List benefits and mitigated risks for the leader
- Recommend one option + a time-boxed pilot with numeric go/no-go criteria; write the record
Why it works
The theory behind it
The ISTQB tool-selection process (CT-TAE / Test Automation Strategy; generic tool support CTFL §6). Framed as an ROI/investment decision so the answer is never 'adopt every tool'; a tool does not replace test design or judgment (Principle 1).
CT-TAE · Test Automation Strategy · CTFL v4.0 §6
Example
See it in use
> /qa:tool-select "visual regression testing"✓ Correct when It lists candidates with benefits/risks, weighted scoring criteria, and a pilot recommendation tied to the matrix.
Related commands
Used by