feat: add explicit check against codeCoverage.expectFrontendCoverageOnly before attempting to collect backend coverage #555
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
…nly before attempting to collect backend coverage
|
|
VeronikaBe
approved these changes
Sep 17, 2024
|
This change would be very helpful for collecting only frontend coverage during e2e testing. Could someone with write access review this PR and retrigger the checks as the results are outdated by now? |
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.
This is an updated PR taken from @funkadelic #474 updated to try to make the tests pass and make it easier for the plugin team to istruct us on how to proceed.
As @funkadelic mentioned on his PR this PR aims at solving #473