Acceptance
Test Cases
<Note: everything surrounded by <> is either a placeholder to be filled
in or a comment to be deleted.>
<Source for this template: Managing Software Requirements: A Use Case
Approach, Second Edition, by Dean Leffingwell and Don Widrig, page 316.>
Test Cases for Use Case: <Name of use case>
|
Test Case Id |
Scenario |
Description |
Condition: <condition> |
Condition: <condition> |
Condition: <condition> |
Expected Result |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<Test Case Id - A unique integer identifying this test case
Scenario – The number of the scenario being used
Description – A brief description in English of the test case, should include whether which
flow (e.g. basic flow, alternate flow 2) is being used
Condition <condition> – The value that will occur for this condition for this test case;
<condition> should describe the condition being tested; one column per condition
Expected Result – What is expected to be the result under these conditions
>
<Duplicate the above table as needed for each use case from the use case model.>