Skip to content

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

Open
wants to merge 3 commits into
base: 2.4-develop
Choose a base branch
from

Conversation

lfluvisotto
Copy link
Contributor

@lfluvisotto lfluvisotto commented Sep 18, 2020

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.

image

Related Pull Requests

N/A

Fixed Issues (if relevant)

N/A

Manual testing scenarios (*)

  1. vendor/bin/mftf build:project
  2. vendor/bin/mftf generate:tests

Questions or comments

N/A

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

Resolved issues:

  1. resolves [Issue] gitignore for files and folders generated by Magento Functional Testing Framework (MFTF) #30135: gitignore for files and folders generated by Magento Functional Testing Framework (MFTF)

@m2-assistant
Copy link

m2-assistant bot commented Sep 18, 2020

Hi @lfluvisotto. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

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.

⚠️ According to the Magento Contribution requirements, all Pull Requests 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 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

@lfluvisotto
Copy link
Contributor Author

@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.

@lfluvisotto lfluvisotto force-pushed the 2.4-develop-gitignore-mftf branch from e4b825f to cc110d6 Compare September 18, 2020 14:56
@ihor-sviziev ihor-sviziev added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Sep 18, 2020
@ghost ghost assigned ihor-sviziev Sep 18, 2020
@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-8233 has been created to process this Pull Request

@sidolov sidolov added Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. labels Sep 21, 2020
@sidolov
Copy link
Contributor

sidolov commented Sep 21, 2020

@magento create issue

@hostep
Copy link
Contributor

hostep commented Sep 22, 2020

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 .gitignore file of the entire project.

There are a whole bunch of .gitignore files in the dev subdirectory for that purpose:

dev/tests/unit/.gitignore
dev/tests/unit/tmp/.gitignore
dev/tests/integration/.gitignore
dev/tests/integration/tmp/.gitignore
dev/tests/acceptance/.gitignore
dev/tests/static/testsuite/Magento/Test/_files/.gitignore
dev/tests/static/.gitignore
dev/tests/static/tmp/.gitignore
dev/tests/api-functional/.gitignore
dev/tests/setup-integration/.gitignore
...

Thoughts?

Also: ignoring the entire dev/tests/acceptance/tests/ directory feels very incorrect, since there are many files already in git from that directory, @lfluvisotto what specific files are being marked in git exactly?

@ihor-sviziev
Copy link
Contributor

@hostep oh, you’re right!

Copy link
Contributor

@ihor-sviziev ihor-sviziev left a 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) ?

@lfluvisotto
Copy link
Contributor Author

@ihor-sviziev , @hostep , PR updated

@hostep
Copy link
Contributor

hostep commented Sep 23, 2020

Looks good

@ihor-sviziev: is it expected that running the MFTF tests creates a _generated directory in the root of the Magento project? This feels incorrect to me, but I might be wrong ...

@ihor-sviziev
Copy link
Contributor

@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

@lbajsarowicz
Copy link
Contributor

lbajsarowicz commented Sep 23, 2020

@ihor-sviziev You should be still happy, as some of the files are generated in vendor/... directory 🤣
Change vendor/ directory to Read Only, execute MFTF tests and watch them fail.

@ihor-sviziev
Copy link
Contributor

ihor-sviziev commented Sep 24, 2020

@lbajsarowicz wow 🤦‍♂️ . Do we have a bug on it in the MFTF?

@lbajsarowicz
Copy link
Contributor

@ihor-sviziev magento/magento2-functional-testing-framework#699

@ihor-sviziev
Copy link
Contributor

@magento run all tests

Copy link
Contributor

@orlangur orlangur left a comment

Choose a reason for hiding this comment

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

Nevermind

@orlangur orlangur assigned ihor-sviziev and unassigned orlangur Oct 8, 2020
@magento-engcom-team
Copy link
Contributor

Hi @orlangur, thank you for the review.
ENGCOM-8233 has been created to process this Pull Request

@orlangur orlangur requested review from orlangur and removed request for orlangur October 8, 2020 12:35
@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B, WebAPI Tests

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B

1 similar comment
@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B

@ihor-sviziev ihor-sviziev added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Oct 7, 2021
@lfluvisotto
Copy link
Contributor Author

Hi @ihor-sviziev, this PR is open and approved since September 2020, isn't it gonna be merged?

@lfluvisotto
Copy link
Contributor Author

@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

@magento-automated-testing
Copy link

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.

@ihor-sviziev
Copy link
Contributor

@lfluvisotto so far, the only high priority (P0, P1 and P2) pull requests are currently getting processed 🙁

@lfluvisotto lfluvisotto force-pushed the 2.4-develop-gitignore-mftf branch from d30431b to a3e4f05 Compare August 19, 2024 01:35
@lfluvisotto
Copy link
Contributor Author

@magento run all tests

@lfluvisotto lfluvisotto force-pushed the 2.4-develop-gitignore-mftf branch from a3e4f05 to 5da8072 Compare August 19, 2024 20:01
@lfluvisotto
Copy link
Contributor Author

@magento run all tests

@lfluvisotto
Copy link
Contributor Author

@engcom-Delta

@engcom-Dash
Copy link
Contributor

engcom-Dash commented Oct 21, 2024

Hello @lfluvisotto

Thanks for the contributions!

✔️ QA Passed
Preconditions:

Install fresh Magento 2.4-develop
Steps to reproduce
According to the issue description.

Before: ✖️

  • _generated folder is visible in git status.

After: ✔️

  • _generated folder is not visible in git status.

Builds are failed, hence moving it to Extended Testing.

@engcom-Dash
Copy link
Contributor

@magento run all tests

@engcom-Dash
Copy link
Contributor

@magento run all tests

@engcom-Dash
Copy link
Contributor

@magento run Unit Tests, Functional Tests CE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: ready for testing Release Line: 2.4 Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
Status: Merge in Progress
Development

Successfully merging this pull request may close these issues.

[Issue] gitignore for files and folders generated by Magento Functional Testing Framework (MFTF)
8 participants