How to Write a Manual Step-by-Step Software Test Case

Write a step-by-step case for testing your software applications.

A software test case is a set of steps and expected results used to test an application. It is created from the software requirements. Well-written test cases can make the testing cycle smooth and efficient. It is imperative to write clear, understandable test cases that can be run against new functionality and regression testing, as well. A good test case is easy to run, consistent in the time it takes to run, and it is easy to maintain.

Instructions

1. Identify the requirement to test and enter this requirement name and/or number in the test case. A business analyst typically creates a design document that includes the requirements.

2. Create a name and/or test number for the test case. It is helpful to create a separate traceability matrix document to link the requirements and test cases together. Identifying the requirement name and number along with the test-case name and number allows for traceability between the requirement and test case.

3. Write a short description of the test case. The test case description gives a high-level overview of what the test case does. It should allow someone with no prior knowledge of the test case to get a clear understanding of what is being covered without going through all of the test steps.

4. Identify all setup information needed for running the test. Setup information includes testing prerequisite items such as data, hardware, software and browsers.

5. Write the steps and results. For each step, write the step number. It is best to keep the number of steps to around 10, with a maximum of 15. Keeping tests short allows easier maintenance, easier results tracking, and reduced testing time. Write the step description. This can include one clear input or a set of inputs, if they are all related. Other elements to include for each step are the expected, a pass/fail indication, the actual result, any notes and any attachments.

Tips & Warnings

• The software application under test is constantly changing. The software test cases for the application must also change. In order to be reusable, test cases should be maintained after each test cycle. Without maintenance, it will be a challenge to determine whether any resulting errors are due to the test case or an actual defect.

• Review test cases with fellow associates, including the business analysts who wrote the requirements, the developers who write the code for the requirements and quality-assurance staff.

• Make test cases self-cleaning. The testing environment should be brought back to the state it was in prior to running the test case.

References

• Mike Clark: JUnit Primer
• MSDN: Globalization Step-by-Step: Sample International Test Cases