Chapter 6 • 20 minutes
Test Tools
Categories of test tools, their benefits and risks, and considerations for introducing them into an organization.
6.1 Tool Support for Testing
Test tools support one or more test activities. Common categories:
- Test management — manage testware, traceability, reporting (e.g. Jira/Zephyr, TestRail, Xray).
- Static testing — static analysis, code review aids (e.g. SonarQube, ESLint).
- Test design and implementation — generate test cases, test data, set up environments.
- Test execution and coverage — unit test frameworks, BDD/UI automation, coverage measurement (e.g. JUnit, Cypress, Playwright, Selenium, JaCoCo).
- Non-functional — performance, security, accessibility (e.g. JMeter, k6, OWASP ZAP).
- DevOps — CI/CD pipelines, containerization, infrastructure as code (e.g. Jenkins, GitHub Actions).
- Collaboration — wikis, chat, defect tracking.
- Specialized — fault seeding, mobile, IoT, accessibility.
6.2 Benefits and Risks of Test Automation
Benefits
- Reduces repetitive manual work and saves time.
- Greater consistency and repeatability.
- Earlier and more objective assessment of system state.
- Faster feedback in CI/CD.
- Allows running tests that are impractical manually (load, large data sets).
Risks
- Unrealistic expectations of what automation will deliver.
- Underestimating maintenance effort of automated tests.
- Over-reliance on automated tests; missing exploratory insight.
- Flaky/brittle tests reducing trust.
- Initial cost, learning curve, and tool licensing.