The following program, when run in code coverage, lists the return; in the
$Main procedure as not being executed.
ctl-opt Copyright('(C) Copyright Group Dekko Inc.')
ActGrp(*NEW) DftActGrp(*NO) ExprOpts(*RESDECPOS) DatFmt(*USA)
OPTION(*SRCSTMT:*NODEBUGIO:*NOUNREF) EXTBININT(*YES)
BndDir('ROUTINES/SRVPGM':'QC2LE');
//****************************************************************
// Begin Calculation Specifications
//****************************************************************
*InLR = *On;
callp $Main();
Return;
//**************************************************************
dcl-proc $Main;
//
//**************************************************************
dcl-s idx1 uns(3);
//************
idx1=1;
return;
end-proc $Main;
From: Edmund Reinhardt <edmund.reinhardt@xxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Date: 05/25/2015 10:25 AM
Subject: Re: [WDSCI-L] What is Code Coverage
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Darren,
We haven't been able to reproduce this behaviour. Would you have a sample
that shows this?
From: darren@xxxxxxxxx
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Date: 05/22/2015 03:07 PM
Subject: Re: [WDSCI-L] What is Code Coverage
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
That's a great overview, thank you. We don't test like that, but I could
see using it to be faster than debug to answer certain questions. Is it
normal that the 'return' opcode is never counted as executing? None of my
procedures hit 100% because the return opcode is considered not executed.
From: Edmund Reinhardt <edmund.reinhardt@xxxxxxxxxx>
To: Rational Developer for IBM i / Websphere
Development Studio
Client for System i & iSeries
<wdsci-l@xxxxxxxxxxxx>
Cc: Violaine Batthish <batthish@xxxxxxxxxx>
Date: 05/22/2015 12:03 PM
Subject: Re: [WDSCI-L] What is Code Coverage
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Darren,
What Code Coverage tells you is exactly which lines are executed by a
particular execution of your program. This is very useful in the context
of testing.
You can tell which branches/procedures/programs are being executed by your
testing.
Given this, you can tell
a) if your testing is not covering important cases.
b) if you have dead code that should be removed
This functionality has been delivered in RDi since 9.1 (May 2014)
What Test Optimizing Advisor gives in addition, is the ability to track
which testcase covered which line.
Given this ability the TOA can tell you
a) whether a testcase is redundant and not worth your time running
b) given the file you have modified as a developer, which test cases are
relevant and should be run
At COMMON, I heard that most shops were spending more than 1 day and half
of them were spending more than a week in running tests before release
their code. The TOA should help reduce this test burden, and make the
tests executed more relevant and save you time which is money.
Edmund
From: darren@xxxxxxxxx
To: "midrange-WDSC WDSC
message board"
<wdsci-l@xxxxxxxxxxxx>
Date: 05/22/2015 11:37 AM
Subject: [WDSCI-L] What is
Code Coverage
Sent by: "WDSCI-L"
<wdsci-l-bounces@xxxxxxxxxxxx>
Just saw a recent post from Edmund Reinhardt about a Test Optimizer, so I
look at the tutorial, and it talks about Code Coverage, which I thought was
a java only tool, but the tutorial shows some RPG programs. So, me being a
green screen programmer for a business centered around an MRP package, does
Code Coverage mean anything to me? I did try running a Code Coverage
Report against one of my programs, and I see a list of my sub-procedures
with various Coverage %s, but I don't see what that means to me.
--
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.
--
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.
--
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.
--
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.
midrange.com
