Documentation
Testing
Validate package changes with Pest and JavaScript tests before merging updates.
On this page
Package changes are safest when you validate both the PHP and browser runtime behavior in the same branch.
PHP test suite
Run the Pest suite from the repository root:
composer test
Use coverage when you are working on package internals or parser behavior.
composer test-coverage
JavaScript test suite
The frontend rules and adapters live in resources/js, so use the JavaScript suite when you change the browser runtime.
npm test
Documentation changes
If you change Markdown pages, the docs template, or shared docs assets, follow the separate documentation workflow so the generated site stays in sync.
Recommended contributor loop
- Update the package code or the relevant documentation.
- Run the narrowest tests that can falsify the change.
- Run any affected browser checks when a rule or adapter changes.
- Inspect the changed behavior before opening a pull request.
Practical verification examples
Rule or parser change
composer test
npm test