Skip to content

[FEATURE] Add Composer scripts to run unit tests #488

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 22, 2024
Merged

[FEATURE] Add Composer scripts to run unit tests #488

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 14 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -633,5 +633,17 @@ class Sabberworm\CSS\CSSList\Document#4 (2) {

## Misc

* Legacy Support: The latest pre-PSR-0 version of this project can be checked with the `0.9.0` tag.
* Running Tests: To run all unit tests for this project, run `composer install` to install phpunit and use `./vendor/bin/phpunit`.
### Legacy Support

The latest pre-PSR-0 version of this project can be checked with the `0.9.0` tag.

### Running Tests

To run all continuous integration (CI) checks for this project (including unit tests),
* run `composer install` to install the development dependencies managed with Composer;
* run `phive install` to install the development dependencies managed with PHIVE;
* [Installation of PHIVE](https://github.com/phar-io/phive?tab=readme-ov-file#getting-phive)
* run `composer ci` to run all static and dynamic CI checks.

Details of other Composer scripts available (e.g. to run one specific CI check) are provided with `composer list`.