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.
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
Need some help to make it running #24
Comments
Can you run |
Sure, here it is:
|
I tried to run Infection for your project (https://github.com/3DFace/generic-storage, commit 3DFace/generic-storage@6ad7556) with disabled MySQL-related tests, and it works (I'm using MacOS, not Windows). Also, noticed that Could you please try to run infection on the same commit on windows and unix and post results here? |
@borNfreee Thank you for investigation! Just tried it on Unix and it seems to be working. I have tested both - HEAD and commit referenced by you. Result is the same - it works on Unix but not on Windows (errors from first message). Not sure if unix output matters... here it is:
|
To my shame, I found old (3.x) After removing it After downloading Should it work when |
yes, it should and it works. Please see the following code where vendor infection/src/Finder/TestFrameworkExecutableFinder.php Lines 52 to 70 in 47dca3d
If your composer global bin dir is already in E.g. I've added global composer bin dir to path on my machine: echo $PATH # outputs "...;/Users/user/.composer/vendor/bin;..." I'm closing this issue since there is no bug :) Please feel free to open a separate one about any issues with executable finder. |
Indeed it was again due to my weak environment. My Sorry for wasting your time and thank you for help! |
Unfortunately I can't make it works:
It seems like it's trying to read code coverage results but cant find them.
Dir
C:\Users\oz\AppData\Local\Temp\infection
contains only 3 files:There is no
./coverage-xml/
subdir.Here is my
infection.json
(generated):And
phpunit.xml
:Should I add/fix some parameters? Or should I run phpunit code coverage by myself with specific options?
The text was updated successfully, but these errors were encountered: