In order to help testers import the written test cases into the test management tool testLink, this article is written...
The test case template is a workbook in Excel format. The first tab page "Version Record" is used to record the change information of the test case set and cannot be deleted. The test cases to be imported start from the second tab.
Description of each field in the template:
ID
use case element
illustrate
1
Requirement identification
The unique identifier corresponds to the use case number, and it is a one-to-many relationship.
2
Use case set directory
Indicate the first-level module, second-level module, or third-level function of the use case. If a module is more complicated, there may be more levels, and each level will be separated by a slash.
3
use case ID
Each use case can be accurately identified, and each use case number must be unique among all test cases. The format is: project code_module name_test terminal_serial number.
4
use case title
Be able to clearly express the test purpose and key test elements of the test case. The format is: verb-object structure, for example: verify xxx, check xxx.
5
state
Before the review, it is in the "Draft" state, after the review is passed, it is in the "Ready" state, and after the review is invalid, it is in the "Abandoned" state.
6
Summary
A brief introduction of the test purpose, applicable entities and related information of the use case.
7
prerequisite
It is necessary to describe the external environment that the test needs to be in and the state and configuration that the test object and auxiliary objects need to be in before the test. It is necessary to ensure the correctness and consistency of test execution after completing the state and configuration described in the preconditions and the external environment.
8
importance
Distinguish the importance of test cases and determine the level of use case execution.
9
step number
Sequentially increasing numbers, starting with 1.
10
operate
In order to achieve the test purpose of the test case, the operations that need to be performed; each operation step corresponds to an expected result.
11
expected outcome
For the test purpose of the test case, the corresponding expected output state after the operation in the test step.
12
Do you need to automate
whether.
13
Is it automated
automatic / manual.
14
writer
Designer and writer of test cases.
15
Expected execution time
The time required to execute a test case completely, in minutes.
16
date of writing
Date when the test case was written, in the format of YYYY/MM/DD.
17
review date
Test case review date in the format of YYYY/MM/DD.
18
Updated
Test case update date, in the format of YYYY/MM/DD.
The following are considerations for using test case templates:
l The header cannot be changed or deleted;
l Do not leave blank lines between use cases;
l For each use case, starting from the second row, only fill in the step number, operation and expected result;
l The use case set directory is a complete hierarchical structure from the top of a test project to the bottom. The levels must be separated by slashes. There is no limit to the number of levels, but it is recommended not to exceed 4 levels;
l Fields that require data verification can only fill in the values in the specified list:
- Status: Draft, Ready, Obsolete
- Importance: high, medium, low
- Whether it has been automated: manual, automatic
l Non-required fields will not be imported into testLink:
- Requirement identification
- use case ID
- Do you need to automate
- writer
- date of writing
- review date
Finally: In order to give back to the die-hard fans, I have compiled a complete software testing video learning tutorial for you. If you need it, you can get it for free 【保证100%免费】
How to obtain the full set of materials: Click the small card below to get it yourself
