Test case concept
Test case (Test Case) is a document designed for a specific purpose with a set of test inputs , execution conditions and expected results . Its role is actually to test whether a specific requirement is met. Test cases are the basis for guiding the testing work.
The role of test cases
Test cases can avoid missed testing and repeated testing.
The execution results of the test cases are also the benchmarks for evaluating the test results.
Test cases are also the criteria for analyzing defects.
Test case composition
Use Case Number, Test Module, Test Point , Priority, Precondition, Test Data, Test Step , Expected Result , Actual Result
use case number
A unique identifier for the test case.
test module
Indicate which module the tested requirement belongs to, mainly for better identification and maintenance of use cases.
use case title
Also known as test point, it is to describe the focus of the test case in one sentence. Each use case corresponds to a test purpose.
priority
Defined according to the priority level of the requirement. High priority should cover core business, important features, and parts with high frequency of use.
prerequisite
Some conditions that need to be met before the test case can be executed, otherwise the test case cannot be executed. For example, some test environments, or operations that need to be performed in advance.
Test Data
When executing a test, some external data needs to be input to complete the test. These data are determined according to the statistics of the test cases, including parameters, files or database records, etc.
test steps
The step description of the test case, the executive personnel can complete the execution of the test according to the test steps.
expected outcome
It is the most important part of the test case, and it is mainly used to judge whether the tested object is normal. Describe user expectations in terms of requirements.
actual results
PASS passed, FAIL failed, N/A not executed.
test case class
P0-core function
Smoke test, a test case to determine if this version is testable.
P1 - high priority
Most often implemented to ensure functionality is stable. Basic functional testing and important bug and boundary testing.
P2-medium priority
More comprehensive validation of all aspects of functionality. Exceptions, Boundaries, Interrupts, Networking, Fault Tolerance, UI, etc.
P3 - low priority
Not often implemented. Performance, stress, compatibility, security, availability, etc.
Test Case Designer
mind Mapping
Use mind maps to clarify the design ideas of modules and use cases. Reviews are available upon completion. After the review is completed, you can modify it directly in the mind map.
excel
If it is required to write test cases in the form of a table, the test ideas in the mind map can be converted into a table form.
Test case writing steps
Divide functional modules
Forward Functional Verification
Single function item verification
Interactive verification between functions
Hidden needs
The choice of black box testing method
Where input data is required, consider using equivalence class partitioning to turn infinite testing into finite testing
Boundary value analysis must be used in any case
Pay attention to whether the main functions of the program, business processes and business logic are implemented correctly, and consider using the scenario method
The function description of the program contains the combination of input conditions, considering the cause-and-effect diagram judgment table
Additional Test Cases Using Error Inference