-
Notifications
You must be signed in to change notification settings - Fork 36
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
PHPUnit 10 Shift #72
PHPUnit 10 Shift #72
Conversation
From the [PHPUnit 8 release notes][1], the `TestCase` methods below now declare a `void` return type: - `setUpBeforeClass()` - `setUp()` - `assertPreConditions()` - `assertPostConditions()` - `tearDown()` - `tearDownAfterClass()` - `onNotSuccessfulTest()` [1]: https://phpunit.de/announcements/phpunit-8.html
|
|
❌ The Shift detected calls to
|
ℹ️ PHPUnit has documented using return types for test cases and data providers since PHPUnit 8. In an effort to modernize your test suite, Shift added a return type of Shift understands developers have different preferences when it comes to type hints. If you do not wish to add return types, you may undo this change by running: |
ℹ️ PHPUnit has documented declaring test classes as Shift understands developers have different preferences when it comes to using |
|
⚗️ This Shift is still being refined. Please report any issues or suggestions to shift@laravelshift.com. Your feedback is what helps improve the experience for everyone. |
This pull request contains changes for upgrading to PHPUnit 10 automated by the PHPUnit 10 Shift.
Before merging, you need to:
shift-111318
branchcomposer update
(if the scripts fail, add--no-scripts
)vendor/bin/phpunit
If there were changes you felt could have been automated, please reply to the follow-up email with your feedback or on Twitter.