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
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -152,9 +152,8 @@ To help you with this, a number of convenience scripts are available:
152
152
*`composer cs` will check for code style violations.
153
153
*`composer cbf` will run the autofixers for code style violations.
154
154
*`composer test` will run the unit tests.
155
-
*`composer coverage` will run the unit tests with code coverage.
156
-
Note: you may want to use a custom `phpunit.xml` overload config file to tell PHPUnit where to place an HTML report.
157
-
Alternative run it like so: `composer coverage -- --coverage-html /path/to/report-dir/` to specify the location for the HTML report on the command line.
155
+
*`composer coverage` will run the unit tests with code coverage and show a text summary.
156
+
*`composer coverage-local` will run the unit tests with code coverage and generate an HTML coverage report, which will be placed in a `build/coverage-html` subdirectory.
158
157
*`composer build` will build the phpcs.phar and phpcbf.phar files.
159
158
160
159
N.B.: You can ignore any skipped tests as these are for external tools.
0 commit comments