Written test case design

Copyright: Merry due share and eternity, knowledge sharing and immortal, I share my happiness ... https://blog.csdn.net/walter247443819/article/details/78870876

How to write software test case? How to write test case design?

      Software Test document describing the specific steps of the testing process, comprising an input test parameters, conditions, configuration, like the expected output, and each module in order to determine whether the software under test is working properly. Writing test cases allows us to clarify ideas, to avoid omissions, and can track the progress of the test, provide a reference for the test project. So how to prepare a qualified test it?

Method / Step

1. Writing software test cases generally include the following:

   1, the test case number; 2, test items; 3, test title; 4, an important level;

   5, the preset condition / prerequisite; 6, steps; 7, expected results / desired result;

   8, the test results / actual results; 9, reproduce probability and so on.

   
2. Severity also called priority is to determine the severity of the defect made. Generally divided into high (Highs) level, the (mediums) levels, low (Lows) level and the like. Some management software is also divided into serious, significant, minor and other levels. Just a different name, in practical work, we have to do a specific judgment based on project content and bug details. There is also a small version of the confirmation test, also known as "smoke test", which is an important level superior to high-level, but not all projects must.

   
3. The preset condition is a special condition or the configuration of the test will be described, the steps required profile is not redundant, clear, quick positioning, and also comprising the step of operating the device or environment information. Reproduction rate is necessary to determine whether the bug is now or how much probability, which is also very important in the testing process.

   
4. He began to write test cases and under what circumstances? When a customer needs analysis document or sort out the developer project developed, to our system documentation, deployment environment or database structure, we start designing and writing test cases based on these documents. Remember, writing test cases must be demand-reference!

   
5. Know what to write test cases are included, we use what tools or software to write test cases at work it? Commonly used Excel spreadsheet, testlink, Zen and other tools, there are some sites use self-help tools developed specifically as shown.

   

   

   

   
6.