I have written something similar to this for a customer of mine,
which tested arbitrary routines (PL/1, ASSEMBLER, C). The interfaces of
the routines had to be defined to the system, and then the system could
run thousands of testcases, stored on PO members (optionally on DB2),
and compare the results with prior (good) results and show differences.
We also tried this for main programs, but because there is no interface
for main programs (input / output parameters), the use of this is
questionable, IMO.
The problem always is: what if the routines rely on "external" data
(VSAM or DB2)?
Two solutions:
a) run the tests on a test system, and restore the VSAM or DB2 data before
each run to a defined "initial" state; compare changes after the run with
"desired" changes (if the routines do updates on the data)
b) "intercept" the access routines (for example DSNHLI) and "simulate" the
DB2 accesses
We tried both, with some success on both. At the moment, I am working on
a project to support a) for another customer (freeze and restore database
contents).
Feel free to contact me offline, if you have questions.
Kind regards
Bernd
Am 16.03.2017 um 01:37 schrieb Frank Swarbrick:
Anyone use this feature of IBM Developer for z Systems (formerly Rational Developer for z
System)? Does it test only callable routines? Or can it also be used for your standard
"monolithic" COBOL program? What about CICS programs?
Frank
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
