Skip to content

[MFTF] add new AdminOpenCatalogProductPageActionGroup #29931

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

Conversation

Usik2203
Copy link
Contributor

@Usik2203 Usik2203 commented Sep 7, 2020

This PR introduce AdminOpenCatalogProductPageActionGroup and makes GoToProductCatalogPageActionGroup deprecated due to wrong naming

Related Pull Requests

https://github.com/magento/partners-magento2ee/pull/329

Resolved issues:

  1. resolves [Issue] [MFTF] add new AdminOpenCatalogProductPageActionGroup #29941: [MFTF] add new AdminOpenCatalogProductPageActionGroup

@m2-assistant
Copy link

m2-assistant bot commented Sep 7, 2020

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

@Usik2203
Copy link
Contributor Author

Usik2203 commented Sep 7, 2020

@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B

@rogyar rogyar self-assigned this Sep 7, 2020
xsi:noNamespaceSchemaLocation="urn:magento:mftf:Test/etc/actionGroupSchema.xsd">
<actionGroup name="AdminOpenCatalogProductPageActionGroup">
<annotations>
<description>Open catalog product page.</description>
Copy link
Contributor

@rogyar rogyar Sep 7, 2020

Choose a reason for hiding this comment

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

At first glance, I was confused with the definition "catalog product page in admin panel". After a couple of seconds, I've realized that we are talking about a page with the product grid.
We may leave the name of the action group as it is. But I would suggest editing the description and have something like

Open page with product grid

Or something like that.

What do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@Usik2203
Copy link
Contributor Author

Usik2203 commented Sep 7, 2020

@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B

@Usik2203 Usik2203 force-pushed the add-AdminOpenProductCatalogPageActionGroup branch from 697e7cf to 832bb01 Compare September 8, 2020 07:28
@Usik2203
Copy link
Contributor Author

Usik2203 commented Sep 8, 2020

@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B

@sidolov sidolov added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Sep 8, 2020
@sidolov
Copy link
Contributor

sidolov commented Sep 8, 2020

@magento create issue

@Usik2203
Copy link
Contributor Author

Usik2203 commented Sep 9, 2020

@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B

@Usik2203
Copy link
Contributor Author

Usik2203 commented Sep 9, 2020

Hi @slavvka
Could i kindly ask you help me with failed EE and B2B test.
Maybe you could provide error message ?
Thanks.

@Usik2203 Usik2203 removed their assignment Sep 9, 2020
@rogyar
Copy link
Contributor

rogyar commented Sep 13, 2020

Hi @Usik2203. Have you tried to run the MFTF tests with your changes on EE/B2B setup locally? You might get a clue from this attempt

@Usik2203
Copy link
Contributor Author

@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B

@Usik2203
Copy link
Contributor Author

Hi @rogyar
Fixed it by creating related PR
Thanks.

@magento-engcom-team
Copy link
Contributor

Hi @sidolov, thank you for the review.
ENGCOM-8209 has been created to process this Pull Request
✳️ @sidolov, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@sidolov sidolov added Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Risk: low labels Sep 14, 2020
@gabrieldagama
Copy link
Contributor

@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B

@gabrieldagama
Copy link
Contributor

@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B

@gabrieldagama
Copy link
Contributor

@magento run all tests

@m2-assistant
Copy link

m2-assistant bot commented Sep 18, 2020

Hi @Usik2203, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

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 Component: Bundle Component: Catalog Component: ConfigurableProduct Component: Downloadable Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner Priority: P3 May be fixed according to the position in the backlog. Progress: accept Release Line: 2.4 Risk: low Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[Issue] [MFTF] add new AdminOpenCatalogProductPageActionGroup
5 participants