Hi Sam,

There are cases where the CC may not complete or give no results when the
SEP is placed on a module that gets hit later, this is being fixed but for
now make sure that the SEP is on the initial program that is run. You can
then control the CC with the CC launch config - right-click on the SEP to
modify the launch config.


Mike Hockings, M.Eng., P.Eng.
DevOps for Enterprise
IBM Developer for z Systems and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
voice 1-905-413-3199 T/L 313-3199 ITN 23133199

From: Sam Byrd <sbyrd@xxxxxxxxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxxxxxxxx
Date: 2020/03/05 11:17
Subject: [EXTERNAL] [WDSCI-L] iRPGUnit and Code Coverage
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>

We're having a problem using RDI 9.6 / RPGUnit 3.x and the iRPGUnit plugin
to obtain code coverage results.

Basically, I create SEPs on all of my service programs

(test suite as well as the business logic itself), I have it set to be in
code coverage mode. On the iRPGUnit tab I'm in debug mode).

When I right click on my test suite service program and ask it to run it
using RPGUnit it runs, but no code coverage data is captured. If instead
of code coverage mode I pick debug mode it's also not breaking.

Everything (and that includes the RPGUnit pieces) has been recompiled to
include debug information.

Anyone have any ideas?

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@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,

or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives

Help support midrange.com by shopping at amazon.com with our affiliate

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.