Aggregation of coverage measurements for code with ifdef

[peter-toft-greve]

I have tried to raise a question on how to aggregate coverage measures for code with ifdef
in https://stackoverflow.com/questions/58632496/how-to-get-100-coverage-with-gcovr-with-ifdef-code
Basically - how can I summarize or aggregate test results from my code when tested with different
compile options. I cannot make this work.

I guess that I probably should have asked here directly.
If answered I will cross-answer the stackoverflow my self.

[latk]

I saw your StackOverflow question, and it motivated me to finally release the necessary functionality (it had already been implemented for a while). Please see the documentation on combining/merging coverage data: https://gcovr.com/en/stable/guide.html#combining-tracefiles In a nutshell, you create a JSON report with the coverage of each configuration, and can then use the -a/--add-tracefile option to merge the JSON files, and create your desired report format. This requires that you update to gcovr 4.2.

…

On Wed, 6 Nov 2019 at 08:07, Peter Toft ***@***.***> wrote: I have tried to raise a question on how to aggregate coverage measures for code with ifdef in https://stackoverflow.com/questions/58632496/how-to-get-100-coverage-with-gcovr-with-ifdef-code Basically - how can I summarize or aggregate test results from my code when tested with different compile options. I cannot make this work. I guess that I probably should have asked here directly. If answered I will cross-answer the stackoverflow my self. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#338?email_source=notifications&email_token=AANTJD76RJAJ7REDGJHM5WDQSJULFA5CNFSM4JJQUET2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HXELTEQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANTJD6CFXBSTLVXDXP6UQTQSJULFANCNFSM4JJQUETQ> .

[peter-toft-greve]

@latk This sounds brilliant. Will test as the first thing tomorrow morning. Thanx a mil. More to follow :)

[peter-toft-greve]

@latk This is a PURE homerun - thanx a mil!!
I will answer on StackOverflow and credit you (+reference the documentation)

For sake of completeness - I take it that this cannot be done prior to gcovr 4.2?

(and we can close this now)

[latk]

Thank you. Yes, the necessary features (JSON output, merging) were first released with gcovr 4.2.

[peter-toft-greve]

@latk One suggestion for further updates; that
gcovr --add-tracefile <wildcard_pattern>
e.g.
gcovr --add-tracefile run-*.json
is supported - to avoid to naming the *json files

With run-1,json and run-2.json as output (cf. https://gcovr.com/en/stable/guide.html#combining-tracefiles) it seems that with gcovr 4.2 I do have to use two --add-tracefile options.

[peter-toft-greve]

@latk as promised > I have updated https://stackoverflow.com/questions/58632496/ and credited you. THANX!!!