...
Test design includes specification of requirements with conditions for their fulfillment. The conditions may also be contextual and include repeatability or presentability. It is followed by specification of individual tests cases and procedure for their execution. The subsequent steps are test environment set-up, test execution and related reporting. The feedback from environment set-up and execution may lead to an update of the original design. For example, the constraints in capabilities of the test environment may lead to the update of test cases. Alternatively, actual preparation of test cases and environment may require additional elaboration and refinement of test cases. On the other hand, significance/priority of some requirements may lead to modification of the test environment in order to enable execution of corresponding test cases. Both will lead to modification of the test procedure.
In parallel: Monitor , monitoring of test progress is performed on the base of test status and related measures/metrics/reports), report stakeholders recieve reports on test status to stakeholders, and issue control/correction directives are issued and perform corrective/adaptive actions are made for/on the test design, environment, execution, and perhaps even evaluation level test plan. Can be done in a single flow or iteratively.
Possibly The test enactment may also provide suggestions or inputs for the update updates of the general Testing and Validation Process and Strategy.
...
On the common industry practices and with the strong influence from IEEE 829, and its sequel/update ISO/IEC/IEEE 29119-3, which even provides even templates for both traditional (sequential and iterative) and agile approaches.
All docments documents should start the following common elements (metadata):
- Organizational numeric identifier of the document
- Descriptive identifying name
- Version number
- Authors and their contacts
- Version history (table with version numbers, dates, contributors and descriptions of changes)
...
Evaluation Level Documentation
For Evaluation Level Documentation are the elements of documentation related to testing of as a specific service, product or solution that are intended for communication between those responsible for test management processes (planning, monitoring and control, and completion assessment) and those who actually perform (design, implement, execute and document) the planned tests.On the base of of status and completion reports, control and correction directives are issued which lead to corrective or adaptive actions and changes in test level documentation or even the test plan.
- Test Plan
- Test Status Report
- Test Completion Report
...