Skip to main content

Plan Test Cases for a Small Software Change

Software Engineering, Testing, Cloud & DevOpsChecklists

By Jefferson Otonbara Imgbi

Published
8 October 2026
Last reviewed
8 October 2026
Connect tests to expected behaviour, exceptions and existing functionality. Download a practical checklist for a fictional change.
Image
A form model and test tokens for normal, uncertain and missing-input cases.

Define the behaviour to check

Read the change description and identify what a user should be able to do. Write the expected result in observable terms. A test that merely repeats the implementation can miss whether the behaviour is useful or correct.

The fictional example adds a country selector to an enquiry form. A normal case includes a selected country and suitable practice number. Missing input and conflicting values need separate consideration.

Choose meaningful cases

Include a normal case, relevant boundary or exception cases and existing behaviour that could be affected. Explain the starting state and input for each. Use synthetic information and a suitable test environment.

For the fictional form, consider an empty selection, an empty number if permitted, and a value that does not suit the selected country. Check what the interface explains and whether the expected result is enforced by the relevant validation.

Record expected and observed results

Write what should happen before running the case. Record what actually happened and whether it supports the requirement. Include the tested version and environment so another person can understand the evidence.

A successful case is not proof that every possible case works. Describe what was covered and any important gap. A failed case needs a useful defect record, with steps and evidence, rather than just a label saying broken.

Review readiness with the team

Use the results to support a review decision. Resolve failures or explain the authorised treatment of an outstanding issue. Choose checks proportionate to the behaviour and potential consequences.

Download the PDF or editable Word checklist. Apply it to the fictional change and ask another reader whether the cases cover the main requirement. This introductory exercise does not replace a complete test strategy.

Source and practice note

GitHub review guidance supplies context for assessing a proposed change; the test-planning checklist is an original RDE exercise. Examples and exercises are original RDE material using fictional situations.

Read the official guidance

Cover image: AI-generated illustrative scene created specifically for this resource.

Download and complete the exercise

Read or print the PDF

Download the editable Word document

Printable PDF and editable Word document. Version 2.0, 8 October 2026. Personal and internal organisational adaptation permitted with Jefferson Otonbara Imgbi author credit retained.

Media and downloads

Plan Test Cases for a Small Software Change (PDF)

Document
test-checklist.pdf (63.88 KB)

Plan Test Cases for a Small Software Change (DOCX)

Document

Related resources

Explore related RDE learning