Re: How to test a service program

David,

Keep in mind that test drivers are not production applications. Rules
that apply to production applications, ie. all I/O is encapsulated in
business logic procedures, need not apply to a test driver.

If you unit testing P1, call P1 then check the results.
If you are unit testing P2, call P2 then check the results.
If you are integration testing P1 and P2 together, they should have
already passed the unit testing above. Thus, you know that P1 works.

-Charles

On Tue, Sep 8, 2009 at 10:36 AM, David FOXWELL<David.FOXWELL@xxxxxxxxx> wrote:

-----Message d'origine-----
De : rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Charles Wilt
procedures.  Also by definition, it's up to the programmer to
not only ensure that any global variables are used correctly,
but to define "correctly" in the first place!

Charles,

What about this kind of scenario :

Procedure P1 in a test program reads File1 and updates a record R1.

Later, another programmer writes P2 that also affects the same record, although that might be a completely unrelated task to that of P1.

The result of the test on procedure P1 might be lost, or worse, it may be assumed to be correct when it is actually the procedure P2 which is inducing the expected result.

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.