-
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
[MFTF] add new AdminOpenConfigurationStoresPageActionGroup #29827
[MFTF] add new AdminOpenConfigurationStoresPageActionGroup #29827
Conversation
Hi @Usik2203. 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 |
@magento run Functional Tests CE , Functional Tests EE , Functional Tests B2B |
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.
The Page does not follow Magento Best Practices.
Are you able to adjust that in scope of this PR?
<description>Open configuration stores page.</description> | ||
</annotations> | ||
|
||
<amOnPage url="{{ConfigurationStoresPage.url}}" stepKey="goToConfigurationStoresPage"/> |
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.
Could you also deprecate the old Page
object and introduce new one that actually follows the Magento Best Practices (AdminConfigurationStoresPage
)?
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.
@lbajsarowicz Done
@magento create issue |
@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B |
@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B Failing tests are not related with the scope of change. |
@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B |
@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B |
The risk was set to |
Hi @lbajsarowicz |
Hi @sidolov, thank you for the review.
|
Hi @gabrieldagama, unfortunately there is no ability to deploy `` Magento instance. Please make sure you specify the correct Magento version/branch. |
@magento give me new instance with extensions magento/magento2-jp |
Hi @gabrieldagama. Thank you for your request. I'm working on Magento instance for you. |
Hi @gabrieldagama, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later. |
Hi @Usik2203, thank you for your contribution! |
This PR add new
AdminOpenConfigurationStoresPageActionGroup
and use this one instead<amOnPage url="{{ConfigurationStoresPage.url}}" stepKey="navigateToWYSIWYGConfigPage1"/>
<waitForPageLoad stepKey="wait1"/>
Resolved issues: