The process of testing should strictly follow certain processes and plans, which is reflected in the test case, and the tester can find out the software in accordance with the test case, without having to have a deep understanding of the demand for software. The preparation of the test case, but it needs to know how to understand the software requirements design architecture, but the test case can be written is the basic quality of a tester. Summarize the test history of several years, some of the following skin experience, communicate with everyone:
Write principles: FVT (function test) - cover demand, detail to API (), integrated business consideration, the number of case is not much, and in the fine, avoid repeating.
SVT (system test) - comprehensive consideration, the interface part is fine, the number of case is not much, but to cover all possible combinations
1. Familiar with demand, understand business
2. Familiar design
3. Combined with demand and design for module division
4. Locate the ratio of the number of Case based on the side of the module
5. Case wants to write enough detail, try to do anyone to complete the test
6. Test code writing naming specification, code comment, try to hook with CASE
Our software needs to guarantee the quality, and the process of norming this process is essential. I hope we can improve together. I hope our test team is getting more and more growing!!
