-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Ignore all .phpunit.result.cache files in the dev/tests directory #34361
Ignore all .phpunit.result.cache files in the dev/tests directory #34361
Conversation
Hi @hostep. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. 🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of Pull Requests 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 |
Hi @ihor-sviziev, thank you for the review.
|
No manual testing required |
@hostep, |
Hmm, then maybe we should add a more global |
@hostep I think it's great idea! |
… they get created by at least the static, unit and graphql functional tests).
5d25345
to
f884c5c
Compare
Okay, done! |
Hi @ihor-sviziev, thank you for the review. |
Just tested locally - everything works fine. ✔ QA passed Before❌On the 2.4-develop branch the output of
After✔ On the extra-phpunit-file-to-ignore (PR) branch the output of
Note: Locally I have the .env file, so it's not related to this PR. |
Hi @hostep, thank you for your contribution! |
Description (*)
When following the instructions for running the functional graphql tests, you'll notice that afterwards your git status is dirty. Because the file
dev/tests/api-functional/.phpunit.result.cache
gets generated by running those tests. So we should ignore that file in git.Related Pull Requests
Fixed Issues (if relevant)
None
Manual testing scenarios (*)
Note for the release notes writers
This doesn't deserve mentioning in the release notes, as it doesn't fix something that users of Magento run into.
Questions or comments
Contribution checklist (*)