Skip to content
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.

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

GH Actions: run tests against PHPUnit PHAR files as well #160

Merged
merged 1 commit into from
Apr 5, 2024

Conversation

jrfnl
Copy link
Collaborator

@jrfnl jrfnl commented Apr 5, 2024

PHPUnit 8.5.38 and 9.6.19 contain a change in the PHAR build process, which means that classes external to PHPUnit are now prefixed differently, which breaks one polyfill.

As things were, such issues would previously not be caught by CI.

This commit adds a new job to the test workflow, which will run the tests against a range of PHP-PHPUnit combinations using the PHPUnit Phar to ensure any such issues will be automatically caught in the future.

The new test workflow will (very) selectively also upload code coverage to safeguard that the PHAR-file specific lines in the code base remain covered by tests as well.

@jrfnl jrfnl added this to the 1.1.1 milestone Apr 5, 2024
@jrfnl
Copy link
Collaborator Author

jrfnl commented Apr 5, 2024

See #161 for context about the specific change which was problematic in these latest PHPUnit releases.

@coveralls
Copy link

coveralls commented Apr 5, 2024

Coverage Status

coverage: 96.264% (+0.4%) from 95.833%
when pulling 7395997 on feature/ghactions-add-phar-testing-job
into 51c2415 on 1.x.

@jrfnl jrfnl force-pushed the feature/ghactions-add-phar-testing-job branch 4 times, most recently from 1c48475 to 1345998 Compare April 5, 2024 14:30
PHPUnit 8.5.38 and 9.6.19 contain a change in the PHAR build process, which means that classes external to PHPUnit are now prefixed differently, which breaks one polyfill.

As things were, such issues would previously not be caught by CI.

This commit adds a new job to the test workflow, which will run the tests against a range of PHP-PHPUnit combinations using the PHPUnit Phar to ensure any such issues will be automatically caught in the future.

The new test workflow will (very) selectively also upload code coverage to safeguard that the PHAR-file specific lines in the code base remain covered by tests as well.
@jrfnl jrfnl force-pushed the feature/ghactions-add-phar-testing-job branch from 1345998 to 7395997 Compare April 5, 2024 14:40
@jrfnl jrfnl merged commit 9c03fd0 into 1.x Apr 5, 2024
154 checks passed
@jrfnl jrfnl deleted the feature/ghactions-add-phar-testing-job branch April 5, 2024 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants