Guidelines for Writing Effective Test Cases: Coverage, Logical Flow, and Concise Description

1. Functional Test Case Writing Strategy

Functional coverage means the completeness of test cases. A comprehensive suite usually includes functional testing, capacity testing (large‑data testing), stress testing, performance testing, security testing, and compatibility testing.

Functional Testing

Functional testing can be understood as black‑box testing: given input data, verify that the output matches the expected result.

According to agile development requirements, exhaustive testing (“prevent errors, test as much as possible”) is no longer suitable; testers need strategies that precisely cover scenarios while keeping the number of cases manageable.

Typical functional test case strategies include equivalence class, boundary value, cause‑effect graph, condition coverage, and error guessing (adding cases based on experience).

Equivalence Class

Divide input parameters into valid and invalid equivalence classes, then select any element from each class as test data. If the program treats elements differently, further subdivision is needed. Each invalid class should be covered by a separate test case to avoid masking errors.

Boundary Value

Boundary values are usually used together with equivalence classes, selecting the edges of both input and output classes as test data.

Cause‑Effect Graph

Unlike equivalence classes and boundary values, cause‑effect graphs focus on selecting test data based on combinations of conditions. For more details see the cause‑effect graph method: https://www.cnblogs.com/linyfeng/p/9211666.html

After applying the above strategies, test cases should be cross‑checked against design or development documents to ensure the business flow is fully covered.

Capacity Testing

Capacity testing (large‑data testing) verifies whether a feature can handle massive amounts of data, e.g., importing 500,000 users without crashing the service.

Stress Testing

Stress testing (often called concurrency testing) simulates short‑term data spikes to see if the program reports errors under peak load.

Performance Testing

Performance testing follows company standards and measures response time and throughput under specified configurations.

Security & Compatibility Testing

This involves verifying security aspects and platform compatibility. For example, when testing PC‑side QQ login, the account length might be limited to the interval [5,10] characters.

2. Logical Flow

A reasonable test case should follow a logical order. For example, a user registration flow → login → file upload can be written sequentially, mirroring the business process and reducing review effort.

3. Comprehensive and Concise Writing

This point reflects personal writing philosophy. Comprehensive coverage includes all test points mentioned above, while conciseness means expressing each point with minimal wording, delivering clear intent efficiently.

If you have ideas or suggestions for improving DevOps processes, feel free to contact me (WeChat: devopsvip). More articles are available by following the public account.