Software Test Case Design Steps

Software Test Case Design StepsSoftware Testing

DesignTest CaseWhen testing, you need to have a clear idea about what to test, what order to test, and what needs to cover. Test Case writers should not only master the technology and process of software testing, in addition, you must have a thorough understanding of the design, functional specifications, user trial scenarios, and program/module structure of the software to be tested. Test Case Design generally includes the following steps:

1. TestRequirement Analysis

Find out the requirements of the software/module to be tested from the Software Requirement documents, organize them into test requirements through your own analysis and understanding, and identify the functions of the tested objects. Testing requirements are characterized by software requirements and testability.

Test requirements should be summarized, classified, or subdivided based on software requirements to facilitate test case design. The relationship between test sets and test requirements in test cases is one-to-one, that is, one or more test cases correspond to one test requirement.

2. Business Process Analysis

Software testing is not just a functional-based black box test, but also a test of the internal processing logic of the software. In order to avoid missing test points, you need to have a clear understanding of the business processes of software products. We recommend that you draw out the business process of the software before designing complex test cases. If the business process design already exists in the design document, you can supplement the existing process from the testing perspective. If the business process cannot be obtained from the design,Test EngineerYou should read the design document andDevelopmentPersonnel Exchange, and finally draw a business flow chart. The business flow chart can help you understand the processing logic and data flow of the software and guide the design of test cases.

The following information should be obtained from the Business Process:

A. What is the main process?

B. What is the conditional alternative process?

C. What is the data flow direction?

D. What are the key judgment conditions?

3. Test Case Design

After completing the test requirement analysis and software process analysis, we began to design test cases. The types of test cases include functional testing, boundary testing, exception testing, performance testing, and stress testing. In case design, except for functional testing, boundaries, exceptions, and performance should be considered as much as possible to discover more hidden problems.

Black box testingTest Case Design MethodInclude: equivalence classification, Boundary Value Division, cause-and-effect analysis, and incorrect prediction,White box testingThe test case design methods include statement coverage, decision coverage, condition coverage, decision/condition coverage, and multiple condition coverage. Black box testing is discussed here. When designing test cases, you can use the software test case design method to design them based on the preceding requirement analysis and Software Process Analysis:

Function Test: test whether a function meets the requirements of the definition, whether the function is correct, complete.

Suitable technology: function tests and equivalence classes derived from business needs and design instructions

Border test: tests the boundaries of a function.

Suitable technology: Boundary Value Division

Exception test: for some functions, the boundary condition cannot be simply understood or some operations are not completely correct, but they may occur. For such cases, you need to write related exception tests.

Suitable Technologies: special business processes, error guesses, Boundary Value Analysis, internal boundary value testing, and,

Performance testing: Check whether the system meets the performance specified in the requirement. The performance mainly includes understanding the internal and external performance factors of the program. Internal performance factors include:Test EnvironmentSystem resource usage. External factors include response time and throughput.

Suitable technology: Test of export of business requirements and design instructions

Stress Testing: stress testing, also known as strength testing, mainly checks the ability of software running in the system running environment under extreme conditions, such as giving a considerable load orNetworkTraffic to application software compatibility testing: test the functionality of software products on different platforms, different tools, and different versions of the same toolCompatibility.

4. Test Case Review

After the test case is designedConfirm TestWhether the process and method are correct and whether there are missing test points requires review of test cases.

The test case review is generally arranged by the test leader. The participants include: Test Case designer, test leader, Project Manager, Development engineer, and other related development and test engineers. After the test case is reviewed, the test engineer modifies the test case based on the review results and records the modification logs.

5. Updated Test Cases

After the test cases are compiled, they must be constantly improved. After new features or update requirements of software products are added, the test cases must be modified and updated.Test processIt is found that the design of test cases is not weekly, and the test cases must be modified and improved. After the software is delivered and usedSoftware defectsThe defect is caused by the vulnerability in the test case and needs to be improved. Generally, minor modifications can be modified in the original test case document, but there must be a change record in the document. The software version is updated, and the test cases should also be updated accordingly. Test Cases are "active" and are constantly updated and improved throughout the software lifecycle.

Article from the collar test software testing network http://www.ltesting.net/