1. Correctly understand the test design
A test design is a method used to achieve a specific test coverage by deriving a use case from a specific test base. The above test basis refers to the information about the test, such as project background, business requirements, domain knowledge, team, schedule, budget, risk, etc., which are the specific test basis after test analysis, and they affect the test design and execution. Test design is the general outline of the whole testing process, and is usually the embodiment of the tester's test ideas. In the testing world, there is a saying that test design is the soul of testing, and it is also a compulsory course for testers.
2. Principles of test design and factors to be considered
In the testing process, it is impossible for testers to exhaustively list all test scenarios or combinations, so when designing test cases, they must learn to grasp the key points or key points of the test and make reasonable trade-offs, which need to be fully analyzed and designed to achieve ideal coverage. The main considerations for test design are as follows.
The basic idea of test design:
Set the test types included in the test items, such as functional test, performance test, security test, reliability test, other tests, etc. It is possible to clearly understand whether there are any omissions in the type of test this time.
Set the priority of test items, first design the test cases of the high-priority test items, and then design the test cases of the low-priority test items. If there is a lack of risk analysis awareness or insufficient risk analysis ability, write out the test cases of all test items first, and then organize and select the priority of the test cases.
When designing test cases, it is necessary to abstract and classify test items with similar functions, not simply writing, let alone simply copying the content of the document, and designing test cases needs to be thought about and optimized.
Design the test cases of the main process and the positive process first, and then design the test cases of the reverse, negative (abnormal, illegal operation), and extended process or function.
Trying to find out the weak points, boundary points, etc. of the system or component, because there are more defects in these special areas, and more tests are needed to reduce the risk of testing and achieve the set test goals.
The following is an example designed based on the above ideas:
3. How to use the method of test design
1. There are many test design methods, mainly the following:
2. How to use test design methods at different stages
In the testing process of requirements, projects or products, there are different testing methods at different testing stages. Divided into development phases, the testing process can be divided into unit testing, integration testing, system testing, and acceptance testing.
Unit tests
Unit testing is a check of the correctness of a program module (a self-developed module or a self-developed system). If the unit test goal is to achieve 100% decision coverage, then the test design method should adopt the logical coverage method of decision logic, and achieve the test goal through analysis and design.
Integration testing
Integration testing is the verification of the integration of all programs (systems) on the basis of unit tests. The integration of the program is done by the interface. The goal of integration testing is to cover all interface functions and interface performance verification, so there will be functional and non-performance verification of the test method.
System testing
System testing is the process of verifying all the functions of the system and simulating the operation of all software users. If the functional test goal of the system is to cover its various application scenarios, then the test should be based on the scenario-based design approach in order to achieve the test objectives defined in the test plan.
As can be seen from the above classification, logical coverage and basic path coverage belong to the white-box method, which is generally applied to unit testing or code level, but logical coverage is not limited to the code layer and can also be applied to the business layer. Therefore, there is no single test method that can meet the needs of test design, but a variety of methods can be used to meet test needs. Whether it is unit testing, integration testing, or system testing, there are certain application scenarios and test objectives, or it should be said that in specific scenarios, a more appropriate method needs to be selected. Therefore, there is no best test design method in each phase of software testing, only the most suitable design method.
At the end of the article, I invite you to join our software testing learning exchange group, where you can discuss and exchange software testing, learn all aspects of software testing such as software testing techniques and interviews, and understand the latest trends in the testing industry, so as to help you quickly advance to Python automated testing/test development, stabilize your current position and move towards a high salary.
At last:
1) Follow + reply by private message: "Test", you can get a free 10G software test engineer interview book document. And the corresponding video learning tutorials are free to share!