As I already mentioned in the #35 issue, I think it's more suitable to use a PHP build tool instead of a JS one. I don't tell that Grunt is not a powerful tool but it's a complicated installation process to be able to run tests.
Phing is required as a composer package and can be run directly after the composer install.
Examples:
```
vendor/bin/phing
vendor/bin/phing test
vendor/bin/phing clean
vendor/bin/phing phplint
vendor/bin/phing phpcs
vendor/bin/phing phpunit
vendor/bin/phing phpunit -Donly.units=true #The travis test process
```
The only difference here is the watch process. Phing doesn't have that kind of feature. It can be emulated with different tasks but require a lot more work. I think that PR is the first step, maybe we can go further if necessary.
Signed-off-by: Stéphane HULARD <s.hulard@chstudio.fr>
- allow maintained versions of PHPUnit 4 instead of the old 4.0 only
- add the code coverage configuration to cover only the library code and
not all tests and vendors as well
- move the configuration to phpunit.xml.dist to follow PHPUnit best
practices
Signed-off-by: Christophe Coevoet <stof@notk.org>
