Test results
1. After two stages before and after several rounds of testing, although some defects left unresolved, but the system function has stabilized, and the project to determine the scope, strategies and plans have been achieved, the test project can end, xx-1.1 can online.
2. Test that subsequent versions of the product to be further improvements in the user experience, the user does not exclude the "halo" feeling when using this product.
Presented a problem
1. demand. In particular xx-1.0 project demand, although demand gradually see a lot of documents, but these documents gives the impression that: incomplete requirements analysis, requirements specification is not clear, logical requirements document readability, realizability, can testing is rather poor, demand greater ambiguity. In order to feel whole xx-1.0 testing constantly tap the demand, identify needs, changing demand and needs assessment. xx-1.1 project requirements has been greatly improved, xx itself and needs through the collection, analysis, validation and review process, but the demand for each interface products is still not unified analysis, validation and evaluation, this part of the demand of ambiguity of larger and more changes throughout the readability of the requirements document, testability, integrity and clarity remains poor.
2. Change control problem. This reflects the more obvious during the test xx-1.0, the project needs change as the project responsible for changes, such as changes to the project plan. xx-1.0 throughout the test has not been confirmed and the change in the statute needs and requirements change mechanism, a meeting, a mail or a verbal communication needs may change. xx-1.1 testing this problem has been good improvement, but poor change control of the implementation of the statute. All the changes are not timely needs a good update to the requirements document, xx-1.0 reflect the more obvious.
3. version control issues. xx-1.0 testing process failed to carry out version management; xx-1.1 code xx testing process itself was version management, product code each interface are managed by each person responsible for the technical, appeared in this period had covered code case, the code is missing or forgetting to upload deployment. Difficult to ensure a clear round test version, and release version and the beta version of consistency.
4. Test environment. Test and development environments could not very well separated during the test xx-1.1, resulting in testing and development can not repair defects in parallel; there are development engineers to repair defects during the test and modify the test environment directly on the test environment situation; the test environment is unstable, as hosts settings are not correct and so on.
The project owes a clear, staff responsibilities unclear.
Testing recommendations
1. legacy defects. Recommended way to patch, or resolve the remaining defects in subsequent editions after xx-1.1 on the line, in order to improve product stability and user experience.
2. It is recommended requirements. Xx itself or whether each interface products, it is recommended to further strengthen the requirements gathering, analysis, validation and review process, to further improve the quality of requirements document: reduce ambiguity needs to enhance the integrity requirements, clarity of description, consistency, readability can be achieved and testability. At the same time recommendations will review the design documents (such as UI / UE, etc.) in subsequent projects to enhance the usability of products to enhance the user experience.
3. Change Control. Change control strategy recommended further strengthen and develop the Statute of subsequent projects, change control and strengthen the implementation of the statute. Not afraid of change, the key to control the timing and good strategy changes.
4. version control. Xx strengthen itself, especially the version of the product for each interface control strategy to ensure the clarity of the test version, released on-line version and the final version of the conformance test /.
5. Test environment. Xx expected in subsequent projects completely separate interface products and various test environment and development environment, or the stage is completely independent, and each part of the environment have a special person in charge of the interface, during the test is strictly prohibited to repair defects in the test environment or change the environment configuration (if they really need to change the configuration, please notify the test and other relevant person in charge). In order to reduce communication so bring the cost of repeated detection.
6. Project management. The main recommendation is to strengthen the planning of the project, such as: scheduling, human resource planning, risk prevention mechanisms, which will be conducive to efficient coordination between project members: we can be more timely, more reasonable plan to develop their own work, but also to more clearly when I'll output what I will with what others do. Reduce project progresses tension and confusion, the project has become more controllable and easy to control.