Test flow: How a version is tested on-line-functional testing

In the traditional software industry, each version of the iteration cycle is less than half a year, more than a few years. The final release of so many features in a release, how the test is guaranteed to be quality, I'll take a project version of my experience as a case, and tell the test process in this process.

We often say that tests need to be involved in the project as early as possible and start testing from the requirements. In this project, the requirements of the test, our side is for each of the requirements of the review, the specific responsible for the document testers are required to do the requirements of the review of the issue record tracking table, request needs to be reviewed in order to ask questions about the demand, unreasonable local requirements pointed out, After the review meeting, publish the requirement review questionnaire to the reviewers who participated in the document, with the result whether the review passed, or the need to re-review.

After the requirements document review is passed, the demand order is entered into the requirements pool and the desired version number of the demand order is specified. Then the design of the task order, the designer in the design of the demand list, will convene a design review meeting, the test should also participate in the design review, the design of each table structure, data design flow to clear, encountered problems to be pointed out on the spot. The design issue review record is filled out and published by the developer who is responsible for the document at this time.

After the design of a single review, the development of the task order will be generated, the development of the development of the document, the test is now based on the previous review of the requirements of the document, design documents as input for the test design. When we do the test design, we will design two kinds of test cases, one is the function test case, the other is the business scenario test case. And the function of the test cases, we tend to first through the mind map function points are split to form a functional tree, and then according to the test design method for the function of the test case design and fill in the use case template, we design the use case requires each design to the page to display the results of the data must be written in the SQL statement, The purpose of this is to test the clarity of the flow of data to the document, and to facilitate the execution of the test as quickly as it is performed. Test cases for a business scenario we first asked for a flowchart to be drawn with Visio, and then different process scenarios were designed according to the predefined input.

After the use case design, we will be based on the complexity of the requirements of the order to decide whether to conduct a conference review or a sign-off review, meeting review will often participate in the entire Test team, and invite the owner of the demand list, design and development leaders, each of our test cases for review , and the sign-off review is sent by email to the above members, the members through the local review and give a reply to the mail. After the use case review is passed, we will upload the use case to SVN for backup.

When the development completed the development of the document, at this time the requirements of personnel will be on the development of the machine to accept the document, the demand for acceptance of the angle is mainly the business logic and UI performance is correct, do not check the correctness of the data. After the requirement acceptance is passed, it is transferred to the test execution, and then we execute it according to the test case passed by the review and make the corresponding defect list. After all defect single regression tests for this document have been completed, the functional test for this demand sheet is closed.

Test flow: How a version is tested on-line-functional testing