Update code coverage config #403
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vexx32
added
PR-Needs-Review 🔍
vexx32
force-pushed
the
Test/CodeCoverage
branch
from
38d7b48
to
caccbf1
Compare
vexx32
force-pushed
the
Test/CodeCoverage
branch
from
caccbf1
to
6374cfc
Compare
Manually cast nested configuration options to their respective concrete types
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Attempt to manually configure tests for Pester v5 and add code coverage that should (hopefully) work correctly.
Context
The automatic test coverage generation that
-CIenables is not reading in our function files since we don't store function files alongside test files. Hopefully a more specific manual configuration should do the trick.Changes
-CIswitch with manually configured-Configurationsettings.Checklist