testbasis

Test basis is a concept in software testing describing the information from which tests are derived. It comprises the sources that define what should be tested and why, serving as the foundation for test design and planning. The test basis can include requirements specifications, functional and nonfunctional requirements, user stories and use cases, design and architectural documents, interfaces and data models, risk analyses, regulatory and standards documents, test policies, and historical defect reports or test results. The content and completeness of the test basis determine the scope of testing, influence test techniques, and support traceability from requirements to test cases.

Purpose and use: Test designers derive test cases, test data, and test procedures from the test basis. A well-defined test basis helps ensure coverage of intended functionality, quality attributes, and constraints, and supports validation and verification activities. It also serves as a reference to assess test completeness and to identify gaps where additional tests are needed.

Establishing and maintaining: The test basis should be identified early and baselined; changes should be tracked through configuration management. A traceability matrix can link each test case to one or more basis items. Validation by stakeholders confirms that the basis accurately reflects the product and its requirements. In practice, several items can form the basis, and their relevance may evolve during the project.

Relation to other concepts: The test basis is not the same as the test oracle, which provides the expected result for a given test. Tests may be derived from multiple basis items, and risk-based prioritization can influence which basis items are tested first.