Steve-Dee-Designs
/
woocommerce
mirror of https://github.com/woocommerce/woocommerce.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update readme to reflect test structure

This commit is contained in:
vedanshujain 2020-05-11 18:13:08 +05:30
parent a74f06f337
commit a42bb0681f
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tests/README.md
View File

@ -54,7 +54,7 @@ A text code coverage summary can be displayed using the `--coverage-text` option
### Writing Tests
* There are two different PHPUnit directories, `tests/legacy` and `tests/php`. The `tests/legacy` directory contains all of the tests for code in the `includes` directory, and the `tests/php` directory is a PSR-4 namespaced directory for tests of code in the `src` directory.
* There are two different PHPUnit directories, `tests/legacy` and `tests/php`. The `tests/legacy` directory contains all of the old tests for code in the `includes` directory, and the `tests/php` directory is where all new tests should go mapped 1:1 with original directories. For example a new test for `/includes/emails/class-wc-email.php` will go in `/tests/php/includes/emails/WCEmailTest.php`.
* Each test file should roughly correspond to an associated source file, e.g. the `formatting/functions.php` test file covers code in the `wc-formatting-functions.php` file
* Each test method should cover a single method or function with one or more assertions
* A single method or function can have multiple associated test methods if it's a large or complex method