Update phpunit to the latest version for magento-coding-standard

[sivaschenko]

Update PHPUnit to the latest version for magento-coding-standard repository.

This will also require update or elimination of PHP_CodeSniffer\Tests\Standards\AbstractSniffUnitTest dependency.

[m2-assistant]

Hi @sivaschenko. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[sivaschenko]

@magento export issue to Jira project AC as Story

[korovitskyi]

@magento I am working on this

[ihor-sviziev]

FYI I tried to update to phpunit 8 or phpunit 9 - the unit tests of coding standard were failing with Fatal Errors due to missing void return type on setUp method on the https://github.com/squizlabs/PHP_CodeSniffer/blob/master/tests/Standards/AbstractSniffUnitTest.php#L55

[korovitskyi]

Hi, @ihor-sviziev , @sivaschenko .
I'm not sure that we can update PHPUnit version to 8 or 9(lastest).
As the dependency squizlabs/php_codesniffer:3.6 (lastest) support only PHPUnit:7.x as lastest.
And the whole magento-coding-standard depends on squizlabs/php_codesniffer' package.

Please, let me know if we have any variants here.
Thank you.

[ihor-sviziev]

@korovitskyi, as an option, we can ask if they're going to add such compatibility and/or send them a pull request? :)

[korovitskyi]

@ihor-sviziev , yes, looks like they are going to add, we can see at PHP_CodeSniffer V 4.0, but it is not released yet.

[m2-assistant]

Hi @andrewbess. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.