Contributing to PHPUnit
Contributor Code of Conduct
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
- Fork the project.
- Make your bug fix or feature addition.
- Add tests for it. This is important so we don't break it in a future version unintentionally.
- Send a pull request. Bonus points for topic branches.
Please make sure that you have set up your user name and email address for use with Git. Strings such as
silly nick name <root@localhost> look really stupid in the commit history of a project.
Pull requests for bug fixes must be based on the current stable branch whereas pull requests for new features must be based on the
We are trying to keep backwards compatibility breaks in PHPUnit to an absolute minimum. Please take this into account when proposing changes.
Due to time constraints, we are not always able to respond as quickly as we would like. Please do not take delays personal and feel free to remind us if you feel that we forgot to respond.
This project comes with a configuration file and an executable for php-cs-fixer (
.php_cs) that you can use to (re)format your source code for compliance with this project's coding guidelines:
$ ./build/tools/php-cs-fixer fix
Using PHPUnit from a Git checkout
The following commands can be used to perform the initial checkout of PHPUnit:
$ git clone git://github.com/sebastianbergmann/phpunit.git $ cd phpunit
Retrieve PHPUnit's dependencies using Composer:
$ composer install
phpunit script can be used to invoke the PHPUnit test runner:
$ ./phpunit --version
Running PHPUnit's own test suite
After following the steps shown above, PHPUnit's own test suite is run like this:
Please use the most specific issue tracker to search for existing tickets and to open new tickets: