Many interview questions, the interviewer will ask questions "used to work in both contact" Before you talk about the company's testing process "over which types of test documents" to determine whether the former company's test management practices, and belongs to the project size . Software testing is usually included in the project only test program (depending on the size of the project exists or not), test cases, test reports, defect reports document, in fact, does not completely cover the entire testing process, but if the answer to these elaborate, is not enough. Even if the company did not project specifications and test procedures, they would need to understand the overall specifications under Category A projects, rational use of the current project at the same time can also enrich their experience.
Share several projects testing the peripheral document: measuring mention list, released a list of the project team tested daily; today the main lecture to explain the measured application list and put off his role.
First understand the entire process under mentioning measured: R & D group to alert measured Mail (say explicitly mentioned test content, raise the measuring point of time, the self-test results and test accessories precautions) -> receive messages from the test group responsible person -> deployment test results of research and development group to reply to e-mail notification> test is passed or not - environment -> execute acceptability test
These are the common measure mentioned processes, a more formal test customer applications, developers will be executed, the next step of coding work through until after the test cases can be received by all in the development stage. Such early development will also avoid the problem severity. After the testing phase to mention a lot of time to save costs.
The above mentioned test procedures involved in the measure is attributable to mention the list of items in the test document, to mention a list of test requirements according to the company, the nature and size of the project will be slightly different, but typically include the following essential elements:
Mention test requirements
Mention measuring time
Mention measured responsible
Test path
Self-test note
function points
Self-test results
The corresponding developer
Special Considerations test
Test Return Instructions
Above, mention measuring demand related to the general demand number, if you use a requirements management tool, you can manually export or association; the first person put in charge of measuring the responsible person to fill mention sensing module or general needs, such as emergency contact in case of emergency situations will ; test path depending on the testing terminal, description will be given corresponding path; generally includes a self-test note whether unit tests whether the pass code review, whether through the database integrity check, etc., provide a list of measurement for an actual complete fill art be the case by selecting the corresponding option; comprising self-test result by, not through, non-development state, typically self-test pass rate of 95% measured to mention, the low priority function points may be performed simultaneously; test considerations generally made mention measured responsible to fill out, inform the focus when the testers check; return instructions generally refers to the test in advance an appointment to return the rule, such as the defect rate reaches a certain percentage of the test is stopped, or by calculating the rate of defects thousand lines of code or function points press judged by segment.
In general, the list also have to mention the measured application segments such as the nature of the demand, new demand, iterative requirements, function optimization requirements, it is recommended to optimize demand, the technology requirements, performance requirements and so on. To mention the flexibility to adjust measurement template option to configure the application list. After the test person in charge of receiving the message, you need to perform the test for acceptability to mention the list of test, test test message by replying to mention that testing results and inform the next test plan; do not explain the reasons and should be repaired by the direction of testing not to mention measured by replying to e-mail and annex defect report.
Project does not exist perfect testing process, only constantly running, constantly adapt to the development needs of the project itself, we can continue to improve our testing process management to escort final product quality.