Information Technology Reference
In-Depth Information
Release
Test Scenarios
Acceptance
Development Tests
PfT
Pilot Operation
Fig. 7.1 PfT interface testing
7.1.4.2
Integration into Test Phase
As already mentioned the acceptance test phase by the customer is preceded by
testing during development. During this earlier phase the developers themselves
carry out tests. In the course of quality assurance in the development team these
tests are documented in scripts.
To gain time in the acceptance test phase itself it has proven useful to let
representatives of the customer participate in these tests even before an interface
is officially provided for acceptance proper. This procedure is depicted in Fig.
7.1
.
7.1.4.3
Interface Acceptance: Time Schedule
PfT is the date of provisioning for tests. These tests are—as already mentioned—
internal tests. Before the official start of acceptance procedures the customer may
accompany these internal tests. This is a question of negotiation with the software
supplier. Since a timely implementation is generally of interest for both parties the
supplier normally is quite willing to let this happen.
Once the interface tests during development come to a positive result acceptance
may be granted under the condition of pilot operation. This makes sense since test
conditions during the development phase are different from formal customer
acceptance procedures. To be on the safe side a time window has to be defined
for this pilot operation under production conditions after putting the system into
service. During this time the usual warranty conditions of the supplier still have
validity (cost free amendments of possible errors popping up).
Step by Step Process
Altogether two scenarios can be envisaged which deliver the results so far discussed
in practise:
