<Project Name> - SDM Test Scenarios

Last Update: <Insert Date>

System and Integration Test Scenario

System and Integration Test Scenario # 1
<Tracking number associated
<A sequential number
with the module, or set of
<Version number of the representing the number of
Version #: Build #: modules, packaged together Retry #:
application being tested> that perform the function
times the test case has been
executed.>
tested by this test scenario>
<A sequential number assigned to this test scenario
Test Scenario ID: Process ID: <Identify the Process ID that this Test Scenario relates with>
for tracking purposes>
<Enter the environment this test scenario is using, <Enter the machine that will be used for this test, e.g. PC,
Environment: Machine tested:
e.g. mainframe, client/server> server>
Test Scenario
<Describe briefly what this test scenario is testing.>
Description:
Objective: <Describe the desired objective of this test scenario.>
Assumptions/
<List any assumptions or constraints that the tester should be aware of.>
Constraints:
Test Files/Test
<List the test files and or test data in order to successful run this test scenario.>
Data:
Author: <Identify the author of this Test Scenario> Last Modified: <Update the date that the Test Scenario was last updated.>
<Identify the person who reviewed this Test
Reviewed by: Reviewed Date: <List the date that the Test Scenario was reviewed on.>
Scenario>
<Identify the person who executed this Test
Executed by: Execution Date: <List the date that the Test Scenario was last executed on.>
Scenario>
Test Steps:
Step # Description Expected Result Actual Result
<Enter the description for each step of the test <Enter the actual result for each step. If
<Use sequential <Enter the expected result of a
scenario. Fully describe what the tester should be the actual result matches the expected
counting numbers> successful execution of each step.>
doing on the application.> result, then enter the same information.>

SDM - Test Scenarios Template

1
 <Project Name> - SDM Test Scenarios
Last Update: <Insert Date>

System and Integration Test Scenario

System and Integration Test Scenario # 2
<Tracking number associated
<A sequential number
with the module, or set of
<Version number of the representing the number of
Version #: Build #: modules, packaged together Retry #:
application being tested> that perform the function
times the test case has been
executed.>
tested by this test scenario>
<A sequential number assigned to this test scenario
Test Scenario ID: Process ID: <Identify the Process ID that this Test Scenario relates with>
for tracking purposes>
<Enter the environment this test scenario is using, <Enter the machine that will be used for this test, e.g. PC,
Environment: Machine tested:
e.g. mainframe, client/server> server>
Test Scenario
<Describe briefly what this test scenario is testing.>
Description:
Objective: <Describe the desired objective of this test scenario.>
Assumptions/
<List any assumptions or constraints that the tester should be aware of.>
Constraints:
Test Files/Test
<List the test files and or test data in order to successful run this test scenario.>
Data:
Author: <Identify the author of this Test Scenario> Last Modified: <Update the date that the Test Scenario was last updated.>
<Identify the person who reviewed this Test
Reviewed by: Reviewed Date: <List the date that the Test Scenario was reviewed on.>
Scenario>
<Identify the person who executed this Test
Executed by: Execution Date: <List the date that the Test Scenario was last executed on.>
Scenario>
Test Steps:
Step # Description Expected Result Actual Result
<Enter the description for each step of the test <Enter the actual result for each step. If
<Use sequential <Enter the expected result of a
scenario. Fully describe what the tester should be the actual result matches the expected
counting numbers> successful execution of each step.>
doing on the application.> result, then enter the same information.>

SDM - Test Scenarios Template

2
 <Project Name> - SDM Test Scenarios
Last Update: <Insert Date>

Regression Test Scenario

Regression Test Scenario # 1
<Tracking number associated
<A sequential number
with the module, or set of
<Version number of the representing the number of
Version #: Build #: modules, packaged together Retry #:
application being tested> that perform the function
times the test case has been
executed.>
tested by this test scenario>
<A sequential number assigned to this test scenario
Test Scenario ID: Process ID: <Identify the Process ID that this Test Scenario relates with>
for tracking purposes>
<Enter the environment this test scenario is using, <Enter the machine that will be used for this test, e.g. PC,
Environment: Machine tested:
e.g. mainframe, client/server> server>
Test Scenario
<Describe briefly what this test scenario is testing.>
Description:
Objective: <Describe the desired objective of this test scenario.>
Assumptions/
<List any assumptions or constraints that the tester should be aware of.>
Constraints:
Test Files/Test
<List the test files and or test data in order to successful run this test scenario.>
Data:
Author: <Identify the author of this Test Scenario> Last Modified: <Update the date that the Test Scenario was last updated.>
<Identify the person who reviewed this Test
Reviewed by: Reviewed Date: <List the date that the Test Scenario was reviewed on.>
Scenario>
<Identify the person who executed this Test
Executed by: Execution Date: <List the date that the Test Scenario was last executed on.>
Scenario>
Test Steps:
Step # Description Expected Result Actual Result
<Enter the description for each step of the test <Enter the actual result for each step. If
<Use sequential <Enter the expected result of a
scenario. Fully describe what the tester should be the actual result matches the expected
counting numbers> successful execution of each step.>
doing on the application.> result, then enter the same information.>

SDM - Test Scenarios Template

3
 <Project Name> - SDM Test Scenarios
Last Update: <Insert Date>

Regression Test Scenario

Regression Test Scenario # 2
<Tracking number associated
<A sequential number
with the module, or set of
<Version number of the representing the number of
Version #: Build #: modules, packaged together Retry #:
application being tested> that perform the function
times the test case has been
executed.>
tested by this test scenario>
<A sequential number assigned to this test scenario
Test Scenario ID: Process ID: <Identify the Process ID that this Test Scenario relates with>
for tracking purposes>
<Enter the environment this test scenario is using, <Enter the machine that will be used for this test, e.g. PC,
Environment: Machine tested:
e.g. mainframe, client/server> server>
Test Scenario
<Describe briefly what this test scenario is testing.>
Description:
Objective: <Describe the desired objective of this test scenario.>
Assumptions/
<List any assumptions or constraints that the tester should be aware of.>
Constraints:
Test Files/Test
<List the test files and or test data in order to successful run this test scenario.>
Data:
Author: <Identify the author of this Test Scenario> Last Modified: <Update the date that the Test Scenario was last updated.>
<Identify the person who reviewed this Test
Reviewed by: Reviewed Date: <List the date that the Test Scenario was reviewed on.>
Scenario>
<Identify the person who executed this Test
Executed by: Execution Date: <List the date that the Test Scenario was last executed on.>
Scenario>
Test Steps:
Step # Description Expected Result Actual Result
<Enter the description for each step of the test <Enter the actual result for each step. If
<Use sequential <Enter the expected result of a
scenario. Fully describe what the tester should be the actual result matches the expected
counting numbers> successful execution of each step.>
doing on the application.> result, then enter the same information.>

SDM - Test Scenarios Template

4
 <Project Name> - SDM Test Scenarios
Last Update: <Insert Date>

Load Test Scenario

Load Test Scenario # 1
<Tracking number associated
<A sequential number
with the module, or set of
<Version number of the representing the number of
Version #: Build #: modules, packaged together Retry #:
application being tested> that perform the function
times the test case has been
executed.>
tested by this test scenario>
<A sequential number assigned to this test scenario
Test Scenario ID: Process ID: <Identify the Process ID that this Test Scenario relates with>
for tracking purposes>
<Enter the environment this test scenario is using, <Enter the machine that will be used for this test, e.g. PC,
Environment: Machine tested:
e.g. mainframe, client/server> server>
Test Scenario
<Describe briefly what this test scenario is testing.>
Description:
Objective: <Describe the desired objective of this test scenario.>
Assumptions/
<List any assumptions or constraints that the tester should be aware of.>
Constraints:
Test Files/Test
<List the test files and or test data in order to successful run this test scenario.>
Data:
Author: <Identify the author of this Test Scenario> Last Modified: <Update the date that the Test Scenario was last updated.>
<Identify the person who reviewed this Test
Reviewed by: Reviewed Date: <List the date that the Test Scenario was reviewed on.>
Scenario>
<Identify the person who executed this Test
Executed by: Execution Date: <List the date that the Test Scenario was last executed on.>
Scenario>
Test Steps:
Step # Description Expected Result Actual Result
<Enter the description for each step of the test <Enter the actual result for each step. If
<Use sequential <Enter the expected result of a
scenario. Fully describe what the tester should be the actual result matches the expected
counting numbers> successful execution of each step.>
doing on the application.> result, then enter the same information.>

SDM - Test Scenarios Template

5
 <Project Name> - SDM Test Scenarios
Last Update: <Insert Date>

Load Test Scenario

Load Test Scenario # 2
<Tracking number associated
<A sequential number
with the module, or set of
<Version number of the representing the number of
Version #: Build #: modules, packaged together Retry #:
application being tested> that perform the function
times the test case has been
executed.>
tested by this test scenario>
<A sequential number assigned to this test scenario
Test Scenario ID: Process ID: <Identify the Process ID that this Test Scenario relates with>
for tracking purposes>
<Enter the environment this test scenario is using, <Enter the machine that will be used for this test, e.g. PC,
Environment: Machine tested:
e.g. mainframe, client/server> server>
Test Scenario
<Describe briefly what this test scenario is testing.>
Description:
Objective: <Describe the desired objective of this test scenario.>
Assumptions/
<List any assumptions or constraints that the tester should be aware of.>
Constraints:
Test Files/Test
<List the test files and or test data in order to successful run this test scenario.>
Data:
Author: <Identify the author of this Test Scenario> Last Modified: <Update the date that the Test Scenario was last updated.>
<Identify the person who reviewed this Test
Reviewed by: Reviewed Date: <List the date that the Test Scenario was reviewed on.>
Scenario>
<Identify the person who executed this Test
Executed by: Execution Date: <List the date that the Test Scenario was last executed on.>
Scenario>
Test Steps:
Step # Description Expected Result Actual Result
<Enter the description for each step of the test <Enter the actual result for each step. If
<Use sequential <Enter the expected result of a
scenario. Fully describe what the tester should be the actual result matches the expected
counting numbers> successful execution of each step.>
doing on the application.> result, then enter the same information.>

SDM - Test Scenarios Template

6