|
On Wednesday 26 November 2003 19:24, rob@xxxxxxxxx wrote: > There actually are tools out there that will trace through your > program, and will even figure out how to test those little obscure > routines that you know can never be executed. Example > update (e) myfile; > if %status=.....; // the status code for matching record > ... > EndIf; > > I know these exist. I just don't know their names. If this is what > you are looking for please respond to the affirmative. Then perhaps > others can chime in. I'm not aware of any 'standard' routines for doing this, though I'm sure most of the testing suites include them. I wrote my own for checking RPG/400 & CL programs (ie OPM only) for what lines are executed, how many times, etc, which is available for download: http://www.dbg400.net/extras.html#runpgmtrc Regards, Martin -- martin@xxxxxxxxxx AIM/Gaim: DBG400dotNet http://www.dbg400.net /"\ DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open \ / Source free test environment tools and others (file/spool/misc) X Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news / \
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
