It's possible for a PHP project to be within a subdirectory of another project. This is especially true for frameworks like Symfony3 which use the concept of bundles.
Currently, the package expects a phpunit.xml to be in the root of a main project(s). Maybe a configuration option for a glob style path to search for these configurations would be a better idea.
There are a few issues though.
The vendors directory will contain many configs. They should be excluded by default, but some mechanism of running those tests should be available.
If tests within the vendors directory are enabled, it should be done so in a read only mode to avoid composer update complaining about dirty repositories.
The Adapter will likely have problems with multiple src and tests directories.
Not sure about the performance impact of watching the whole directory tree for changes.
If each phpunit.xml is treated as its own Project, how will nested projects behave?
It's possible for a PHP project to be within a subdirectory of another project. This is especially true for frameworks like Symfony3 which use the concept of bundles.
Currently, the package expects a
phpunit.xmlto be in the root of a main project(s). Maybe a configuration option for a glob style path to search for these configurations would be a better idea.There are a few issues though.
composer updatecomplaining about dirty repositories.Adapterwill likely have problems with multiple src and tests directories.Project, how will nested projects behave?