Test Techniques
The systematic methods our 50+ QA engineers use to design and implement tests, combining black-box, white-box, and experience-based approaches for maximum coverage.
Short answer
Test techniques are the methods testers use to decide which tests to run. They fall into three families: black-box techniques that work from the requirements (equivalence partitioning, boundary value analysis, decision tables, state transitions, use cases), white-box techniques that work from the code (statement and branch coverage), and experience-based techniques (error guessing, exploratory testing, checklists). Most projects combine all three. Worked examples are in our test cases guide.
Overview
Some test techniques apply more to specific situations and test levels; others apply to all test levels. When creating test cases, testers generally use a combination of test techniques to achieve the best results from the test effort.
The use of test techniques in test analysis, design, and implementation can range from very informal to very formal. The appropriate level of formality depends on the testing context, including process maturity, time constraints, regulatory requirements, and team skills.
Types of Test Techniques
Black-Box
Based on analysis of the test basis, concentrating on inputs and outputs without reference to internal structure. Applicable to both functional and non-functional testing.
White-Box
Based on analysis of architecture, detailed design, internal structure, or code. Concentrates on structure and processing within the test object.
Experience-Based
Leverages the experience of developers, testers, and users. Helps identify tests not easily found by systematic techniques. Coverage may vary based on tester approach.
Formality Depends On
The appropriate level of formality when applying test techniques depends on the testing context:
Need Testing Expertise?
Our ISTQB-certified engineers apply the right combination of techniques for your project context and quality objectives.