|Classes of Renato De Oliveira Lucena||>||PHP Pokemon Script||>||vendor/mockery/mockery/CONTRIBUTING.md||>||Download|
We'd love you to help out with mockery and no contribution is too small.
Issues can be reported on the issue tracker. Please try and report any bugs with a minimal reproducible example, it will make things easier for other contributors and your problems will hopefully be resolved quickly.
We're always interested to hear about your ideas and you can request features by creating a ticket in the issue tracker. We can't always guarantee someone will jump on it straight away, but putting it out there to see if anyone else is interested is a good idea.
Likewise, if a feature you would like is already listed in the issue tracker, add a :+1: so that other contributors know it's a feature that would help others.
Contributing code and documentation
If you have a big change or would like to discuss something, create an issue in the issue tracker or jump in to \#mockery on freenode
Any code you contribute must be licensed under the BSD 3-Clause License.
Mockery may have several active branches at any one time and roughly follows a Git Branching Model. Generally, if you're developing a new feature, you want to be targeting the master branch, if it's a bug fix, you want to be targeting a release branch, e.g. 0.8.
To run the unit tests for Mockery, clone the git repository, download Composer using
the instructions at http://getcomposer.org/download/,
then install the dependencies with
This will install the required PHPUnit and Hamcrest dev dependencies and create the
autoload files required by the unit tests. You may run the
Mockery and it's code generation can be difficult to debug. A good start is to