mj/php-ovh
1
0
Fork 0
mirror of https://github.com/ovh/php-ovh.git synced 2023-11-05 03:20:26 +01:00
Code Issues Releases Wiki Activity
1b19b16def
php-ovh/.gitignore

8 lines
85 B
Plaintext
Raw Normal View History

Initial commit Signed-off-by: Vincent Cassé <vincent.casse@ovh.net>
2014-08-22 18:22:16 +02:00
node_modules
vendor
composer.lock
composer.phar
Improve the PHPUnit setup - 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>
2015-03-19 17:10:26 +01:00
/phpunit.xml
Use a PHP build tool, Phing instead of Grunt. 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>
2016-04-05 14:49:08 +02:00
/build.properties
/docs
Copy Permalink