Instead of the current mechanism left over from using SimpleTest, I would suggest creating a config phpunit.xml.dist file to use with PHPUnit. An example of how this would work can be found in this commit.
If the need for using a constant to define the TESTDIR can be removed the bootstrap entry in the XML could be pointed directly to the vendor autoloader without negating this to the bootstrap.
One of the benefits would be that simply running phpunit would be enought to run all the tests, no separate bootstrap per repo needed.
In the example I've also taken the liberty of adding some suggestions of output to log to stdout to be easily available in the build (or when running the tests locally). I will follow up on this in a later pull-request.
As a side-note: Good work on the contributing.md nice to see that little link in the PR-UI on github :smile:
poef
commented
8 years ago
Instead of the current mechanism left over from using SimpleTest, I would suggest creating a config
phpunit.xml.distfile to use with PHPUnit. An example of how this would work can be found in this commit.If the need for using a constant to define the
TESTDIRcan be removed thebootstrapentry in the XML could be pointed directly to the vendor autoloader without negating this to the bootstrap.One of the benefits would be that simply running
phpunitwould be enought to run all the tests, no separate bootstrap per repo needed.In the example I've also taken the liberty of adding some suggestions of output to log to stdout to be easily available in the build (or when running the tests locally). I will follow up on this in a later pull-request.
As a side-note: Good work on the
contributing.mdnice to see that little link in the PR-UI on github :smile: