-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test coverage output #115
Comments
First of all, let me forward you to Medium articles where I demonstrated a "modern" SDLC: Integration of GCBLUnit that brings the concept of Test and Unit to the debugger (as well as output in JUnit format) is complicated by this - OlegKunitsyn/gnucobol-docker#2 (comment) Back to your question. The debugger colors executed lines in VSCode when the coverage is enabled. Coverage data parsed by gcov-parse are available in run-time, so you could implement an export functionality and propose a Pull Request. It would not be the "Test coverage", but better than nothing. |
Couldn't one create a simple task and execute `gcov ${filename}? there (test would be possible by opening the terminal and execute it there manually)? |
Hi @GitMensch, Noobie here but very interested in the value here and helping out. :) But I don't get the whole "gcov" thing. I'd tried read online, but I can't seem to find anything. Maybe you can point me out where and how I can use it with gnuCobol. I tried the following C:\workspace>cobc -v C:\workspace\cobol-check2>gcov -v C:\workspace>gcov ALPHA.cbl Thanks :) |
That seems like a side-note, something you may want to question at the GnuCOBOL discussion boards (it ends in "pass the correct coverage options to GCC via cobc, then run the program, then check the coverage). |
Hi @OlegKunitsyn,
Is it possible to get a report of the results of the Test coverage in an output ?
Like so to run in sonar.
Thanks!
The text was updated successfully, but these errors were encountered: