Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Phar distribution #1

Closed
maks-rafalko opened this issue Jul 1, 2017 · 0 comments
Closed

Phar distribution #1

maks-rafalko opened this issue Jul 1, 2017 · 0 comments
Assignees
@maks-rafalko
Milestone
0.3

Comments

@maks-rafalko
Copy link
Member

As a developer, I want to have Infection Phar Distribution
And be able to self-update it
@maks-rafalko maks-rafalko added this to the v1.0.0 milestone Jul 1, 2017
@maks-rafalko maks-rafalko self-assigned this Jul 2, 2017
@maks-rafalko maks-rafalko modified the milestones: 0.3, v1.0.0 Jul 14, 2017
@3DFace 3DFace mentioned this issue Aug 29, 2017
Closed
@DeepDiver1975 DeepDiver1975 mentioned this issue Feb 20, 2021
Closed
maks-rafalko added a commit that referenced this issue Aug 7, 2021
@maks-rafalko
For Mutant's phpunit.xml, set executionOrder="default" to prevent r…
9fca23b 
…andom ordering of the tests since we need them to be sorted (fastest - first)

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.
maks-rafalko added a commit that referenced this issue Aug 7, 2021
@maks-rafalko
For Mutant's phpunit.xml, set executionOrder="default" to prevent r…
5c6b61f 
…andom ordering of the tests since we need them to be sorted (fastest - first) (#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.
maks-rafalko added a commit that referenced this issue Dec 7, 2021
@maks-rafalko
Exclude PSR/* namespace from prefixing due to the following error:
a3d99ea 
```
PHP Fatal error:  Uncaught TypeError: Composer\XdebugHandler\XdebugHandler::setLogger(): Argument #1 ($logger) must be of type Psr\Log\LoggerInterface, _HumbugBoxacfef8e3819a\Infection\Logger\ConsoleLogger given, called in phar:///home/maksrafalko/apps/infection/build/infection.phar/src/Console/XdebugHandler.php on line 15 and defined in /infection/vendor/composer/xdebug-handler/src/XdebugHandler.php:93
Stack trace:

```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maks-rafalko maks-rafalko

Labels
None yet
Projects
None yet
Milestone
0.3
Development

No branches or pull requests
1 participant
@maks-rafalko