ISTQB Test Management Glossary for QA Pros

Testing is more than executing test cases or logging bugs – it’s about managing a structured process that ensures quality, transparency, and accountability throughout the software lifecycle. To make this process effective, teams need a shared language: a consistent set of terms that every tester, developer, and product owner understands the same way.

The ISTQB (International Software Testing Qualifications Board) glossary provides that common ground. It is the international reference for how professionals define, organize, and communicate about testing. Below is a practical explanation of 25 key ISTQB test management terms, enriched with real-world context and relevance for today’s Agile and DevOps teams.

1. What is Test Policy?

A test policy defines an organization’s overall philosophy toward quality and testing. It explains why testing matters, which standards must be upheld, and how testing supports business goals. A strong test policy aligns all projects under a shared quality vision, such as prioritizing defect prevention or treating automation as a strategic investment.

2. What is Test Strategy?

A test strategy describes how the test policy is implemented across the organization. It defines test levels (unit, integration, system, acceptance), methods (manual, automated), and guiding principles like risk management and coverage objectives. A consistent strategy ensures teams test in compatible ways.

3. What is Test Approach?

A test approach adapts the test strategy to a specific project. It reflects the project’s risks, tools, timelines, and system architecture—for example, emphasizing API testing in backend-heavy systems or exploratory testing for new user interfaces.

4. What is a Test Plan?

A test plan is the operational roadmap for testing. It defines what will be tested, how, when, by whom, and with which resources. Effective test plans include objectives, scope, deliverables, metrics, risks, and contingency plans. In Agile environments, test plans are often living documents that evolve with each sprint.

5. What is Test Planning?

Test planning is the activity of creating and refining the test plan. It includes defining success criteria, estimating effort, selecting test levels, and scheduling activities. Test planning is a collaborative process that aligns testing with business and release goals.

6. What is Test Monitoring?

Test monitoring tracks progress against the test plan using metrics such as execution rates, defect trends, and pass/fail ratios. Monitoring helps teams detect deviations early and respond before issues impact delivery.

7. What is Test Control?

Test control involves taking corrective actions based on monitoring results. This may include adjusting scope, reallocating resources, or reprioritizing tests to keep testing aligned with project goals.

8. What is Test Analysis?

Test analysis determines what should be tested. Testers review requirements, designs, and risks to identify test conditions—specific behaviors or features that must be validated. Good analysis bridges business expectations and technical implementation.

9. What is Test Design?

Test design transforms test conditions into detailed test cases. Testers define preconditions, inputs, steps, and expected results, and apply techniques such as boundary value analysis or decision tables to maximize coverage.

10. What is Test Implementation?

Test implementation prepares test assets for execution. This includes creating test data, configuring environments, and developing automated scripts. The goal is to ensure test cases are executable, traceable, and ready for use.

11. What is Test Execution?

Test execution is the process of running test cases, recording outcomes, and logging defects when actual results differ from expectations. Execution requires discipline, observation, and clear communication to provide meaningful feedback.

12. What is Test Completion?

Test completion marks the formal end of testing activities. Teams evaluate results against exit criteria, summarize outcomes, archive testware, and capture lessons learned to improve future testing efforts.

13. What is the Test Basis?

The test basis is the source of information used to derive tests. It may include requirements, user stories, architecture diagrams, risk assessments, and stakeholder input. A clear test basis reduces ambiguity and supports effective analysis.

14. What is a Test Condition?

A test condition is a testable aspect of the system, such as a function, workflow, or business rule. Test conditions help structure and prioritize testing activities.

15. What is a Test Case?

A test case specifies steps, data, and expected outcomes for verifying a single test condition. Well-written test cases are clear, reusable, and traceable, serving as both validation tools and documentation.

16. What is a Test Procedure (or Script)?

A test procedure describes how to execute one or more test cases, including setup and cleanup steps. Automated test scripts are technical implementations of these procedures.

17. What is a Test Suite?

A test suite is a collection of related test cases grouped by purpose, feature, or release. Examples include regression, smoke, or acceptance test suites.

18. What is Testware?

Testware encompasses all testing artifacts, including plans, cases, scripts, data, environments, and reports. It represents the tangible output of testing activities.

19. What is a Test Environment?

A test environment is the controlled setup where testing occurs. It includes hardware, software, configurations, and network settings that ideally mirror production to ensure reliable results.

20. What is Test Data?

Test data consists of input values used during testing. It may be real or synthetic and is designed to validate normal behavior, edge cases, and error conditions.

21. What are Entry Criteria?

Entry criteria define the conditions that must be met before testing can begin, such as environment readiness or completed requirements. They help prevent premature or ineffective testing.

22. What are Exit Criteria?

Exit criteria specify when testing can stop. Examples include achieving a target execution rate or resolving all critical defects. Exit criteria provide a clear definition of done for testing.

23. What is Traceability?

Traceability links requirements, test cases, executions, and defects. It ensures that all business needs are validated and supports impact analysis, compliance, and audits.

24. What is Test Coverage?

Test coverage measures how much of the test basis or system has been exercised by tests. High coverage increases confidence but does not guarantee defect-free software.

25. What is Risk-Based Testing?

Risk-based testing prioritizes tests based on the likelihood and impact of failures. It helps teams focus effort on the most critical areas of the system.

From Theory to Practice

Understanding ISTQB terminology is important, but applying it consistently is what improves testing maturity. Teams that share a common testing language collaborate more effectively, plan better, and communicate results more clearly.

Bringing It All Together with Appsvio Test Management for Jira

To apply these concepts in practice, QA teams need a centralized solution to manage test assets and execution. Appsvio Test Management (ATM) for Jira embeds ISTQB-aligned concepts—test plans, cases, executions, environments, and traceability—directly into Jira workflows.

With ATM, teams can:

• Build and manage test cases linked to user stories
• Track coverage and execution progress in real time
• Maintain full traceability between requirements, tests, and defects
• Generate structured, audit-ready reports