Re: How to test a service program

["Carel Teijgeler" <coteijgeler@xxxxxxxxx>]

David,

Do not know where F1_SAVE is defined, global or locally in the
procedure(s)?

Some answers:
a) use different LFs in each procedures. LFs may have the same key fields,
which  mean they share the same access path.
b) define F1_SAVE locally with STATIC, if it has to be tested after a
second call to the same procedure.
c) use another design: one procedure to open the file, procedures P! and
P2, procedure to update the file (not tested this, but I would open, update
and close the file within the same procedure).

With regards,
Carel Teijgeler

*********** REPLY SEPARATOR  ***********

On 7-9-2009 at 11:47 David FOXWELL wrote:

> I was wondering how others get round the problem of multiple procedures
using the same files in a service program, or using global variables.
> Example :
>
> Procedure P1 updates file F1.
> Test program calls P1 then compares F1 with F1_SAVE.
> Developer adds P2 to service program which also updates F1.
> Test program now calls P1, then P2 then compares F1 with F1_SAVE.
>
> How are you making sure that the tests on each procedure are completely
isolated, eg, P2 does not modify the results from the test on P1?
>