Re: RDi 9.1 Code coverage tool - Main Procedure not covered

I agree with Buck
Please open a PMR because there must be something unique about your
situation that we will need to have an in-depth conversation to reproduce.



Regards,

Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i



Phone: 1-905-413-3125 | Home: 1-905-854-6195 IBM
E-mail: edmund.reinhardt@xxxxxxxxxx
RDi YouTube: 8200 Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham, ON L6G 1C7
Find me on: LinkedIn: Canada
http://ca.linkedin.com/in/edmundreinhardt/






From: Buck Calabro <kc2hiz@xxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx,
Date: 10/06/2014 12:46 PM
Subject: Re: [WDSCI-L] RDi 9.1 Code coverage tool - Main Procedure not
covered
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



On 6/9/2014 6:02 AM, Aaron Price wrote:

I have once again tested this, but with no luck :(

Using the following procedure,
Right click on my program object > Code Coverage (prompt) > Batch
Leave all tabs at default except for:
https://dl.dropboxusercontent.com/u/3229426/start.png
and
https://dl.dropboxusercontent.com/u/3229426/Append.png

Teardown code is as follows:
https://dl.dropboxusercontent.com/u/3229426/Teardown.png

In the teardown code above the close mode of GetClientRate (which is the
API that I am running code coverage for) switches LR *on and returns
(which I suspect may be the cause of the issue ?!?)

Running the coverage gives me exactly the same results: No Main
procedure coverage at all (identified by buck as an issue with programs
with prototyped entry parameters) and coverage which only covers one of
the test cases.

Spooled output from the run shows that all test cases have run:

*** Tests from TSB.GETCLR ***
Success. 45 test cases, 131 assertions, 0 failure, 0 error.

Running the same RUCALLTST command with a breakpoint on one of the lines
which the coverage report shows in RED (Not Run), breaks during three of
the test cases, proving that this line is covered by multiple test
cases.

Try as I might, I cannot get my RDi to produce the same behaviour. I
wrote a simple RPG program that takes one parameter. If 'open' it does
a RETURN, if 'close' it sets on LR. Created a test, put the 'close' in
the teardown and fired it off. Append to previous shows each and every
test being called, not just the last one.

I suggest opening a PMR. I Bet the developers would love to understand
this behaviour and fix it. I'm going to be off the grid for a week, so
I can't do any more testing until I get back.

Thanks for your patience and participation!
--buck
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.