Information Technology Reference
In-Depth Information
name
testers
kick-off
scripts
planning
accesses
paths
all
partner
systems
error
tool
adresses
Fig. 7.11 Planning integration tests
Release and communication of system addresses,
Granting of the necessary access rights on alien systems,
Provisioning of exchange directories.
Figure
7.11
shows the integrative testing systematic.
Otherwise all criteria relevant to individual acceptance or for stand alone
interfaces apply correspondingly. Concerning the final acceptance document all
responsible persons of the partner systems should sign it.
7.4.4
Integrative Test Scripts
An important pre-condition already mentioned is the drafting of integrative test scripts.
Generally these will be developed by testers of the key system involved and consulted
upon with the partner systems. Figure
7.12
shows such a test script schematically.
It is important when applying such a test script that the sequence be kept so that
the necessary resources (testers and systems) can be provided at the right moment.
However, there are limits to exact scheduling. If problems occur during the test
sequence in a particular system or interface, unplanned delays will be the result.
Reasons can be manifold:
Configuration errors,
Customising problems,
Interface errors,
Software error in system A,
Software error in system B.
Sometimes even simple communication problems between participants suffice
to bring the sequence to a halt. Delays and problem solutions are the consequence.
In any case a delay means re-scheduling in the short term with all the difficulties to
keep resources at the ready.
The objective of integrative acceptance is not the acceptance of a system but the
acceptance of a complete process. For this reasons it is important that the signatures
