Principles for developing test cases

Test cases should include the functions to be tested, data to be input, and expected output results. Test data should be tested with a small amount of efficient test data. The basic goal is to design a set of test data that discovers an error or a certain type of error. The test cases should cover the following aspects:

1. correctness test: Enter the actual user data to verify that the system meets the requirements.

Requirements of the Requirement Specification; the test points in the test case should first ensure that at least all the functions in the requirement specification should be covered and normal.

 

2. Fault Tolerance (robustness) test: The program can receive correct data input and generate correct (expected) output, when illegal data is input (illegal data type, non-conforming data, and overflow data), the program should be able to give a prompt and handle it accordingly. Think of yourself as a customer who doesn't know how to operate the product at all.

3. Complete
Security Testing: attempts by unauthorized users to use software systems or data, the extent to which the system can be controlled, and the Data Processing of programs can maintain external information (
Database or file.

4. Inter-Interface Test: test the coordination and communication between each module and the consistency and correctness of data input and output.

5. Database testing: tests the database structure, data tables, and data calling relationships of the software system based on the database design specifications.

6. Boundary Value Analysis: Determine the boundary condition (just equal to, slightly less than, slightly greater than, and just greater than the equivalence class boundary value ).
During the test, some valid or invalid data is input, which is mainly selected near the boundary value.

7,
Stress Test: enter 10 records to run each function, 30 records to run, and 50 records to run... Test.

8. equivalence Division: divides all possible input data (valid and invalid) into several equivalence classes.

9. Error Prediction: based on test experience and intuition, refer to errors in previous software systems.

10. Efficiency: the scheduled function and system running time (mainly for databases) are completed ).

11. Understandable (operational): the difficulty of understanding and using the system (user-friendly ).

12. Portability: Running Performance in different operating systems and hardware configurations.

13,
Regression test: All test points are tested based on test cases and problems found during the test
The developer has solved the problem and will perform the next round of testing.

14. Comparison Test: Compare the running and running of a similar product or existing product with the tested product, or compare it with the previous test results.

 

Note: For different test types and stages, the focus of test case writing is different.

1. Among them, 1st, 2, 6, 8, 9, and 13 items are module (component, control) testing, combination (integration) testing,
System Testing involves and focuses on testing.

2. Unit (module) testing (components, controls) testing: 5th key tests.

3. Combination (integration) test: focuses on testing data input and logic between interfaces, that is, 4th items.

4. System Testing: Focus on testing 3rd, 7, 10, 11, 12, and 14 items.

5. For stress testing and portability testing, if you are a company product series, you can use representative products for a representative test.

6. GMPS Basics
After the test case is designed, other test projects only write test cases of different parts of the design.

7. the test cases for each test project are not static. As the test experience accumulates or when testing other projects find that there are insufficient test points, test Cases of test projects can be supplemented and improved continuously.

 

PS: What does GMPS mean? Only
GMP stands for good manufacturing practices. It is a quality standard adopted by pharmaceutical companies.
GMPS indicates that it meets the quality standards.