From c6f723059c231c767f29ae3804973ee555461f90 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc=20W=C3=BCrth?= Date: Wed, 19 Mar 2014 17:30:10 +0100 Subject: [PATCH] testcases => test cases --- CONTRIBUTING.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ab748c188..8fdfd430c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,8 +2,8 @@ CakePHP loves to welcome your contributions. There are several ways to help out: * Create an [issue](https://github.com/cakephp/cakephp/issues) on GitHub, if you have found a bug -* Write testcases for open bug issues -* Write patches for open bug/feature issues, preferably with testcases included +* Write test cases for open bug issues +* Write patches for open bug/feature issues, preferably with test cases included * Contribute to the [documentation](https://github.com/cakephp/docs) There are a few guidelines that we need contributors to follow so that we have a @@ -30,7 +30,7 @@ chance of keeping on top of things. * Make commits of logical units. * Check for unnecessary whitespace with `git diff --check` before committing. * Use descriptive commit messages and reference the #issue number. -* Core testcases should continue to pass. You can run tests locally or enable +* Core test cases should continue to pass. You can run tests locally or enable [travis-ci](https://travis-ci.org/) for your fork, so all tests and codesniffs will be executed. * Your work should apply the CakePHP coding standards. @@ -48,10 +48,10 @@ chance of keeping on top of things. * Submit a pull request to the repository in the cakephp organization, with the correct target branch. -## Testcases and codesniffer +## Test cases and codesniffer CakePHP tests requires [PHPUnit](http://www.phpunit.de/manual/current/en/installation.html) -3.5 or higher. To run the testcases locally use the following command: +3.5 or higher. To run the test cases locally use the following command: ./lib/Cake/Console/cake test core AllTests --stderr