The first step: evaluation and development program status
This first step is to create the W & T program prerequisites, W & T plan for assessing the implementation of software solutions. In this step, the tester can question the completeness and correctness of the development plan. And complete and extend the definition of project plans based testers test the software to estimate the amount of resources to address the implementation of the program required.
Step two: forming a test plan
Forming a test plan should be in line with the software development process model, the structure of all plans should be the same, will have content based on perceptions of the degree of testers in development projects.
The third step: testing software needs explanation
Incomplete, incorrect, or inconsistent with the requirements of software development will lead to failure. In the requirements gathering stage, incorrect description of software requirements, will significantly increase development costs. By testers verify, we must ensure that the needs explanation is correct, complete, and there will be no conflict.
Test software design Step four:
This step testers must first be able to verify through testing software technology exterior and interior design, test design is able to complete the requirements described in these design goals and can work on specific hardware.
Step five: Test the software development process
According to internal software development methodology design document selection will determine the type and scope of testing testers needed. Because the software builds become more automated, so this stage requires relatively little test, however, if the software using waterfall development model, prone to errors that should be found. Experience has shown that, identify problems and will save a lot of costs than found in dynamic testing problems during the construction phase.
Step Six: Implementation and recording error
This phase includes the dynamic state test code, the steps specified in the test plan, methods, tools will be used to verify compliance with the provisions of the executable code of the software requirements specification and structural design.
Step Seven: acceptance testing
Acceptance testing allows users to evaluate the software at the desired functional operation of their daily work applicability and availability. So that users can test the software should be considered to achieve what features and software requirements described in the document should realize what features contrast.
Step eight: Test results report
Test Report is an ongoing process, it can also be recorded verbal expression. Defects and problems related to the appropriate team would like to report, and the report to be easy to understand, this is very important. This would at the lowest possible cost to fix the problem.
Step 9: Software installation and testing
Once the test team has confirmed that the software is available for production use in a production environment, ability to execute the software will be tested. This will test the interface, software and operating procedures of the operating software.
Step 10: Test the software change
When performing the tenth step, the process is maintained after the software is installed using. With concepts throughout the implementation process to change at any time demand changes, the test plan should be changed accordingly, and these changes should affect the entire software testing and evaluation.
Step Eleven: efficiency assessment test
The best improvement in test by test tasks to complete the final stage of evaluation of test efficiency. This assessment should first be completed by the testers, but also including developers, software quality and professional users guarantor (if these people then).
I'm going to focus on coupons www.591q.cn