You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My team has implemented a binary that wraps around PHPUnit and configures / executes tests for us when we simply point it at a particular directory. I want to implement an Infection Test Framework extension that we would only use internally that executes tests via our binary. Since our binary dynamically creates a PHPUnit configuration file, there is no existing configuration file to point Infection to. However, when I try to run Infection I get the following error because it requires a configuration file exist:
In FileOrDirectoryNotFound.php line 71:
The path "/home/nthompson/development/MyApp/modules/ExampleModule" does not contain any of the requested files: "PhpUnitTestRunner.xml", "PhpUnitTestRunner.yml", "PhpUnitTestRunner.xml.dist", "PhpUnitTe
stRunner.yml.dist", "PhpUnitTestRunner.dist.xml", "PhpUnitTestRunner.dist.yml"
Workaround
If I create a fake, empty configuration file by running the following command then Infection works as expected:
touch modules/ExampleModule/PhpUnitTestRunner.yml
Ideal Solution
I would much prefer to be able to simply turn off the check for a pre-existing configuration file.
Description
My team has implemented a binary that wraps around PHPUnit and configures / executes tests for us when we simply point it at a particular directory. I want to implement an Infection Test Framework extension that we would only use internally that executes tests via our binary. Since our binary dynamically creates a PHPUnit configuration file, there is no existing configuration file to point Infection to. However, when I try to run Infection I get the following error because it requires a configuration file exist:
Workaround
If I create a fake, empty configuration file by running the following command then Infection works as expected:
Ideal Solution
I would much prefer to be able to simply turn off the check for a pre-existing configuration file.
Related Context
I also submitted the bug Infection can't run custom Test Framework extensions because TestFrameworkTypes is hardcoded related to other issues I encountered while setting up my Test Framework extension. Whereas that bug will affect anyone trying to create a Test Framework extension, I realize this feature request may be more niche to my use case.
The text was updated successfully, but these errors were encountered: