


Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
A test case template and an example for software engineering, specifically for an atm system's pin change functionality. The template includes fields for test case number, name, system, subsystem, designers, design and execution dates, short description, pre-conditions, step actions, expected system responses, and comments.
Typology: Exercises
1 / 4
This page cannot be seen from the preview
Don't miss anything!



Test Case #: Test Case Name:
System: Subsystem:
Designed by: Design Date:
Executed by: Execution Date:
Short Description:
Pre-conditions
Step Action Expected System Response Pass/ Fail
Comment
Post-conditions
The subsystem/module (with in the main system) of which the functionality-to-be-tested is part of.
1.2 SHORT DESCRIPTION
[A short detail of the test e.g. the functionality to be tested etc.]
1.3 PRECONDITIONS
[Describe the preconditions for the test case. A precondition is the state of the system that must exist before a test case can be performed.]
[Describe the post conditions for the use case. A post condition is a list of possible states the system can be in immediately after a test case has finished.]
[Describe the flow of events that would be expected in normal conditions]
[System response after each action/event performed by tester]