I have just noticed that this isnt really compatible with RPGUNIT
anyway, the Coverage report seems to only show the last test case that
is run as part of the process, not the whole run. I just ran the test
cases in reverse order and got a completely different report out, and
lines that are definitely covered bu the Unit test arent shown as being

I dont really fancy running the code coverage tool for each individual
test case, and RPGUNIT is our standard unit testing tool for APIs. So
this coverage checker isnt really appropriate for us Shame L



From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxx> [mailto:WDSCI-L
<wdsci-l-bounces@xxxxxxxxxxxx>] On Behalf Of darren@xxxxxxxxx
Sent: 06 June 2014 12:53
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi 9.1 Code coverage tool - Main Procedure not

They would appreciate it if you brought it up in an official PMR.

From: "Aaron Price" < Aaron.Price@xxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Date: 06/06/2014 05:25 AM
Subject: Re: [WDSCI-L] RDi 9.1 Code coverage tool - Main Procedure not
Sent by: "WDSCI-L" < wdsci-l-bounces@xxxxxxxxxxxx>

Thanks Buck,

Do I need to raise this with IBM, or will they pick it up from this



From: WDSCI-L < wdsci-l-bounces@xxxxxxxxxxxx> [mailto:WDSCI-L
< wdsci-l-bounces@xxxxxxxxxxxx>] On Behalf Of Buck Calabro
< kc2hiz@xxxxxxxxx>
Sent: 05 June 2014 18:24
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDi 9.1 Code coverage tool - Main Procedure not

On 6/5/2014 12:28 PM, Aaron Price wrote:

I have just tried the code coverage tool to check the coverage one of
our RPGUNIT test programs.

It seemed to work correctly for all subprocedures, however the
tool shows zero% coverage for all of the main procedure code (this
cannot be the case as the Main Procedure is what is calling the
subprocedures). The report shows the Main procedure code (including
*INZSR) all highlighted in Red and there is a 0% coverage item in the
Program tree.

I see the same thing. This appears to be an issue for programs with a
main procedure. Programs that use *ENTRY PLIST show coverage properly
in the 'mainline' section. For example, this shows 100% coverage:

d binary s 9b 0
d int s 10i 0
d uint s 10u 0

* all these occupy 4 bytes of storage
c eval binary = *hival
c eval int = *hival
c eval uint = *hival

c binary dsply
c int dsply
c uint dsply

This shows 0% coverage:

// *entry plist
dcmpfr1 pr extpgm('CMPFR1')
d inPrdFil 10
d inPrdLib 10

dcmpfr1 pi
d inPrdFil 10
d inPrdLib 10

// load work fields from input
prdFil = %trim(inPrdFil);
prdLib = %trim(inPrdLib);


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.