From: "Guo, Gua" <gua.guo@intel.com>
To: devel@edk2.groups.io
Cc: Gua Guo <gua.guo@intel.com>
Subject: [PATCH 0/3] Add code coverage support for GCC
Date: Fri, 30 Sep 2022 09:53:45 +0800 [thread overview]
Message-ID: <cover.1664502701.git.gua.guo@intel.com> (raw)
From: Gua Guo <gua.guo@intel.com>
V1: Add coverage option for GCC
V2: Add ReadMe.md for how to generate coverage report
V3: Add VS2019 and GCC code coverage support
V4: Add VS2019 and GCC Azure CI/CD support
V5: Fix some typo and some flow issue
Gua Guo (3):
UnitTestFrameworkPkg: Add code coverage support for GCC
BaseTools/Plugin: Add coverage support for Unit Test
.azurepipelines: Install code coverage tool
.azurepipelines/Ubuntu-GCC5.yml | 5 +-
.azurepipelines/Windows-VS2019.yml | 5 +
.../templates/pr-gate-build-job.yml | 2 +
.azurepipelines/templates/pr-gate-steps.yml | 5 +
.../HostBasedUnitTestRunner.py | 119 ++++++++++++++++++
UnitTestFrameworkPkg/ReadMe.md | 37 +++++-
.../UnitTestFrameworkPkg.ci.yaml | 2 +
.../UnitTestFrameworkPkgHost.dsc.inc | 3 +-
pip-requirements.txt | 3 +
9 files changed, 176 insertions(+), 5 deletions(-)
--
2.31.1.windows.1
next reply other threads:[~2022-09-30 1:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 1:53 Guo, Gua [this message]
2022-09-30 1:53 ` [PATCH 1/3] UnitTestFrameworkPkg: Add code coverage support for GCC Guo, Gua
2022-12-21 3:41 ` Michael Kubacki
2022-12-21 3:53 ` Guo, Gua
2022-12-21 3:58 ` Michael Kubacki
2022-12-21 4:02 ` Guo, Gua
2022-09-30 1:53 ` [PATCH 2/3] BaseTools/Plugin: Add coverage support for Unit Test Guo, Gua
2022-12-21 3:42 ` [edk2-devel] " Michael Kubacki
2022-09-30 1:53 ` [PATCH 3/3] .azurepipelines: Install code coverage tool Guo, Gua
2022-12-21 3:42 ` [edk2-devel] " Michael Kubacki
2022-12-21 6:35 ` Guo, Gua
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=cover.1664502701.git.gua.guo@intel.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