<Project Name> - SDM Test Scenarios

Last Update: <Insert Date>

SDM - Test Scenarios Template

1

<Project Name> - SDM Test Scenarios

Last Update: <Insert Date>

SDM - Test Scenarios Template

2

09/012005

<Project Name> - SDM Test Scenarios

Last Update: <Insert Date>

System and Integration Test Scenario

System and Integration Test Scenario # 1
Version #:

Test Scenario ID:

Environment:

<Version number of the

application being tested>

<Tracking number associated

with the module, or set of
modules, packaged together
that perform the function
tested by this test scenario>

Build #:

<A sequential number assigned to this test scenario

Process ID:
for tracking purposes>
<Enter the environment this test scenario is using,
Machine tested:
e.g. mainframe, client/server>

Test Scenario
Description:

<Describe briefly what this test scenario is testing.>

Objective:

<Describe the desired objective of this test scenario.>

Assumptions/
Constraints:
Test Files/Test
Data:
Author:
Reviewed by:
Executed by:
Test Steps:
Step #

Retry #:

<A sequential number

representing the number of
times the test case has been
executed.>

<Identify the Process ID that this Test Scenario relates with>

<Enter the machine that will be used for this test, e.g. PC,
server>

<List any assumptions or constraints that the tester should be aware of.>
<List the test files and or test data in order to successful run this test scenario.>
<Identify the author of this Test Scenario>
<Identify the person who reviewed this Test
Scenario>
<Identify the person who executed this Test
Scenario>

Last Modified:
Reviewed Date:
Execution Date:

Description

<Update the date that the Test Scenario was last updated.>
<List the date that the Test Scenario was reviewed on.>
<List the date that the Test Scenario was last executed on.>

Expected Result

<Enter the description for each step of the test

<Use sequential
scenario. Fully describe what the tester should be
counting numbers>
doing on the application.>

<Enter the expected result of a

successful execution of each step.>

SDM - Test Scenarios Template

3

Actual Result
<Enter the actual result for each step. If
the actual result matches the expected
result, then enter the same information.>

<Project Name> - SDM Test Scenarios

Last Update: <Insert Date>

System and Integration Test Scenario

System and Integration Test Scenario # 2
Version #:

Test Scenario ID:

Environment:

<Version number of the

application being tested>

<Tracking number associated

with the module, or set of
modules, packaged together
that perform the function
tested by this test scenario>

Build #:

<A sequential number assigned to this test scenario

Process ID:
for tracking purposes>
<Enter the environment this test scenario is using,
Machine tested:
e.g. mainframe, client/server>

Test Scenario
Description:

<Describe briefly what this test scenario is testing.>

Objective:

<Describe the desired objective of this test scenario.>

Assumptions/
Constraints:
Test Files/Test
Data:
Author:
Reviewed by:
Executed by:
Test Steps:
Step #

Retry #:

<A sequential number

representing the number of
times the test case has been
executed.>

<Identify the Process ID that this Test Scenario relates with>

<Enter the machine that will be used for this test, e.g. PC,
server>

<List any assumptions or constraints that the tester should be aware of.>
<List the test files and or test data in order to successful run this test scenario.>
<Identify the author of this Test Scenario>
<Identify the person who reviewed this Test
Scenario>
<Identify the person who executed this Test
Scenario>

Last Modified:
Reviewed Date:
Execution Date:

Description

<Update the date that the Test Scenario was last updated.>
<List the date that the Test Scenario was reviewed on.>
<List the date that the Test Scenario was last executed on.>

Expected Result

<Enter the description for each step of the test

<Use sequential
scenario. Fully describe what the tester should be
counting numbers>
doing on the application.>

<Enter the expected result of a

successful execution of each step.>

SDM - Test Scenarios Template

4

Actual Result
<Enter the actual result for each step. If
the actual result matches the expected
result, then enter the same information.>

<Project Name> - SDM Test Scenarios

Last Update: <Insert Date>

Regression Test Scenario

Regression Test Scenario # 1
Version #:

Test Scenario ID:

Environment:

<Version number of the

application being tested>

<Tracking number associated

with the module, or set of
modules, packaged together
that perform the function
tested by this test scenario>

Build #:

<A sequential number assigned to this test scenario

Process ID:
for tracking purposes>
<Enter the environment this test scenario is using,
Machine tested:
e.g. mainframe, client/server>

Test Scenario
Description:

<Describe briefly what this test scenario is testing.>

Objective:

<Describe the desired objective of this test scenario.>

Assumptions/
Constraints:
Test Files/Test
Data:
Author:
Reviewed by:
Executed by:
Test Steps:
Step #

Retry #:

<A sequential number

representing the number of
times the test case has been
executed.>

<Identify the Process ID that this Test Scenario relates with>

<Enter the machine that will be used for this test, e.g. PC,
server>

<List any assumptions or constraints that the tester should be aware of.>
<List the test files and or test data in order to successful run this test scenario.>
<Identify the author of this Test Scenario>
<Identify the person who reviewed this Test
Scenario>
<Identify the person who executed this Test
Scenario>

Last Modified:
Reviewed Date:
Execution Date:

Description

<Update the date that the Test Scenario was last updated.>
<List the date that the Test Scenario was reviewed on.>
<List the date that the Test Scenario was last executed on.>

Expected Result

<Enter the description for each step of the test

<Use sequential
scenario. Fully describe what the tester should be
counting numbers>
doing on the application.>

<Enter the expected result of a

successful execution of each step.>

SDM - Test Scenarios Template

5

Actual Result
<Enter the actual result for each step. If
the actual result matches the expected
result, then enter the same information.>

<Project Name> - SDM Test Scenarios

Last Update: <Insert Date>

Regression Test Scenario

Regression Test Scenario # 2
Version #:

Test Scenario ID:

Environment:

<Version number of the

application being tested>

<Tracking number associated

with the module, or set of
modules, packaged together
that perform the function
tested by this test scenario>

Build #:

<A sequential number assigned to this test scenario

Process ID:
for tracking purposes>
<Enter the environment this test scenario is using,
Machine tested:
e.g. mainframe, client/server>

Test Scenario
Description:

<Describe briefly what this test scenario is testing.>

Objective:

<Describe the desired objective of this test scenario.>

Assumptions/
Constraints:
Test Files/Test
Data:
Author:
Reviewed by:
Executed by:
Test Steps:
Step #

Retry #:

<A sequential number

representing the number of
times the test case has been
executed.>

<Identify the Process ID that this Test Scenario relates with>

<Enter the machine that will be used for this test, e.g. PC,
server>

<List any assumptions or constraints that the tester should be aware of.>
<List the test files and or test data in order to successful run this test scenario.>
<Identify the author of this Test Scenario>
<Identify the person who reviewed this Test
Scenario>
<Identify the person who executed this Test
Scenario>

Last Modified:
Reviewed Date:
Execution Date:

Description

<Update the date that the Test Scenario was last updated.>
<List the date that the Test Scenario was reviewed on.>
<List the date that the Test Scenario was last executed on.>

Expected Result

<Enter the description for each step of the test

<Use sequential
scenario. Fully describe what the tester should be
counting numbers>
doing on the application.>

<Enter the expected result of a

successful execution of each step.>

SDM - Test Scenarios Template

6

Actual Result
<Enter the actual result for each step. If
the actual result matches the expected
result, then enter the same information.>

<Project Name> - SDM Test Scenarios

Last Update: <Insert Date>

Load Test Scenario

Load Test Scenario # 1
Version #:

Test Scenario ID:

Environment:

<Version number of the

application being tested>

<Tracking number associated

with the module, or set of
modules, packaged together
that perform the function
tested by this test scenario>

Build #:

<A sequential number assigned to this test scenario

Process ID:
for tracking purposes>
<Enter the environment this test scenario is using,
Machine tested:
e.g. mainframe, client/server>

Test Scenario
Description:

<Describe briefly what this test scenario is testing.>

Objective:

<Describe the desired objective of this test scenario.>

Assumptions/
Constraints:
Test Files/Test
Data:
Author:
Reviewed by:
Executed by:
Test Steps:
Step #

Retry #:

<A sequential number

representing the number of
times the test case has been
executed.>

<Identify the Process ID that this Test Scenario relates with>

<Enter the machine that will be used for this test, e.g. PC,
server>

<List any assumptions or constraints that the tester should be aware of.>
<List the test files and or test data in order to successful run this test scenario.>
<Identify the author of this Test Scenario>
<Identify the person who reviewed this Test
Scenario>
<Identify the person who executed this Test
Scenario>

Last Modified:
Reviewed Date:
Execution Date:

Description

<Update the date that the Test Scenario was last updated.>
<List the date that the Test Scenario was reviewed on.>
<List the date that the Test Scenario was last executed on.>

Expected Result

<Enter the description for each step of the test

<Use sequential
scenario. Fully describe what the tester should be
counting numbers>
doing on the application.>

<Enter the expected result of a

successful execution of each step.>

SDM - Test Scenarios Template

7

Actual Result
<Enter the actual result for each step. If
the actual result matches the expected
result, then enter the same information.>

<Project Name> - SDM Test Scenarios

Last Update: <Insert Date>

Load Test Scenario

Load Test Scenario # 2
Version #:

Test Scenario ID:

Environment:

<Version number of the

application being tested>

<Tracking number associated

with the module, or set of
modules, packaged together
that perform the function
tested by this test scenario>

Build #:

<A sequential number assigned to this test scenario

Process ID:
for tracking purposes>
<Enter the environment this test scenario is using,
Machine tested:
e.g. mainframe, client/server>

Test Scenario
Description:

<Describe briefly what this test scenario is testing.>

Objective:

<Describe the desired objective of this test scenario.>

Assumptions/
Constraints:
Test Files/Test
Data:
Author:
Reviewed by:
Executed by:
Test Steps:
Step #

Retry #:

<A sequential number

representing the number of
times the test case has been
executed.>

<Identify the Process ID that this Test Scenario relates with>

<Enter the machine that will be used for this test, e.g. PC,
server>

<List any assumptions or constraints that the tester should be aware of.>
<List the test files and or test data in order to successful run this test scenario.>
<Identify the author of this Test Scenario>
<Identify the person who reviewed this Test
Scenario>
<Identify the person who executed this Test
Scenario>

Last Modified:
Reviewed Date:
Execution Date:

Description

<Update the date that the Test Scenario was last updated.>
<List the date that the Test Scenario was reviewed on.>
<List the date that the Test Scenario was last executed on.>

Expected Result

<Enter the description for each step of the test

<Use sequential
scenario. Fully describe what the tester should be
counting numbers>
doing on the application.>

<Enter the expected result of a

successful execution of each step.>

SDM - Test Scenarios Template

8

Actual Result
<Enter the actual result for each step. If
the actual result matches the expected
result, then enter the same information.>