From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"crossedcarpet@hotmail.com" <crossedcarpet@hotmail.com>,
"Guo, Gua" <gua.guo@intel.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] gTest code coverage
Date: Fri, 15 Sep 2023 19:12:37 +0000 [thread overview]
Message-ID: <CO1PR11MB49298B4D31575EA5A6BCD787D2F6A@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <ctXi.1694796502762209056.TZcO@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
This describes local development code coverage. Let us know if these work for you.
https://github.com/tianocore/edk2/tree/master/UnitTestFrameworkPkg#code-coverage
Thanks,
Mike
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of CrossedCarpet
Sent: Friday, September 15, 2023 9:48 AM
To: devel@edk2.groups.io
Subject: [edk2-devel] gTest code coverage
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 (#108732): https://edk2.groups.io/g/devel/message/108732
Mute This Topic: https://groups.io/mt/101383490/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 4082 bytes --]
next prev parent reply other threads:[~2023-09-15 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 16:48 [edk2-devel] gTest code coverage CrossedCarpet
2023-09-15 19:12 ` Michael D Kinney [this message]
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=CO1PR11MB49298B4D31575EA5A6BCD787D2F6A@CO1PR11MB4929.namprd11.prod.outlook.com \
--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