Test Dossier Template

Name of Best Practice / Test Dossier Template
File Name / BiSL_BP002
Date modified / 16-11-2006
Description of contents / Template for a test dossier that can be used in the performance of an acceptance test.
Type of document / Template
BiSL Processes / Review and testing
Comments

ASL BiSL Foundation

P.O. Box 9769

3506 GE Utrecht

The Netherlands

T+31 (0) 30 753 1424

F+31 (0) 30 755 1502

Test Dossier Template
Place / City
Date / dd mm yyyy
Author / Author
Status / Status

Table of contents

1General test dossier <Information system>

1.1Introduction

1.1.1General

1.1.2General functionality and data test

1.1.3Graphical Interface test

1.1.4Output test

1.2General functionality and data test

1.2.1Introduction

1.2.2General

1.2.3Functionality test

1.2.4Data test

1.3Graphical Interface test

1.3.1Introduction

1.3.2Objective

1.3.3General screen operation (example)

1.3.4Screen component test status during start-up (example)

1.3.5Correct screen actions test (example)

1.4Input / Output test

1.4.1Introduction

1.4.2Input types

1.4.3Output types

1.4.4General input / Output tests

1.4.5Testing of data in tables

1.4.6Input "Data File" tests

1.4.7"Overview / List" output tests

1.4.8"Text File" output tests

1.4.9Output "Data File" tests

2<Information system> <module> test dossier

2.1Introduction

2.1.1General

2.1.2Specific issues

2.2General functionality and data test

2.2.1Basic Principles

2.2.2Functionality test

2.3Graphical Interface test

2.3.1Screen list

2.3.2Deviations from General <Information System> Test Dossier

2.4Input / Output test

2.4.1Input

2.4.2Output

2.4.3Database actions (CRUD matrix)

2.4.4Deviations from General <Information System> Test Dossier

Version Management

Version / Date / Author / Description
0.1 / Working Group
BISL Best Practices / Initial document

Distribution List

Version / Date / To
0.1

1General test dossier Information system

1.1Introduction

1.1.1General

This general test dossier is intended for recording information common to all test dossiers centrally, sothat it does not need to be recorded in each individual test dossier.

The structure of this document is the same as that of a physical test dossier, enabling relevant general information can be found quickly.

Test dossiers are used to check whether the intended functionality of a module has actually been realized and that it functions correctly.

Because a module has numerous facets, we can divide the test into a number of separate tests geared towards specific facets:

General functionality and data test.
Graphic Interface test.
Output test.

This general test dossier describes the general requirements that apply with regard to these matters.

1.1.2General functionality and data test

Module test dossiers contain a decision diagram for each function, distinguishing the different test cases, without examining the physical test data.The test cases concern the functional requirements, as well as the constraints at levels 2 and 3.

As regards the data, this dossier details the relevant permanent requirements.i.e. the level-1 constraints.

1.1.3Graphical Interface test

Modules usually have one or more graphical interfaces at their disposal for communications with the end user.This test dossier details the general requirements that the screens within<information system> must fulfil.

Furthermore, general decision diagrams detail the test criteria for the various types of screen actions.Thefollowing screen actions can be distinguished:selection and post-selection / browsing, addition, changing and deletion.Any deviations must be must be analysed and tested.

1.1.4Output test

Output tests concern the general requirements that apply to the output of a module.

1.2General functionality and data test

1.2.1Introduction

This chapter details the general requirements that the testing of a function within a module of the <information system> must fulfill.

1.2.2General

Firstly, the points of departure for the tests must be formulated.These include the tables that must befilled in.

1.2.3Functionality test

A solution must be provided for the functions featured in the module.The following must be elaborated foreach function:

A list of the possible access paths to the function.
A decision diagram showing the desired operation of the function, as well as the constraints atlevels 2 and 3. The diagram must detail the conditions and subsequent actions ("Processing"or"Error Notification").
Any deviations from the general test dossier.

1.2.4Data test

The data in a module can be made subject to general permanent requirements that form a basis for the testing of a standard.i.e. the level-1 constraints supplemented with the requirements for specific fields.This pertains specifically to:

Field / General test(s)
Date field / Has a valid date been entered?
Numerical field / Have only figures been entered?
Text field / Have only letters been entered?
Memo field / Is the memo field long enough for entry of the general data?

1.3Graphical Interface test

1.3.1Introduction

This chapter details the general requirements that the screens must fulfil.Furthermore, general decision diagrams detail the test criteria for the various types of screen actions.The following screen actions canbe distinguished:selection and post-selection / browsing, addition, changing and deletion.

1.3.2Objective

The screens must comply with the <standards> as described in <document>.

1.3.3General screen operation (example)

Each <information system> module features standard functionalities, such as the selection of a record and a subsequent action, or the keeping of a record.

This chapter describes the following general functionalities:

"Select record" functionality
"Keep record" functionality

"Select record" functionality

Description of functionality

The objective of this function is to display records from a table in a list from which an end user can select one or more records.

The end user can perform and action on the selected records, such as maintenance (display, change ordelete).The end user can also choose to create a model document for one or more selected records.

"Select record" functionality decision diagram

The decision diagram below describes a normal selection functionality that is not part of another functionality, i.e. a browser screen.

Conditions / 01 / 02 / 03 / 04 / 05 / 06 / 07 / 08 / 08 / 09
1 record selected / - / Y / Y / Y / Y / N / - / - / - / -
>1 record selected / - / N / N / N / N / Y / - / - / - / -
Add Record function selected / Y / N / N / N / N / N / N / N / N / N
Display Record function selected / N / Y / N / N / N / N / N / N / N / N
Change Record function selected / N / N / Y / N / N / N / N / N / N / N
Delete Record function selected / N / N / N / Y / N / N / N / N / N / N
Model Documents function selected / N / N / N / N / Y / Y / N / N / N / N
Search function selected / N / N / N / N / N / N / Y / N / N / N
Cancel function selected / N / N / N / N / N / N / N / Y / N / N
Sort function selected / N / N / N / N / N / N / N / N / Y / N
Actions
Add Record (functionality maintenance) / X / . / . / . / . / . / . / . / . / .
View Record (functionality maintenance) / . / X / . / . / . / . / . / . / . / .
Change Record (functionality maintenance) / . / . / X / . / . / . / . / . / . / .
Delete Record (functionality maintenance) / . / . / . / X / . / . / . / . / . / .
Start Model Document functionality / . / . / . / . / X / X / . / . / . / .
Start Search functionality / . / . / . / . / . / . / X / . / . / .
Cancel search criteria / . / . / . / . / . / . / . / X / . / .
Sort records / . / . / . / . / . / . / . / . / X / .

The decision table below describes a limited selection funtionality that is not part of another functionality, usually a "Maintenance" functionality.

Conditions / 01 / 02 / 03 / 04
1 record selected / - / Y / Y / Y
Add Record function selected / Y / N / N / N
Display Record function selected / N / Y / N / N
Change Record function selected / N / N / Y / N
Delete Record function selected / N / N / N / Y
Actions
Add Record / X / . / . / .
View Record / . / X / . / .
Change Record / . / . / X / .
Delete Record / . / . / . / X

"Search" functionality decision diagram

The extensive selection functionality enables use of the search functionality to limit the number of records displayed in the selection functionality.

The decision table below describes the Search functionality:

Conditions / 01 / 02 / 03 / 04 / 05 / 06 / 07
0 Selection criteria entered / Y / Y / N / N / N / N / -
>=1Selection criteria entered / N / N / Y / Y / Y / N / -
Order OK / Y / N / Y / Y / N / Y / N
Cancel order / N / Y / N / N / Y / N / N
Data OK / - / - / Y / N / - / - / -
Actions
Check data / . / . / X / X / . / . / .
Report errors / . / . / . / X / . / . / .
Close function / X / X / X / . / X / X / .
Refresh record list in browser / . / . / X / . / . / . / .

"Maintain record" functionality

Description of functionality

A record can be added or deleted in the database. Furthermore, the data in a record can be viewed orchanged.

The "Apply" command in the table below is essentially the same as the "Save" command, the only difference being that the functionality is not closed after the "Apply" command.

"Maintain record" functionality decision diagram

Conditions / 01 / 02 / 03 / 04 / 05 / 07 / 09 / 10 / 11 / 12 / 13 / 15 / 16 / 17 / 18 / 19
Add mode / Y / Y / Y / Y / Y / N / N / N / N / N / N / N / N / N / - / N
View mode / N / N / N / N / N / Y / N / N / N / N / N / N / N / N / - / N
Change mode / N / N / N / N / N / N / Y / Y / Y / Y / Y / N / N / N / - / N
Delete mode / N / N / N / N / N / N / N / N / N / N / N / Y / Y / Y / - / N
Save delete/command / Y / Y / N / N / N / N / Y / Y / N / N / N / Y / Y / N / N / -
Apply command / N / N / Y / Y / N / N / N / N / Y / Y / N / N / N / N / N / -
Cancel/close command / N / N / N / N / Y / Y / N / N / N / N / Y / N / N / Y / N / -
Data OK / Y / N / Y / N / - / - / Y / N / Y / N / - / Y / N / - / - / -
Actions
Check data / X / X / X / X / . / . / X / X / X / X / . / X / X / . / . / .
Report errors / . / X / . / X / . / . / . / X / . / X / . / . / X / . / . / .
Save data / X / . / X / . / . / . / X / . / X / . / . / . / . / . / . / .
Delete data / . / . / . / . / . / . / . / . / . / . / . / X / . / . / . / .
Discard changes / . / . / . / . / X / . / . / . / . / . / X / . / . / . / . / .
Update transaction files / X / . / X / . / . / . / X / . / X / . / . / X / . / . / . / .
Close function / X / . / . / . / X / X / X / . / . / . / X / X / . / X / . / .

1.3.4Screen component test status during start-up (example)

Browserscreen test

The decision diagram below concerns a screen featuring extensive selection functionality:

Conditions / 01 / 02 / 03 / 04 / 05 / 07 / 09 / 10 / 11 / 12 / 13 / 14 / 15 / 16 / 17
authorized / Y / Y / Y / Y / Y / Y / Y / Y / Y / Y / Y / Y / Y / Y / N
Records table to be displayed / Y / Y / Y / Y / Y / Y / N / N / N / N / N / N / N / N / -
Criteria for table to be displayed in place / Y / Y / Y / Y / N / N / Y / Y / Y / Y / N / N / N / N / -
Model docs for table to be displayed in place / Y / Y / N / N / Y / N / Y / Y / N / N / Y / Y / N / N / -
Sorting for table to be displayed in place / Y / N / Y / N / - / - / Y / N / Y / N / Y / N / Y / N / -
Actions
Display records in list / X / X / X / X / X / X / . / . / . / . / . / . / . / . / .
Add button enabled / X / X / X / X / X / X / X / X / X / X / X / X / X / X / .
Display button enabled / X / X / X / X / X / X / . / . / . / . / . / . / . / . / .
Change button enabled / X / X / X / X / X / X / . / . / . / . / . / . / . / . / .
Delete button enabled / X / X / X / X / X / X / . / . / . / . / . / . / . / . / .
Make Selection button enabled / X / X / X / X / . / . / X / X / X / X / . / . / . / . / .
Cancel Selection button enabled / . / . / . / . / . / . / . / . / . / . / . / . / . / . / .
Sorting field filled in and enabled / X / . / X / . / X / . / X / . / X / . / X / . / X / . / .

The decision diagram below concerns a screen featuring limited selection functionality:

Conditions / 01 / 10 / 17
authorized / Y / Y / N
Records table to be displayed / Y / N / -
Actions
Display records in list / X / . / .
Add button enabled / X / X / .
Display button enabled / X / . / .
Change button enabled / X / . / .
Delete button enabled / X / . / .

<Following default screen> test

<……………>

1.3.5Correct screen actions test (example)

First of all, the screens must be listed in the order in which they are displayed and subsequently categorized according to the screen actions they can feature.Specifically:

Screen / Screen action
<Screen 1> / Browser screen
<Screen 2> / Display / Add / Change / Delete
… / …

The various screen actions must subsequently be tested according to the tables below:

Selection / post-selection / browser screen test

This screen features extensive selection functionality.

Conditions / 1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 / 9
authorized / Y / Y / Y / Y / Y / Y / Y / Y / N
Menu/Button:Add / Y / N / N / N / N / N / N / N / -
Menu/Button/Double-click grid:View / N / Y / N / N / N / N / N / N / -
Menu/Button:Change / N / N / Y / N / N / N / N / N / -
Menu/Button:Delete / N / N / N / Y / N / N / N / N / -
Sorting selected / N / N / N / N / Y / N / N / N / -
Additional selection made / N / N / N / N / N / Y / N / N / -
Close screen / N / N / N / N / N / N / Y / N / -
Actions
Modification:Add / X / . / . / . / . / . / . / . / .
Modification:View / . / X / . / . / . / . / . / . / .
Modification:Change / . / . / X / . / . / . / . / . / .
Modification:Delete / . / . / . / X / . / . / . / . / .
Refresh record list / X / . / X / X / X / X / . / . / .
Previous screen / . / . / . / . / . / . / X / . / .
Do nothing / . / . / . / . / . / . / . / X / X

Modification screen test

Conditions / 1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 / 9
Mode:Add / Y / Y / Y / Y / Y / Y / Y / Y / N
Button:OK / Y / Y / N / N / N / N / N / N / -
Button:Cancel / N / N / Y / N / N / N / N / N / -
Button:Apply / N / N / N / - / Y / N / N / N / -
Button:Help / N / N / N / N / N / Y / N / N / -
Screen closed / N / N / N / N / N / N / Y / N / -
Constraint triggered / Y / N / N / Y / N / N / N / N / -
Actions
Add Record / . / X / . / . / X / . / . / . / .
Previous screen / . / X / X / . / . / . / X / . / .
Other screen mode / . / . / . / . / X / . / . / . / .
Display help / . / . / . / . / . / X / . / . / .
Report error / X / . / . / X / . / . / . / . / .
Do nothing / . / . / . / . / . / . / . / X / X
Conditions / 1 / 2 / 3 / 4 / 5
Mode:View / Y / Y / Y / Y / N
Button:Close / Y / N / N / N / -
Button:Help / N / Y / N / N / -
Close screen / N / N / Y / N / -
Actions
Previous screen / X / . / X / . / .
Display help / . / X / . / . / .
Do nothing / . / . / . / X / X
Conditions / 1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 / 9
Mode:Change / Y / Y / Y / Y / Y / Y / Y / Y / N
Button:OK / Y / Y / N / N / N / N / N / N / -
Button:Cancel / N / N / Y / N / N / N / N / N / -
Button:Apply / N / N / N / - / Y / N / N / N / -
Button:Help / N / N / N / N / N / Y / N / N / -
Close screen / N / N / N / N / N / N / Y / N / -
Constraint triggered / Y / N / N / Y / N / N / N / N / -
Actions
Change Record / . / X / . / . / X / . / . / . / .
Previous screen / . / X / X / . / . / . / X / . / .
Display help / . / . / . / . / . / X / . / . / .
Report error / X / . / . / X / . / . / . / . / .
Do nothing / . / . / . / . / . / . / . / X / X
Conditions / 1 / 2 / 3 / 4 / 5 / 6 / 7
Mode:Delete / Y / Y / Y / Y / Y / Y / N
Button:OK / Y / Y / N / N / N / N / -
Button:Cancel / N / N / Y / N / N / N / -
Button:Help / N / N / N / Y / N / N / -
Close screen / N / N / N / N / Y / N / -
Constraint triggered / Y / N / N / N / N / N / -
Actions
Delete Record / . / X / . / . / . / . / .
Previous screen / . / X / X / . / X / . / .
Display help / . / . / . / X / . / . / .
Report error / X / . / . / . / . / . / .
Do nothing / . / . / . / . / . / X / X

1.4Input / Output test

1.4.1Introduction

This chapter describes the general requirements that the output generated by the module must fulfil.

1.4.2Input types

The following input types can be distinguished:

< List of examples of input types used in the information system>

Data input using the keyboard:see chapters 2 and 3
Data in the tables
Data file from another information system.

1.4.3Output types

The following outpur types can be distinguished:

< List of examples of output types used in the information system>

Data in the tables
Hard copy overviews and/or lists
Text file for reading data into a word processor
Data file for processing in another information system.

1.4.4General input / Output tests

A list must be made of the input files and the output generated by the module (with the exception of the tables), categorizing the files and output by type.Specifically:

Screen / Type
Input 1 / Data file
Output 1 / List
Output 2 / <Word processor> text file
Output 4 / Data file

1.4.5Testing of data in tables

The consequences for the tables from the execution of the different functions within a module are detailed in a CRUD matrix.CRUD stands for Create, Read, Update and Delete.i.e. the possible processes for the data in the tables.This is detailed for each function and entity.

1.4.6Input "Data File" tests

The following general tests must be performed on an Input Data File:

Item / General Tests
Appellation / Does the data file have a name?
Extension / Is the file extension correct?
Delimiters / Have the delimiters been correctly placed in the data file?
Start/Trailer Record / Does the data file have a header and trailer record?

1.4.7"Overview / List" output tests

The following general tests must be performed on an Overview/List:

Item / General Tests
Appellation / Does the overview have a name?Is this suitable?Is it stated on every page?
Date / Has a creation date been stated?Is it stated on every page?
Numbering / Has every page been numbered?
Layout / Does it comply with the applicable standards within <information system>?

1.4.8"Text File" output tests

The following general tests must be performed on an Textt File:

Item / General Tests
Appellation / Does the text file have a name?
Extension / Is the file extension correct?
Format / Does the file have the format required for the relevant word processor?

1.4.9Output "Data File" tests

The following general tests must be performed on an Output Data File:

2<Information system> <module> test dossier

2.1Introduction

2.1.1General

This test dossier specified which tests must be performed on the<information system> <module>.Theseare divided as follows:

General functionality and data test.
Graphic Interface test.
Input / Output test.

This detailing does not deviate from the requirements as described in the general test dossier.

2.1.2Specific issues

None.

2.2General functionality and data test

2.2.1Basic Principles

2.2.2Functionality test

The following functions can be distinguished in this module:

<Function A>
<Function B>
<Et cetera>

<Function A>

Possible access paths

<Function A> test cases

<One or more decision diagrams state which action ("Process" or "Error Notification") the function mustperform and under which condition.

The conditions can among other things include the fields that have and have not been filled in, and information as to whether the values entered are correct, and/or whether the values in the fields are consistent with one another.>
<Example decision diagram with test cases:>

Conditions / 1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 / 9
<Field 1> filled in / Y / Y / Y / Y / Y / Y / Y / Y / N
<Field 2> filled in / Y / Y / Y / Y / Y / Y / Y / N / -
<………> / Y / Y / Y / Y / Y / Y / N / - / -
<………> / Y / Y / Y / Y / Y / N / - / - / -
<Field 1> <= <Field 2> / Y / Y / Y / Y / N / - / - / - / -
<………> / Y / Y / Y / N / - / - / - / - / -
<………> / Y / Y / N / - / - / - / - / - / -
<………> / Y / N / - / - / - / - / - / - / -
Actions
Processing / X / . / . / . / . / X / . / . / .
Error notification / . / X / X / X / X / . / X / X / X

Deviations from General <Information System> Test Dossier

<Function B>

Possible access paths

<………>

Test cases

<………>

Deviations from General <Information System> Test Dossier

<……….>

<Et cetera>

2.3Graphical Interface test

2.3.1Screen list

The following screens are used in this module:

Screen / Screen action
<Information system> main screen / (Menu screen)
<Screen 1> / Display / Add / Change / Delete
<Screen 2> / Browse
<Screen 3> / Display / Add / Change / Delete / Browse
<………….> / <……………>

2.3.2Deviations from General <Information System> Test Dossier

2.4Input / Output test

2.4.1Input

The <Module> has no other input than the input via the screen.

2.4.2Output

The <Module> generates the following specific output:

Output / Type
<Output 1> / <Type a>
<Output 2> / <Type b>
<………..> / <………>

<Output types can include the following:data in the tables, hard copy lists, text files, data files.See also:General <information system> test dossier, section 4.3>

2.4.3Database actions (CRUD matrix)

The consequences for the entities from the execution of the different functions within the module are dislplayed in the following table.

Function / Entity / <Table 1> / <Table 2 / Table 3> / <…….>
<Function A> / C / - / R / -
<Function B> / - / I / R / D
<…………> / R / - / C / -

(Create, Read, Update, Delete)

<Table 2>description of table 2 content>

<……….

2.4.4Deviations from General <Information System> Test Dossier

1/17