Thorbjørn, being that I believe Buck is doing mostly RPG with his XP
approach I was wondering if you were recommending "test-driven development"
for RPG and how you go about doing that. The reason I ask is I have my own
methods that I use where I call on Junit to make a Java Toolbox call to an
RPG *PGM on the iSeries which simply calls predefined programs and returns
whether or not they were successful (i.e. I wrap them in MONITOR blocks and
have predefined result fields I compare them to).

Was your comment based on RPG unit testing?

Aaron Bartell

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Thorbjørn Ravn Andersen
Sent: Friday, July 06, 2007 6:15 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] WDSC 6, Subclipse and iSeries projects

Buck skrev den 03-07-2007 16:55:
Version control like Subversion is a powerful tool that supports you in
organizing and saving software development projects.

I am going to try to use svn to _try_ some XP-like stuff, especially
'release often' and 'continuous integration.' I don't have a System i

I would suggest that you look into "test-driven development". Whenever you
need to write a callable routine start by writing the test, and first then
write the code which does what the test requests, then add more tests and
more code, with the continous goal that all tests pass.

This naturally includes error checking for bad input :)

For me, this has two very visible advantages - you design from "above"
instead from "beneath" giving cleaner code, and the unit tests document your
code afterwards!

Best regards,
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page