Use PHPUnit 9.3+ schema when coverage tag exists #2
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
This modifies the coverage report and JUnit logger creation to make Infection fully compatible with the newer PHPUnit schema. More info: infection#1294
|
Let's go with you proposal. Thank you. |
sanmai
pushed a commit
that referenced
this pull request
Jan 3, 2021
* create mutators * avaible only string param * unit tests * cs-fix * mutatesNode rule * coallesce on mutators * regex only removes carret and dolar * code format * riddiculus pretty fix * Add mutators to schema.json, add more tests, add psalm annotations, add support for all possible delimiters * Add psalm issues to baseline because thecodingmachine/safe does not support psalm annotations yet thecodingmachine/safe#141 * Add test with an unpacked array * Simplify code by using ?? operator Co-authored-by: bernard.van.der.esch <bernard.van.der.esch@orba.co> Co-authored-by: Bernard van der Esch <b.vanderesch@gmail.com>
sanmai
pushed a commit
that referenced
this pull request
Sep 11, 2021
…andom ordering of the tests since we need them to be sorted (fastest - first) (infection#1547) When Infection build Mutant's `phpunit.xml` file, we add `<file>` tags, sorted by tests execution time, so that the fastest tests runs first. But when the original `phpunit.xml` contains `executionOrder="default"`, it was inherited to Mutant's `phpunit.xml` and broke the order, running the tests in a random order each time `infection` was executed. This also explains why I got different execution time of Infection for the project with *functional* tests. When Mutant is covered by 1000 functional tests, and tests are executed by random, it can be killed by the first test in run #1 and can be killed by 1000-th test in run #2, if the killing test is executed the last. With this update, all the tests will be executed in the same orders (fastest - first) in all the infection runs.
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 modifies the coverage report and JUnit logger creation to make Infection fully compatible with the newer PHPUnit schema.
More info: infection#1294