OUM

TE.025 SYSTEM TEST SCENARIOS

<Company Long Name>
<Subject>

Author:

<Author>

Creation Date:

November 22, 2010

Last Updated:

January 27, 2011

Document Ref:

<Document Reference Number>

Version:

DRAFT 1A

Approvals:
<Approver 1>
<Approver 2>

TE.025 System Test Scenarios

Doc Ref: <Document Reference Number>

January 27, 2011

DOCUMENT CONTROL
1.1

Change Record
3

Date

Author

Version

Change Reference

22-Nov-10

<Author>

Draft 1a

No Previous Document

1.2

Reviewers

Name

<Subject>
File Ref: 197262650.doc

Position

<Application Name> Defect Report

(v. DRAFT 1A )

6 of 3

TE.025 System Test Scenarios

Doc Ref: <Document Reference Number>

January 27, 2011

Contents

1 Document Control...................................................................................................................... ii
1.1 Change Record......................................................................................................................... ii
1.2 Reviewers.................................................................................................................................. ii
2 Introduction................................................................................................................................ 1
2.1 Scope and Purpose................................................................................................................... 1
2.2 How to Review.......................................................................................................................... 1
2.3 Related Documents................................................................................................................... 1
3 <Application Name> Test Scenario.......................................................................................... 2
3.1 System Test Scenarios for <area>............................................................................................ 2
4 <Application Name> Defect Report.......................................................................................... 3

<Subject>
File Ref: 197262650.doc

<Application Name> Defect Report

(v. DRAFT 1A )

6 of 3

Doc Ref:

INTRODUCTION
2.1 Scope and
Purpose
This document details the test scenarios that will be used in the execution of the task, TE.070
Perform System Test.
The purpose of a test scenario is to identify and communicate steps that should be performed, their
expected results, and under which conditions the test scenario should run. Test scenarios are
necessary to verify successful and acceptable implementation of the requirements.

2.2

How to Review

Please use the following criteria when reviewing the System Test Scenarios:

Have all System Test Scenarios described in the System Test Plan been detailed, or has
there been explained why there is a discrepancy?

Are the System Test Scenarios related to specific use case scenarios or other type of
requirements?

Is there for each scenario described test steps in sufficient detail for a tester to
understand without consulting others?

Is there for each scenario step described an understandable expected outcome?

Have the pre-conditions for the execution of the scenarios been described?

Has the required test data been described for each test scenarios?

2.3 Related
Documents
This document is related to the following document:

The System Test Plan (TE.050) contains the list of test scenarios that are detailed in this
document.

<Application Name> Defect Report

File Ref: 197262650.doc

(v. )

6 of 3

Doc Ref:

<APPLICATION NAME> TEST SCENARIO

3.1 System Test

Scenarios for <area>
Test Scenario ID
Requirement(s)

Test Scenario Name

<Indicate the requirement(s) that is tested under this scenario. This could for example be a system use case
scenario, but could also be some other requirement, such as a supplemental requirement.>

Revision History
Date

Author

Version

Description
Test Case created.

Objectives
Test Setup
Requirements
Pre-conditions
Test Data
Variable

Values

Test Procedure
Step #

Step Details

Expected Result

01
02
03
Comments
Actual Results

<PASS/FAIL/SKIPPED>

Completed
Signed Out
Test Log
Date

Tester Name

Actual Results
(Pass/Fail)

Comments

<Application Name> Defect Report

File Ref: 197262650.doc

(v. )

6 of 3

Doc Ref:

<APPLICATION NAME> DEFECT REPORT

The following provides a template to report defects found during the execution of the test cases.

Defect Form
Test Case ID
Report Type:
Problem Summary:
Environment:

Version & Release Number

Severity: Low/Medium/High/Urgent

Reported by:
Date:
Detailed Description:

How to Reproduce:

Assigned to Developer:

Completion Date:

Status:

Priority:

Resolution:

Cost/Time to Fix:
Authorization:
Date:
Re-tested by:
Date:
Page __ of ___

<Application Name> Defect Report

File Ref: 197262650.doc

(v. )

6 of 3