Input Map

From dis-Emi-A

The Input Map is a global asset to a software package which helps in identifying relevant tests to be done on any given input in the system. The production, and use, of the input map is done as part of Test Suite Construction.

Contents 1 Input Types 2 Context 3 Map Listing 4 String 5 Domain ~ String 6 Email ~ String, Domain

Input Types

All inputs in the system need to have a specific type, and in general more than one type applies to the input. It is important, for ease of reference, that all the types have a unique name.

If multiple types do apply, then generally one is more a specific form of another one, so a simple hierarchy forms. For example, if entering an email address of a recipient we have:

Email Address ~ String

This indicates that (for input) the email address is additionally a string input, thus identifying further tests for this input.

Context

For some inputs used in many locations in the software, that context of the use is also important in deciding what needs to be tested. In these cases it is important to note that context in the input map.

Map Listing

The listing should be kept fairly simple. It needs to reference the types, the special features which apply to the type, and a reference to the source of that requirement.

Here is a simple example. A form suitable to the software used to manage the list is recommended; the syntax/form used here is optimal for the WikiMedia.

String min length max length Domain ~ String a real domain {REQ:3748} Email ~ String, Domain on a global blacklist {REQ:3213}