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
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -399,6 +399,8 @@ To run the tests specific to the use of `PHP_CODESNIFFER_CBF === true`:
399
399
400
400
### Writing End-to-End Tests
401
401
402
+
#### Bashunit
403
+
402
404
Bash-based end-to-end tests can be written using the [Bashunit](https://bashunit.typeddevs.com/) test tooling using version 0.26.0 or higher.
403
405
404
406
To install bashunit, follow the [installation guide](https://bashunit.typeddevs.com/installation).
@@ -413,6 +415,20 @@ You can then run the bashunit tests on Linux/Mac/WSL, like so:
413
415
When writing end-to-end tests, please use fixtures for the "files under scan" to make the tests stable.
414
416
These fixtures can be placed in the `tests/EndToEnd/Fixtures` subdirectory.
415
417
418
+
#### phpt
419
+
420
+
PHP-based end-to-end tests can be written using the `phpt` format. This is the format that PHP uses for its own tests. We use PHPUnit to run these tests.
421
+
422
+
```bash
423
+
vendor/bin/phpunit -c phpunit-e2e.xml.dist
424
+
```
425
+
426
+
The following resources may be helpful when writing `phpt`-style tests:
0 commit comments