Skip to content

[MFTF] Use action group for logout #28942

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

Merged

Conversation

Usik2203
Copy link
Contributor

Use <actionGroup ref="AdminLogoutActionGroup" stepKey="amOnLogoutPage"/> for logout instead
<amOnPage url="{{AdminLogoutPage.url}}" stepKey="amOnLogoutPage"/>

@m2-assistant
Copy link

m2-assistant bot commented Jun 30, 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.

@Usik2203
Copy link
Contributor Author

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

Copy link
Contributor

@lbajsarowicz lbajsarowicz left a comment

Choose a reason for hiding this comment

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

✔️ Nice catch! I remember that I've done it once or twice, but there are still leftovers, as we can see. Appreciate your efforts to get rid of such.

@@ -40,7 +40,7 @@
<click selector="{{CurrencySetupSection.currencyOptions}}" stepKey="closeOptions"/>
<waitForPageLoad stepKey="waitForCloseOptions"/>
<click stepKey="saveUnselectedConfigs" selector="{{AdminConfigSection.saveButton}}"/>
<amOnPage url="{{AdminLogoutPage.url}}" stepKey="logout"/>
<actionGroup ref="AdminLogoutActionGroup" stepKey="amOnLogoutPage"/>
Copy link
Contributor

Choose a reason for hiding this comment

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

If you can keep the original stepKey that would be appreciated, as some developers might have attached their Actions to it.

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

@magento-engcom-team
Copy link
Contributor

Hi @lbajsarowicz, thank you for the review.
ENGCOM-7767 has been created to process this Pull Request
✳️ @lbajsarowicz, 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

@@ -34,7 +34,7 @@
<actionGroup ref="AdminDeleteCustomerActionGroup" stepKey="deleteCustomer">
<argument name="customerEmail" value="CustomerEntityOne.email"/>
</actionGroup>
<amOnPage url="{{AdminLogoutPage.url}}" stepKey="logout"/>
<actionGroup ref="AdminLogoutActionGroup" stepKey="amOnLogoutPage"/>
Copy link
Contributor

Choose a reason for hiding this comment

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

If you can keep the original stepKey that would be appreciated, as some developers might have attached their Actions to it.

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

@lbajsarowicz
Copy link
Contributor

@magento run Functional Tests EE

@Usik2203
Copy link
Contributor Author

Usik2203 commented Jul 1, 2020

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

@Usik2203
Copy link
Contributor Author

Usik2203 commented Jul 1, 2020

@magento run Functional Tests EE

@engcom-Delta
Copy link
Contributor

Notice: QA not applicable

@engcom-Charlie
Copy link
Contributor

@magento run all tests

@engcom-Charlie engcom-Charlie added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Jul 9, 2020
@slavvka slavvka added this to the 2.4.1 milestone Jul 9, 2020
@slavvka slavvka 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 Jul 9, 2020
@magento-engcom-team magento-engcom-team merged commit ddd1f98 into magento:2.4-develop Jul 11, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jul 11, 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: Covered All changes in Pull Request is covered by auto-tests Component: Bundle Component: Catalog Component: CatalogRule 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 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.

6 participants