What is referred to as the 'test basis'?

The term 'test basis' refers to all documents from which requirements can be inferred. This includes any material that provides the information necessary to design test cases and to ensure that the testing is aligned with the intended functionality and quality expectations of the software. The test basis can consist of requirement specifications, design documents, user stories, or any other relevant documentation that contributes to the understanding of what needs to be tested.

Having a comprehensive test basis is crucial in Agile environments where requirements may evolve frequently. It ensures that the testing activities are grounded in solid documentation and that the testing team has a clear understanding of what is expected from the system being developed. By relying on the test basis, testers can create effective test cases that validate the software's compliance with user requirements and overall quality standards.

In contrast, documents specifying test case execution primarily focus on the process of how tests should be conducted rather than the information that informs what tests are needed. The final report on testing outcomes details the results after testing has been carried out, and the schedule of testing activities outlines the timeline for when tests will occur. While these elements are important in the testing process, they do not constitute the foundational information from which testing requirements are derived.