Designing Exception Test Cases: Business, Operational, Standard, and Experience Requirements

Before software is delivered to end users, various types of testing are required, including exception testing.

Exception testing checks how a system handles abnormal situations, both hardware and software, by deliberately creating error conditions to verify that error messages are clear, constraints are enforced, and the system remains stable without crashing.

The article focuses on designing exception test cases. To validate software robustness and reliability, it proposes analyzing four aspects: business requirements, operational requirements, standard requirements, and experience requirements.

Exception Test Points – Business Requirements:

1. Special business flow testing – run the software through non‑standard business processes to see if it generates incorrect data or causes system failure.

2. Stress testing – evaluate system behavior under extreme load on critical business functions.

3. Modification of important configuration – change or delete key configuration items and verify appropriate warnings and recovery guidance.

4. Modification of environment variables – alter runtime environment variables and observe system response.

5. Changing user credentials or permissions – modify database access usernames/passwords during operation and check system reaction.

6. System upgrade – upgrade an older system while it is running to see how it handles the change.

Operational Requirements:

1. Single‑quote handling – test input fields with single quotes, double quotes, ampersands, angle brackets, etc., and verify error handling and recovery.

2. Mandatory field testing – ensure required fields prompt users when left empty and handle the omission correctly.

3. Special field type testing – provide invalid data for fields such as ID numbers, dates, phone numbers, postal codes, and check error messages.

4. Date type testing – test boundary values and format validity, including leap‑year dates, and verify appropriate prompts.

5. Web session testing – for B/S applications, verify that accessing protected URLs without login triggers proper warnings.

Standard Requirements:

1. Database server crash – forcibly stop the database server and check the system’s error reporting and recovery guidance.

2. Data migration – perform database migration during operation and observe system behavior.

3. Table corruption – illegally delete or modify tables and verify accurate error messages and remediation steps.

4. Network failure – disconnect the network or generate heavy traffic to test error handling.

5. Installing additional software on the server – add antivirus, new browsers, input methods, or office tools during runtime and monitor system response.

6. Port conflict – run multiple services on the same port and check for proper conflict handling.

Experience Requirements:

1. File loss – forcibly delete essential application files and verify error prompts and recovery actions.

2. File manipulation – move, delete, or change attributes of installation or generated files during operation.

3. Server resource stress – artificially increase CPU, memory, or disk load on database, web, or middleware servers and observe system reaction.

4. Power outage – cut power to test machines during testing to assess recovery capability.

5. Service termination – pause database or web services and watch how the system handles the interruption.

Conclusion:

Only software that passes thorough exception testing can maintain stable operation after launch, giving end users confidence; the results also provide valuable feedback for further system optimization.