Product test management in research and development management _ test Management

Projects in the analysis, design, implementation, after assembly, the test is tested as a test to determine whether the software designed to meet the functional requirements of the design, and its performance requirements and their hidden requirements play a significant role, as the final form of products, may be in some function or design defects, or the user's needs distorted design , can be found in the testing process, to be amended.

So from this point of view, we should pay attention to software testing, software testing is to improve the quality of software is an important means. According to some foreign development company's statistics, is generally designed: to achieve: The proportion of the tester input is 1:3:3, visible to the degree of attention to the test.

Then the test should also have the working method of testing, first of all to make a test plan, select the test model, develop good test cases, and then review. I think test case design is very important, test cases, to cover the function of the software, the general situation of the operation, special circumstances, explosion and other special operations, design use cases can also take into account the new bug. In short, good test cases, so that we can quickly discover the soft rib, reduce the duplication of work, reduce software defects in the dew.

Test case design is also an experience accumulation process, a good test engineer, must be able to identify some common defects, that is, some test cases are also reusable.

With test cases, we can go through these use cases to test our software products one after the other. Identify the defects, and then hand them over to the development team for revision, and then follow the test.

After we submit the test, generally based on the test, fixed some bugs or logic errors, resulting in a new version, and then submit a new version of the test, then in the middle of the wheel of the test, whether the coverage test every time, I personally think, if the first one or two rounds of testing more serious, That can be followed by a new version of the test program, you can discard the original version of the program, in a new version of the program to test, the test priority is to determine whether the bug is fixed, and then test the last version of the use cases, until all the tests are completed or a new version appears, and then discard the new version of the test.

After several rounds of test repair, and finally a full range of coverage testing, I think the software at this time the functional quality should be more assured.

The entire testing process is based on the requirements of the basic requirements of the test case for testing guidance.

This article is reproduced from the 51testing Software test network, see more: http://www.51testing.com/html/30/n-847730.html