...
- Test Design Specification
- Test Case Specification
- Test Data Requirements
- Test Data Report
- Test Environment Requirements
- Test Environment Report
- Detailed test results (base for status and completion reports on the base of individual tests execution logs and anomalies/incidents reports)
Test Plan
Test Plan: A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. Ref IEEE Std 829.
Test Environment or Test Bed is an execution environment configured for testing. It may consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, test tools, etc. The Test Plan for a project should enumerated the test beds(s) to be used.
...
Scenario Testing is a higher level approach to testing of complex systems that is not based on Test Cases, but on working through realistic and complex stories reflecting user activities. These stories may consist of one or several user stories,which capture what a user does or needs to do as part of his or her job function, expressed through one or more sentences in the everyday or domain language. The tester who follows the scenario must interpret the results and evaluate whether they can be considered as a pass or failure. This interpretation may require backing by domain experts. This term should be distinguished from Test Procedure and Test Case scenario.
...
The Test Script is a sequence for instructions that need to be carried out on the tested system in order to execute a test case, or test a part of system functionality. These instructions may be given in the form suitable for manual testing or, in automated testing, as short programs written in a scripting or general purpose programming language. For software systems or applications, there are test tools and frameworks that allow specification and continuous or repeatable execution of prepared automated tests.
Traceability Matrix is a table or standalone document matching Requirements and Test Cases, thus ensuring their mutual association and coverage. It enables both forward and backward traceability, as it simplifies how the test cases need to be modified upon the change of requirements, and vice versa. It is used to verify whether all the requirements have corresponding test cases, and to identify for which requirement(s) a particular test case has been written for. Columns REQS, rows Tests Cases.
Test Data Requirements
Test Data Report
Test Environment Requirements
Test Environment Report
Detailed test results
(base for status and completion reports on the base of individual tests execution logs and anomalies/incidents reports)
(Test records - for each test, an unambiguous record of the identities and versions of the component or system under test, the test specification and actual outcome.)
The Test Log is the record of Test Cases execution and obtained results, in the order of their running.