Information Technology Reference
In-Depth Information
7.4
Integrative Testing
7.4.1 Process Tests
Everything so far discussed about interface tests and simulations was done
from a purely technical point of view. The question was: do interfaces function
correctly, when transferring the requested number auf data records in a
given format? In this way all interfaces within a system network can be tested
successively. If no errors show up there is no technical reason why acceptance
should not be granted. This is the common attitude of developers and software
suppliers.
For the daily business based on software applications such a functioning
is indeed assumed. In action the interfaces, however, are transparent to the
user. His interest is a functioning process—in particular that part of a process
for which he is responsible in daily business. In this sense his interest is in the
factual result at the end of a process chain. And this requires an in-depth test
methodology.
In practise this means that tests have to be integrative for acceptance. Test cases
have to include all relevant sub-processes (including work instructions) on all
systems linked up by their mutual interfaces (Fig. 7.10 ). Only after the complete
chain has been passed with positive results, this part of a process can be regarded as
accepted. Interfaces will only be looked at individually when specific problems
have shown up during testing.
Integration Test
Integration Test
Functional Test
Functional Test
Export
Import
Export
System 1
System 2
Import
Export
Import
System 3
System 4
Functional Test
Functional Test
Integration Test
Fig. 7.10 Integrative testing
 
Search WWH ::




Custom Search