My advice is testing is one of the toughest issues.
Mostly I see trivial to no testing.
Multiple libraries sounds like a possible advantage to your
situation, but I assume the test environment should model
the production environment.
Saving file data at critical points may be important so you
can have known/defined system state(s).
I suggest developing and maintaining test scripts so testing is
organized to hit all critical paths and avoid missing
critical functions.
A team approach sounds likely with your "whole chain of files",
both for time savings and having the right person(s) involved
with data entry and data analysis.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave
Sent: Tuesday, July 31, 2012 6:52 AM
To: RPG programming on the IBM i / System i
Subject: question on rpg testing
Hi all,
I'm interested in how people are going about their tests!
I'm creating a test library libA for pgmA.
PgmA will do a load of stuff then call other programs that will write to files, return, then pgmA will write just one or two files, all of which wil be in libA. All the called programs have their own test libraries.
Should one set up the library to only control the contents of the files written by PGMA or whole chain of files? It seems to me that the latter would make the library difficult to maintain if one of the called programs get modified.
--
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.
midrange.com
