|
Alan
The original code coverage launched through RDi used the RDi debug technology and had the ability to access remote source. But the feedback we received was that it was too slow and people wanted to run it unattended as part of a build pipeline. So we developed the CODECOV command and gave it away for free. Written in C++ and all contained on the IBM i, it was a good fit for CI/CD pipelines. It does have the limitation that it does not look outside of the machine it is running on.
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Alan Cassidy <cfuture@xxxxxxxxxxx>
Date: Tuesday, March 21, 2023 at 10:13 AM
To: wdsci-l@xxxxxxxxxxxxxxxxxx <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [WDSCI-L] Coee Coverage wtih object and source on different systems
Thanks a lot, Edmund.
I thought I had remembered an "in-house" presentation by someone from
work here that showed remote Code Coverage, so my memory now stands
corrected.
There are rules here, so I'll now have to see if I can copy enough data
to the Development box to do this with, or try to make do with regular
debug, but it's not very clear at all in the program I'm working on.
--Alan
On 3/21/2023 9:57 AM, Edmund Reinhardt wrote:
Hello Alan--
I asked the CODECOV developer and this is the response.
This is not possible in the current implementation. CODECOV depends on CCA tools to run the actual code coverage collection. CCA uses some core components in STRDBG to drive a low level debug session. The CCA layer does not have network communication capability. It does not have a way to retrieve source on a different system
Sorry
Edmund Reinhardt
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Alan Cassidy <cfuture@xxxxxxxxxxx>
Date: Sunday, March 19, 2023 at 10:06 AM
To: wdsci-l@xxxxxxxxxxxxxxxxxx <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] [WDSCI-L] Coee Coverage wtih object and source on different systems
(--I posed the following to the RPG list (with no replies) but just
realized it fits better here.--)
The only thing I could find on Code Coverage was Guarino's three-part
videos on Youtube showing how it works.
I have run programs using Debug on our Production machine, setting it up
to look at the source code on our Development box.
But I need a little more guidance in how to have CODECOV work to
generate a results file using the source on a different box. Debug okay.
But command-line CODECOV command doesn't have an option for that. I've
been trying and trying to just do it in RDi (with remote-IBM i box
source) but can't get it.
I followed Guarino's example but he has source and object on the same
system. My source is on a different machine. I've used debug in that
context, but can't seem to get it for Code Coverage. Any help or
reference is appreciated.
-Alan Cassidy
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l .
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l .
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
