-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GoogleTest - ConfigKnobShimLib using basecore PPI mock #200
Conversation
...Library/ConfigKnobShimLib/ConfigKnobShimDxeLib/GoogleTest/ConfigKnobShimDxeLibGoogleTest.cpp
Outdated
Show resolved
Hide resolved
using namespace testing; | ||
|
||
/////////////////////////////////////////////////////////////////////////////// | ||
class GetConfigKnobOverrideFromVariableStorageTest : public Test { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming this works, I would remove the cmocka unit tests in this same PR, no need to keep both.
...Library/ConfigKnobShimLib/ConfigKnobShimDxeLib/GoogleTest/ConfigKnobShimDxeLibGoogleTest.cpp
Outdated
Show resolved
Hide resolved
...Library/ConfigKnobShimLib/ConfigKnobShimDxeLib/GoogleTest/ConfigKnobShimDxeLibGoogleTest.inf
Outdated
Show resolved
Hide resolved
Codecov Report
@@ Coverage Diff @@
## main #200 +/- ##
=======================================
Coverage 27.58% 27.58%
=======================================
Files 16 16
Lines 4520 4520
=======================================
Hits 1247 1247
Misses 3273 3273
Flags with carried forward coverage won't be shown. Click here to find out more. |
9efa0ff
to
5d16181
Compare
…vianNK/mu_feature_config into vnowkakeane/gtest_demo_cherry
2dfb55f
to
71d1ca0
Compare
## Description Original PR: microsoft#200 Google Tests for ConfigKnobShimDxeLib and ConfigKnobShimPeiLib ConfigKnobShimPeiLib is consuming the PPI mock from mu_basecore (microsoft/mu_basecore#579), so merging this is pending the mu_basecore PR being merged. Pipelines will fail in the meantime. - [ ] Impacts functionality? - **Functionality** - Does the change ultimately impact how firmware functions? - Examples: Add a new library, publish a new PPI, update an algorithm, ... - [ ] Impacts security? - **Security** - Does the change have a direct security impact on an application, flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter validation improvement, ... - [ ] Breaking change? - **Breaking change** - Will anyone consuming this change experience a break in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call a function in a new library class in a pre-existing module, ... - [x ] Includes tests? - **Tests** - Does the change include any explicit test code? - Examples: Unit tests, integration tests, robot tests, ... - [ ] Includes documentation? - **Documentation** - Does the change contain explicit documentation additions outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation on an a separate Web page, ... ## How This Was Tested Ran the tests using stuart_ci_build. ## Integration Instructions N/A
Preface
Please ensure you have read the contribution docs prior
to submitting the pull request. In particular,
pull request guidelines.
Description
Implementing GoogleTest for ConfigKnobShimLib, consuming the PPI mock from mu_basecore (microsoft/mu_basecore#579).
For each item, place an "x" in between
[
and]
if true. Example:[x]
.(you can also check items in the GitHub UI)
flow, or firmware?
validation improvement, ...
in build or boot behavior?
a function in a new library class in a pre-existing module, ...
outside direct code modifications (and comments)?
on an a separate Web page, ...
How This Was Tested
<Please describe the test(s) that were run to verify the changes.>
Integration Instructions
<Describe how these changes should be integrated. Use N/A if nothing is required.>
Add just the tests included in the demo