Re: Automatically exporting code coverage report

Hi Vern,Thanks for this. I checked and the CCZIPs are indeed PK files. They are basically a normal zip file containing snapshots of the source members at the point the code coverage was done, plus an xml that details which lines of code were hit.Thing is, RDi will use all that info to create a user-friendly html or pdf report. So, it would be possible to write something to unzip it and do that too, without involving RDi, but I was hoping there was already something out there.Many thanks for replyingJon
-------- Original message --------From: VERNON HAMBERG Owner <vhamberg@xxxxxxxxxxxxxxx> Date: 25/06/2024 15:17 (GMT+00:00) To: wdsci-l@xxxxxxxxxxxxxxxxxx Cc: jiddickson@xxxxxxxxx, wdsci-l@xxxxxxxxxxxxxxxxxx Subject: Re: [WDSCI-L] Automatically exporting code coverage report
Hello Jon
Is a CCZIP actually a PK-file? If you open it in WRKL NK and the first 2 letters are "PK", then it is. Then you could use JAR to unzip it and see what is there
HTHVern

On Tue, 25 Jun, 2024 at 4:46 AM, jiddickson via WDSCI-L <wdsci-l@xxxxxxxxxxxxxxxxxx> wrote: To: wdsci-l@xxxxxxxxxxxxxxxxxx
Cc: jiddickson@xxxxxxxxx
Hi, long time viewer, but first time poster here.On the IBMi, is there a way to programmatically generate a code coverage report (in PDF say)? So without doing manually in RDi.We're using CODECOV and starting to write unit tests, but would great if we could also automate that final step of exporting the CCZIP file to a PDF as evidence to attach to our ticket.From goggling, the nearest I could find was a shell script on the IBMz called ccexport.sh. That would do the trick, but we're on IBMi, and I couldn't find an equivalent.Many thanksJon