Loading...
Posted date
Overall test plan guide
Table of contents
- Overview
- Contents
- 1.About this document
- 1.1. Purpose
- 1.2. Concept
- 1.3. Targets
- 1.4. How to use this document
- 2. About overall test plans
- 2.1. About overall test plans
- 2.2. Why an overall test plan is needed?
- 2.3. Consideration time
- 2.4. Points to be considered
- 3.Points to be confirmed before considering the overall test plan
- Information in the project
- Information outside the project
- 4.Explanation of topics that need to be considered
- Topics that need to be considered
- 4.1.Test policies
- Overview of points to be considered
- Consideration method
- Reference
- 4.2. Position of test phases
- Overview of points to be considered
- Consideration method
- Reference
- 4.3. Coverage policies
- Overview of points to be considered
- Consideration method
- Reference
- 4.4. Scope of testing
- Overview of points to be considered
- Consideration method
- Reference
- 4.5. Test environments
- Overview of points to be considered
- Consideration method
- Reference
- 4.6. Team structure
- Overview of points to be considered
- Consideration method
- Reference
- 4.7. Tasks and allocation of roles
- Overview of points to be considered
- Consideration method
- Reference
- 4.8.Schedule
- Overview of points to be considered
- Consideration method
- 4.9.Management policies
- Overview of points to be considered
- Consideration method
- 5.Position of overall test plan
- Overview of points to be considered
- Consideration method
- 6. Sources
4.9.Management policies
When carrying out test control, you need to manage the status of the QCD, project and test targets, correctly assess the current status and make improvements.
In this topic, you will consider on various management methods and processes that need to be agreed on before starting testing.
In many cases, these points are also considered in the project plan. This chapter compiles points that need to be considered when implementing tests.
Overview of points to be considered
Confirm the management methods that will be used for the points that need to be managed during testing.
Relationship between this topic and other topics in the overall test plan
This topic is not closely related to any other topics.
Consideration method
In many cases, the scope of this consideration is the project as a whole, and these points are considered in the project plan, which means they may not need to be included in the overall test plan.
You will, however, need to check that the following points concerning management are considered.
- Progress management
- Check that pre-testing activities are considered and progress can be managed and reported based on results.
For example, when creating test cases or test scenarios, it should be possible to measure progress based on the number that have been created and the number that remain. - Check that the progress on activities that take place after testing starts and the results generated by tests can be measured and reported.
For example, it should be possible to measure progress based on the following.- The number of test cases or test scenarios that have been executed and those that remain. Retesting in the event of a bug or a specification change must also be considered.
- Number of detected bugs, bug resolution schedule and results.
- Check that pre-testing activities are considered and progress can be managed and reported based on results.
- Quality control
- The methods for evaluating quality during testing and the preparations required for those evaluations (measurement of quality indicators, etc.) must be established.
- Management of bugs
- The processes for determining the priority order of bugs detected in testing and then fixing those bugs must be established.
- Information on test cases and reproduction procedures must be managed as a set so that bugs can be reproduced.
- Configuration management
- The configuration must be managed so that the test results can be checked and reproduced at certain times, such as when a bug is detected or when a specific test finish.
For example, materials related to the test target program, the test cases and test environment required for testing, the design specifications used as input for the test cases, evidence and whether each test case passes or fails must be managed as a set. - It is necessary to establish which materials (from which time) will be used in specific phases and the tests conducted in those phases (performance tests, operational scenario tests, etc.)
This is necessary to confirm the version of the program being released in the test environment and the design specifications being used as input for the test cases that should be used.
- The configuration must be managed so that the test results can be checked and reproduced at certain times, such as when a bug is detected or when a specific test finish.
- Change management
- It must be presumed that any accepted changes to the specifications will be accompanied by an investigation of how those changes will affect test activities such as creating test cases and executing tests.
- Issue management
- Risk management
- Management of property of the user department
- If property such as test data, test environments or work areas is borrowed for testing, methods for handling and managing that property must be stipulated.
