Template test scenario

TEST SCENARIO <TEST LEVEL/APPLICATION>

1.1

Test basis

Document

1.2

Author

Date

Version

The requisites

To start the test execution the following matters need to be present:

Minimal system requirements:

System configuration:

1.3

Product risks (from MTP)

1.
2.
3.
4.
5.

Sogeti Nederland B.V.

Augustl 20, 2008

1.0
1

Template test scenario

TEST SCENARIO

2.1

Intake test environment

An important stage in the test process is the test environment intake. This can be determined per environment or for the DTAP as a
whole. For DTAP the table below needs to be filled in for every environment.
Test environment: D/T/A/P *
Platform
Name Authorization requested Name
Name
Authorization delivered
Username
valid
Program
(date)
applicant manager (date)
(password) from/to
Database
Service
Workstation *
Pre-migration
Platform
Program
Database
Service
Workstation
Postmigration
Platform
Program
Database
Service
Workstation
* fill in what is called for

Sogeti Nederland B.V.

Augustl 20, 2008

1.0

pagina 2

Does it
work
correctly?
Yes/No

Template test scenario

2.2

Pretest

Name test script:

Which test cases:
Tested product risks:
Date execution:
Number of defects:
Defects related to the test configuration:
Defect
Solution

<Defects related to the test object need to be kept in the defect management tool. These defects are of no concern and will not stop
further testing. This is the judgment of the TC /TM. >
Go/No Go moment for continuing the test process.

Sogeti Nederland B.V.

Augustl 20, 2008

1.0

pagina 3

Template test scenario

Test scenario

2.3

1st test round <release number>

In the table below the executed tests are listed in logical order. It is important to keep this order during the test execution.
Nr.

Name test script

Test level

Which tests?

Tested product
risks

Start date

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Sogeti Nederland B.V.

Augustl 20, 2008

1.0

Expected
end date

% done

Number of
defects

Template test scenario

Test scenario

2.4

2nd test round <release number>

In the table below the executed tests are listed in logical order. It is important to keep this order during the test execution.
Nr.

Name test script

Test level

Which tests?

Tested product
risks

Start date

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Release advice:

Sogeti Nederland B.V.

Augustl 20, 2008

1.0

Expected
end date

% done

Number of
defects