coverage in json format

[brunolnetto]

Hi,

I am thankful for this repository and its many possibilities. I wrote the command below to improve kcov-habilities.

kcov --report-only --clean \
     --bash-dont-parse-binary-dir \
     --include-pattern=.sh \
     --exclude-pattern=tests \
     --include-path=. \
     ./coverage/ bats ./tests

In words, it generates on the current folder the folder coverage from the evaluation of the current folder itself, except the tests folder. It won't parse the binary directory for other scripts and will not accumulate data from multiple runs.

After the command run as above, I obtained the output available on my repository. During research, I saw some inconsistent information about kcov output. The most relevant, in my opinion, was the output in JSON format.

The command run kcov --version gives the output kcov 38, which means I have 2 versions behind the last version kcov 40. It is my greatest suspicion. What do you think?

[SimonKagstrom]

Do you really want --report-only here? The idea with that is to separate coverage collection (with --collect-only) from reporting, which is done with --report-only. Since this is bash, it might not make any difference, but I don't think that was what's intended?

What are the inconsistencies?

There have been bugfixes for later versions, but I'm not sure if it matches your descriptions.

[brunolnetto]

For now, I want to update kcov to its latest version kcov 40. We will see if it is enough.

[brunolnetto]

I could not update it manually. Repository says its latesy version is 40. How can I update it to this version?

[SimonKagstrom]

There is a docker image, which perhaps is the easiest way. https://hub.docker.com/r/kcov/kcov/

Otherwise, you'll have to build it from source.

[brunolnetto]

Badge docker build says no longer available. Should I trust it? These badges make kcov not trustworthy. We must work on it. The next question is: how?