Shulou(Shulou.com)06/03 Report--

In many interview questions, the interviewer will judge whether the previous company's test management is standardized or not, and the size of the project by asking "tell me about your previous company's test process" and "what types of test documents you have come into contact with in your previous work." The usual software test project only contains test plan (depending on whether the project size exists or not), test case, test report, defect report document, in fact, it can not fully cover the whole testing process. Even if the company does not have a standardized project and testing process, they also need to understand the overall specifications of Class A projects, reasonable use in the current project can also enrich their own experience.

Share the surrounding documents of several project tests: test list, release list, project team test daily; today, we will mainly explain the list and function of the application for test.

First of all, understand the whole process of the test: the R & D team sends out an email (explaining the contents and time points of the test, attachments to the self-test results and matters needing attention, etc.) > the person in charge of the test group receives the email-> deploy the test environment-> perform the acceptability test-> notify the R & D group of whether the test passed or not.

The above is the general test procedure. In the more formal customer application testing, the developer will pass all the acceptability test cases in the development phase, and then proceed to the next step of coding. This also avoids severity problems in the early stages of development. Save a lot of time and cost for the later stage of testing.

The test list mentioned above also belongs to the project test document. The list varies slightly according to the company's requirements, project size and nature, but usually includes the following necessary contents:

Demand for raising and testing

Measurement time

Refer to the person responsible for testing

Test path

Self-test description

Function point

Self-test result

Corresponding developer

Special considerations for testing

Test return instructions

Above, the test requirements are generally associated with the requirement number, which can be exported or manually associated if the requirements management tool is used; the person responsible for the test usually fill in the test module or the first person in charge of the requirements, and will contact urgently in case of emergency; the test path will be described according to the difference of the test terminal. The self-test description generally includes whether to pass the unit test, whether to pass the code review, whether to pass the database integrity check, and so on. The personnel filling in the test list need to check the corresponding pass options according to the actual completion; the self-test results include pass, fail, undeveloped and other statuses. Generally, the self-test pass rate reaches 95%, and the low-priority function points can be carried out at the same time. The matters needing attention in the test are generally filled in by the person responsible for the test to inform the tester of the focus of the inspection; the test return description generally refers to the return rules agreed in advance, and if the defect rate reaches a certain percentage, the test is stopped, or judged by calculating the defect rate of thousands of lines of code or by subdivision by function points.

In general, the application list is also subdivided, such as new requirements, iterative requirements, functional optimization requirements, suggested optimization requirements, technical requirements, performance requirements and so on. To flexibly adjust the template option configuration of the test application list. After receiving the email, the person in charge of the test needs to perform the acceptability test against the test list, and the test explains the test results and informs the next test plan by replying to the test email; the test does not reply to the test email to explain the reasons for failure and the suggested repair direction and attach the defect report.

There is no perfect testing process in the project. Only by constantly running in and adapting to the development needs of the project itself can we constantly improve our testing process management and protect the final product quality.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.