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

4.0 | Drop support for PHPUnit < 7.5 #239

Merged
merged 6 commits into from
Jan 14, 2025

Conversation

jrfnl
Copy link
Collaborator

@jrfnl jrfnl commented Jan 14, 2025

Drop support for PHPUnit < 7.5 [1]

Adjust CI, README and composer.json for the drop of support for PHPUnit < 7.5.0.

The 7.5.0 version is a deliberate choice to allow for dropping all PHPUnit 7.x related polyfills.

Drop support for PHPUnit < 7.5 [2]

Remove the AssertIsType polyfill and all references to it.

Includes updating example code about using the polyfills in the README.

Drop support for PHPUnit < 7.5 [3]

Remove the AssertStringContains polyfill and all references to it.

Drop support for PHPUnit < 7.5 [4]

Remove the AssertEqualsSpecializations polyfill and all references to it.

Drop support for PHPUnit < 7.5 [5]

Remove in-code work-arounds which were in place to support PHPUnit < 7.5.0.

Drop support for PHPUnit < 7.5 [6]

Even though the TestListener implementation is not (yet) compatible with PHPUnit 10 (nor 11 or 12), we should still drop support for PHPUnit < 7.5 from the existing implementation.

This includes:

  • Dropping support for the PHPUnit 6 specific implementation of the TestListener.
  • Removing the semi-duplicate test fixture classes for PHPUnit < 7, as well as removing the test helper method containing the toggle for which fixture to use.
  • Updating the documentation in the README.

Adjust CI, README and `composer.json` for the drop of support for PHPUnit < 7.5.0.

The 7.5.0 version is a deliberate choice to allow for dropping all PHPUnit 7.x related polyfills.
@jrfnl jrfnl added this to the 4.0.0 milestone Jan 14, 2025
@jrfnl jrfnl requested a review from hellofromtonya January 14, 2025 15:56
@jrfnl
Copy link
Collaborator Author

jrfnl commented Jan 14, 2025

FYI: Coveralls will probably "block" the PR, but that will work itself out with the follow-up PRs/commits for the PHPUnit < 7.5 version drop.

Alternatively, if we want to be sure, I can pull the other PRs first and we could leave this one for last.

@coveralls
Copy link

coveralls commented Jan 14, 2025

Coverage Status

coverage: 98.445% (+0.8%) from 97.628%
when pulling 1dcba37 on feature/drop-support-for-phpunit-lt-7.5-1
into b4c70e2 on 4.x.

@hellofromtonya
Copy link
Collaborator

FYI: Coveralls will probably "block" the PR, but that will work itself out with the follow-up PRs/commits for the PHPUnit < 7.5 version drop.

Alternatively, if we want to be sure, I can pull the other PRs first and we could leave this one for last.

Hmm, might be better to pull the other PRs first to ensure the CI is passing before merge.

@jrfnl
Copy link
Collaborator Author

jrfnl commented Jan 14, 2025

FYI: Coveralls will probably "block" the PR, but that will work itself out with the follow-up PRs/commits for the PHPUnit < 7.5 version drop.
Alternatively, if we want to be sure, I can pull the other PRs first and we could leave this one for last.

Hmm, might be better to pull the other PRs first to ensure the CI is passing before merge.

Just checked - that won't work as the tests won't pass in that case as they would still be run against PHPUnit 6.x and I'd be removing things needed to get the tests to pass on PHPUnit 6.x.

Darn... update the PR to include all six commits ?

@hellofromtonya
Copy link
Collaborator

Just checked - that won't work as the tests won't pass in that case as they would still be run against PHPUnit 6.x and I'd be removing things needed to get the tests to pass on PHPUnit 6.x.

Darn... update the PR to include all six commits ?

I was thinking the same thing. Yes, one PR with all of the commits.

jrfnl added 4 commits January 14, 2025 17:29
Remove the `AssertIsType` polyfill and all references to it.

Includes updating example code about using the polyfills in the README.
Remove the `AssertStringContains` polyfill and all references to it.
Remove the `AssertEqualsSpecializations` polyfill and all references to it.
Remove in-code work-arounds which were in place to support PHPUnit < 7.5.0.
@jrfnl jrfnl changed the title Drop support for PHPUnit < 7.5 [1] Drop support for PHPUnit < 7.5 Jan 14, 2025
@jrfnl jrfnl changed the title Drop support for PHPUnit < 7.5 4.0 | Drop support for PHPUnit < 7.5 Jan 14, 2025
@jrfnl
Copy link
Collaborator Author

jrfnl commented Jan 14, 2025

I was thinking the same thing. Yes, one PR with all of the commits.

Done. Including updating the PR description to match.

@jrfnl
Copy link
Collaborator Author

jrfnl commented Jan 14, 2025

Not as big as I expected: image (which is a good thing for the reviewing)

Even though the TestListener implementation is not (yet) compatible with PHPUnit 10 (nor 11 or 12), we should still drop support for PHPUnit < 7.5 from the existing implementation.

This includes:
* Dropping support for the PHPUnit 6 specific implementation of the TestListener.
* Removing the semi-duplicate test fixture classes for PHPUnit < 7, as well as removing the test helper method containing the toggle for which fixture to use.
* Updating the documentation in the README.
@jrfnl jrfnl force-pushed the feature/drop-support-for-phpunit-lt-7.5-1 branch from 9c679ec to 1dcba37 Compare January 14, 2025 16:34
Copy link
Collaborator

@hellofromtonya hellofromtonya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Separately reviewed each individual commit. LGTM 👍
  • Reviewed as a whole. LGTM 👍

Combining all the commits into one PR worked well.

Ready for merge.

@hellofromtonya hellofromtonya merged commit d6cf070 into 4.x Jan 14, 2025
135 checks passed
@hellofromtonya hellofromtonya deleted the feature/drop-support-for-phpunit-lt-7.5-1 branch January 14, 2025 21:24
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.

3 participants