Reactivating coverage #125
Open
Conversation
This file contains hidden or 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
thirsch
commented
Feb 22, 2024
Collaborator
thirsch
force-pushed
the
feature/reactivate-coverage
branch
from
d81b53a to
21dbad3
Compare
connorhu
approved these changes
Feb 29, 2024
thirsch
force-pushed
the
feature/reactivate-coverage
branch
from
d021dc8 to
21dbad3
Compare
thirsch
force-pushed
the
feature/reactivate-coverage
branch
from
21dbad3 to
0154cf9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 three steps are the minimum to get coverage working again. It can be used by invoking
php run.php --coverageand will write the results in tests/coverage/*