Test cases that testers must master

The test case （Test Case） Is a set of test inputs designed for a specific purpose 、 Documentation of execution conditions and expected results . Its function is to test whether a specific requirement is met . Test cases are the basis for guiding the test work .

Composition of test cases

Standard test cases usually consist of the following modules ：

· Use case number ： Unique identification of the test case .

·  modular ： Indicate which module the tested requirements belong to , Mainly to better identify and maintain use cases .

·  Use case title ： Also known as test point , Is to describe the focus of test cases in one sentence . Each use case corresponds to a test purpose .

·  priority ： Define according to the priority of the requirements . High priority should cover the core business , Important features and parts with high frequency of use .

·  Prerequisite ： Some conditions that the use case needs to meet before execution , Otherwise, the test case cannot be executed . For example, some test environments , Or operations that need to be performed in advance .

·  Test data ： When performing tests , You need to input some external data to complete the test . These data are determined according to the statistics of test cases , With parameters 、 Files or database records, etc .

·  testing procedure ： Step description of test case , The executor can complete the execution of the test according to the test steps .

·  Expected results ： Is the most important part of the test case , It is mainly used to judge whether the tested object is normal . Describe the user's expectations according to the requirements

·  The actual result ：PASS adopt ,FAIL Failure ,N/A unexecuted .

Test case priority

At work , Test cases are divided into different levels according to system requirements ：

· P0： Core function test cases （ Smoke testing ）, Test case to determine whether this version is testable . This part of the test case if FAIL, Other test cases don't need to be executed , You need to call back and retest the developer .

· P1： High priority test cases , The most common implementation is to ensure that the function is stable . Contains basic functional tests and important errors 、 Boundary test .

· P2： Medium priority test cases , More comprehensive verification of all aspects of the function , Include exception tests 、 The border 、 interrupt 、 The Internet 、 Fault tolerance 、UI Wait for test cases .

· P3： Low priority test cases , Not always executed , Generally include performance 、 pressure 、 Compatibility 、 Security 、 Availability, etc .

In different companies , There may be some differences in the grading of test cases , But basically the same .

The role of test cases

What are the benefits of writing test cases ？

First , You can have a good idea by using useful examples , It will not be repeated many times at one test point , There are ideas , Avoid missing test points . And the test data can be prepared in advance in the test case , In this way, some important data will not be missed .

The execution results of test cases are also the measurement benchmark for evaluating test results . If you design use cases that fully cover the requirements , All test cases are executed and passed , All problems found are modified , It can be delivered to customers with confidence .

Test cases are also the standard for analyzing defects . Because the expected results will be described in detail in the test case , The expected result is to analyze whether there is  Bug  A standard of . Consistent with the expected results , No Bug. conversely , Inconsistent with the expected results , Is there Bug, Need R & D and repair .

Test case design tool

When writing use cases , You can use mind mapping to clarify the design ideas of modules and use cases . After the mind map is completed, you can review . After the review , If you need to modify something, you can modify it directly in the mind map .

If you are required to write test cases in a tabular way , The test ideas in mind mapping can be transformed into tabular form .

Later, we will introduce the specific design method of test cases ~ Coming soon ！