Add support for Pest test framework #1516
Merged
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
maks-rafalko
force-pushed
the
feature/pest-adapter
branch
from
f215a8c
to
16694e2
Compare
maks-rafalko
force-pushed
the
feature/pest-adapter
branch
from
16694e2
to
e64900c
Compare
|
rebased on master - removed code coverage ignorer from Pest adapter as well |
|
added docs, ready for review |
|
@maks-rafalko All ready in our side. Thank your help on this! |
|
let's get it merged, going to release tonight |
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 PR:
Pesttest framework support site#217What is Pest?
This is a test framework built on top of PHPUnit and very similar to Jest from JS ecosystem. It's getting more and more popular, espesially in Laravel ecosystem.
Why is it on
infection/infectionpackage instead of in a separateinfection/pest-test-framework-adapter?Because recently we decided to leave PHPUnit inside the core. And since Pest is really just a wrapper around PHPUnit, even in the code it is just a decorator around
PhpUnitAdapter.phpclass. So it does make sense to store it here to not copy paste and maintain the same code in a different package.Misc
Pest maintainers helped us to add support of JUnit report for Pest: pestphp/pest#291, so it works as quick as PHPUnit adapter - with running only those tests that cover mutation.
I'm going to write some docs here at Infection and for Pest, and we are good to go with
0.23.0release.