You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,11 +34,13 @@ This package contains Composer scripts to quickly run the developer checks which
34
34
35
35
After `composer install`, you can do:
36
36
37
-
-`composer test`: **Run all checks and tests** - this should pass cleanly before you submit a pull request.
38
-
-`composer lint`: Just run PHP and XML linters.
39
-
-`composer phpcs`: Just run PHPCS against this package.
40
-
-`composer phpunit`: Just run the unit tests.
41
-
-`composer ruleset`: Just run the ruleset tests.
37
+
-`composer lint`: Lint PHP and XML files in against parse errors.
38
+
-`composer cs`: Check the code style and code quality of the codebase via PHPCS.
39
+
-`composer test`: Run the unit tests for the VIPCS sniffs.
40
+
-`composer test-coverage`: Run the unit tests for the VIPCS sniffs with coverage enabled.
41
+
-`composer test-ruleset`: Run the ruleset tests for the VIPCS sniffs.
42
+
-`composer feature-completeness`: Check if all the VIPCS sniffs have tests.
43
+
-`composer check`: Run all checks (lint, CS, feature completeness) and tests - this should pass cleanly before you submit a pull request.
42
44
43
45
## Branches
44
46
@@ -190,7 +192,7 @@ The ruleset tests, previously named here as _integration tests_, are our way of
190
192
191
193
An example where it might not would be when a ruleset references a local sniff or a sniff from upstream (WPCS or PHPCS), but that the violation code, sniff name or category name has changed. Without a ruleset test, this would go unnoticed.
192
194
193
-
The `composer test` or `composer ruleset` commands run the `ruleset-test.php` files (one for each standard), which internally run `phpcs` against the "dirty" test files (`ruleset-test.inc`), and looks out for a known number of errors, warnings, and messages on each line. This is then compared against the expected errors, warnings and messages to see if there are any missing or unexpected violations or difference in messages.
195
+
The `composer check` or `composer test-ruleset` commands run the `ruleset-test.php` files (one for each standard), which internally run `phpcs` against the "dirty" test files (`ruleset-test.inc`), and looks out for a known number of errors, warnings, and messages on each line. This is then compared against the expected errors, warnings and messages to see if there are any missing or unexpected violations or difference in messages.
194
196
195
197
When adding or changing a sniff, the ruleset test files should be updated to match.
0 commit comments