-
Notifications
You must be signed in to change notification settings - Fork 9.4k
gitignore for files and folders generated by Magento Functional Testing Framework (MFTF) #30107
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
base: 2.4-develop
Are you sure you want to change the base?
gitignore for files and folders generated by Magento Functional Testing Framework (MFTF) #30107
Conversation
Hi @lfluvisotto. 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 |
@ihor-sviziev if you could have a look at PR, I'd appreciate that, let me know if you have any comments or suggestions, thanks. |
e4b825f
to
cc110d6
Compare
Hi @ihor-sviziev, thank you for the review. |
@magento create issue |
I think the last two lines should be put in https://github.com/magento/magento2/blob/2.4-develop/dev/tests/acceptance/.gitignore instead of the There are a whole bunch of
Thoughts? Also: ignoring the entire |
@hostep oh, you’re right! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @lfluvisotto,
Could you update your PR according to following suggestion #30107 (comment) ?
cc110d6
to
cf43e37
Compare
@ihor-sviziev , @hostep , PR updated |
Looks good @ihor-sviziev: is it expected that running the MFTF tests creates a |
@hostep i do agree with you @okolesnyk @lbajsarowicz could you provide us some feedback, why the _generated folder is creating in the file reject root? Seems like that’s wrong behavior |
@ihor-sviziev You should be still happy, as some of the files are generated in |
@lbajsarowicz wow 🤦♂️ . Do we have a bug on it in the MFTF? |
@magento run all tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nevermind
Hi @orlangur, thank you for the review. |
@magento run Functional Tests B2B, WebAPI Tests |
@magento run Functional Tests B2B |
1 similar comment
@magento run Functional Tests B2B |
Hi @ihor-sviziev, this PR is open and approved since September 2020, isn't it gonna be merged? |
@magento run Database Compare, Functional Tests B2B, Functional Tests CE, Functional Tests EE, Integration Tests, Magento Health Index, Sample Data Tests B2B, Sample Data Tests CE, Sample Data Tests EE, Semantic Version Checker, Static Tests, Unit Tests , WebAPI Tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
@lfluvisotto so far, the only high priority (P0, P1 and P2) pull requests are currently getting processed 🙁 |
d30431b
to
a3e4f05
Compare
@magento run all tests |
…ng Framework (MFTF)
a3e4f05
to
5da8072
Compare
@magento run all tests |
Hello @lfluvisotto Thanks for the contributions! ✔️ QA Passed Install fresh Magento 2.4-develop Before: ✖️
After: ✔️
Builds are failed, hence moving it to Extended Testing. |
@magento run all tests |
@magento run all tests |
@magento run Unit Tests, Functional Tests CE |
The Functional CE test failures are different in recent 2 successive builds. They neither part of PR nor failing because of the PR changes, hence moving it to Merge in Progress. Run 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/30107/1e0ffd99ee07a604cdeb8594e2e2a75c/Functional/allure-report-ce/index.html#categories/8e2b61f028e5c19ee17f4a30e7a11231/e7f6001bd601f0e/ Run 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/30107/bae9cda4e82d9e6bf29028c27a73eb05/Functional/allure-report-ce/index.html#categories/6ca9d315ebd9ab54dbe1fb9148ebdc1f/35be6f0af80b7f16/ |
Description (*)
When we execute the commands related on https://devdocs.magento.com/mftf/docs/commands/mftf.html
Folders and files will be created during execution of MFTF commands.
In my opinion the changes on those folders and files should not be staged for commit.
Related Pull Requests
N/A
Fixed Issues (if relevant)
N/A
Manual testing scenarios (*)
Questions or comments
N/A
Contribution checklist (*)
Resolved issues: