From: "CrossedCarpet" <crossedcarpet@hotmail.com>
To: devel@edk2.groups.io
Subject: [edk2-devel] gTest code coverage
Date: Fri, 15 Sep 2023 09:48:22 -0700 [thread overview]
Message-ID: <ctXi.1694796502762209056.TZcO@groups.io> (raw)
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
Greetings,
Does gTest need any additional steps for building the code coverage files? Or is this not a possibility?
The documentation states "Host based Unit Tests will automatically enable coverage data." and indeed I used to find these coverage files when using the UnitTestFramework. Does this mean that the statement doesn't apply to gTests?
Thank you for your attention,
C.C.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108731): https://edk2.groups.io/g/devel/message/108731
Mute This Topic: https://groups.io/mt/101383490/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 1180 bytes --]
next reply other threads:[~2023-09-15 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 16:48 CrossedCarpet [this message]
2023-09-15 19:12 ` [edk2-devel] gTest code coverage Michael D Kinney
2023-09-19 16:44 ` CrossedCarpet
2023-09-19 18:09 ` Michael D Kinney
2023-09-19 22:42 ` Guo, Gua
2023-09-21 10:25 ` CrossedCarpet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ctXi.1694796502762209056.TZcO@groups.io \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox