How to design test cases

Test cases are the lifeline of testers in the process of business testing .
When there is no way to test in the face of big demand , The test case is the tester's carding and in-depth exploration of the overall concept ;
When any problem is encountered during the test process to block the test scenario or idea , The test case is the execution instruction and steering wheel of the tester .
When the demand document and the corresponding demand technical scheme are output , The tester needs to deconstruct the requirements according to the provided documents , After deconstructing the atomic content of the requirements , Then design the test case , The test case needs to consider both the comprehensiveness of test verification and the depth of test . that , This requires testers to consider comprehensively to build test ideas and what test strategies and methods to use to ensure the comprehensiveness of test coverage as much as possible .

Try to ask , When faced with a large demand （ This means that it will cost at least 2 Requirements that can only be completed in iterations ）, What kind of test case design ideas do testers need to have in order to achieve high timeliness 、 High efficiency 、 Comprehensively achieve test coverage ？

The core of test case design

How important

The primary consideration in the design of test cases is the main process scenario （ Be sure to make clear the background of the demand and what problems the demand is generated to solve ）, The main flow includes ：
1. The design of test cases revolves around the description of product requirements documents
2. Whether the design scenario of the test case conforms to the use scenario of the actual user
In the mainstream , Grasp the priority of test cases , Be able to find serious problems in the test process as early as possible , Expose the problem as soon as possible

Equivalence

The design of test cases needs to be designed according to the developed implementation logic , Black box testing may involve invalid test cases among multiple test cases designed , For example, in some interaction scenarios , There are multiple entries in the existing form , If the tester designs , Design each input item as a test scenario , Without knowing the implementation , The number of test cases will increase exponentially , There must be many invalid test cases . Of course , The metaphor here is extreme , But the tester needs to have this awareness , To sort out the logical branches implemented on the development side , Prevent the generation of garbage test cases .

Borderline

The design of test cases involves the interaction between functional modules , Since interaction is involved, there must be boundaries . The tester needs to identify the upstream and downstream of the requirement , This demand has several entrances and several exits .

Based on the above , As the core idea of designing test cases, it runs through the whole process of writing test cases , Then cooperate with the test method , You will have a complete skeleton of requirements in your mind , Then the tester's assurance of quality will be greatly improved .

Test point

Main process

Main process , That is, all the function point scenarios described in the requirements , Here is the focus of the test , It is also an important means for smoke test to check the quality of the test .

Branch process

Branch logic scenarios other than trunk logic .

Abnormal flow

Data exception ： For example, key data is missing 、 Data is pushed repeatedly
Call chain exception ： For example, the service call link is abnormal , System processing
Common exceptions are ：

1. Dependent services are not available , Whether there is degradation treatment , Whether there are monitoring alarms ？
2. Dependent data missing , whether catch abnormal , Ensure that the program does not crash, And produce error journal ？
3. Service to restart , Fault tolerance ？
4. The basic component service is abnormal , Such as redis、kakfa、mysql Isoanomaly , Whether to lose data , After the basic services are restored , Whether the service can be restored ？

UI Test point

1. style 、 style 、 Layout
2. check ： Required 、 Optional filling, etc
3. Show whether there are covers and unreasonable omissions
4. Whether the prompt is friendly
5. wait （ Here, you can view different items UI Focus to complement ）

Forward compatible

When transforming the existing requirements , You need to consider interfaces or GUI Forward compatibility on .

Association function

It is necessary to evaluate whether the requirement will affect the existing functions , such as ： Changes to common modules in the code .

Historical data impact

Whether historical data need to be processed for demand transformation ？ Such as ： Existing table structure changes, etc .

Performance impact

The performance impact here is relatively simple , Such as ： Interface response speed （ Big data query 、 High concurrent access, etc ）、GUI The rendering speed of （ Rendering with large amount of data ） As a basic performance compliance index ;
For the maximum business processing capacity of the system 、 Processing speed and other performance , We need to start another big story .

Terminal compatibility

If the product supports ：PC、 Applet 、APP And so on , Functional availability needs to be verified at multiple terminals .

Security

Business data security ： Such as , Important data is not in clear text ;
Business scenario security ： Such as , Bypass login authentication 、 Data tampering in transactions 、 Malicious call of interface, etc

The above ideas and methods for designing test cases are the precipitation and summary of personal work experience , It belongs to my humble opinion , But it should be a reference for testing newcomers , At the same time, we also hope that the elites in the industry can find deficiencies and defects , Put forward suggestions for improvement .

welfare （ Official account collection ）

The main content includes ： Ali 、 tencent 、 Meituan 、 Byte runout and other test interview questions , A functional test 、 Performance testing 、 Automated testing, learning videos, etc .