Skip to content

501 mftf fails to rerun when storefront customer log out occurs after customer deletion #31101

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

sagar1dahiwala
Copy link
Contributor

@sagar1dahiwala sagar1dahiwala commented Nov 30, 2020

Description (*)

Updated MFTF Tests that fails to Rerun When Test Logs Out of Storefront After Deleting Customer

Related Pull Requests

  1. https://github.com/magento/partners-magento2b2b/pull/507
  2. https://github.com/magento/partners-magento2ee/pull/430

Fixed Issues (if relevant)

  1. Fixes magento/partners-magento2b2b#501

Manual testing scenarios (*)

  1. None

Questions or comments

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)

- Updating CE test when log out performed after customer is deleted
- Updating CE test when log out performed after customer is deleted
- All the test are covered
@m2-assistant
Copy link

m2-assistant bot commented Nov 30, 2020

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

@danmooney2
Copy link
Contributor

@magento run Functional Tests CE

@danmooney2 danmooney2 marked this pull request as ready for review November 30, 2020 18:54
@danmooney2 danmooney2 changed the title 501 mftf fails to rerun when logs out 501 mftf fails to rerun when storefront customer log out occurs after customer deletion Nov 30, 2020
@@ -48,6 +48,8 @@
</before>

<after>
<!-- Customer Log Out -->
<actionGroup ref="StorefrontCustomerLogoutActionGroup" stepKey="customerLogout"/>
Copy link
Contributor

Choose a reason for hiding this comment

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

Please use the same stepkey: customerLogoutStorefront

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated.

@@ -22,8 +22,9 @@
<createData entity="Simple_US_Customer" after="createCategory" stepKey="createCustomer"/>
</before>
<after>
<!-- Logout customer -->
<actionGroup ref="StorefrontCustomerLogoutActionGroup" stepKey="customerLogoutStorefront"/>
Copy link
Contributor

Choose a reason for hiding this comment

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

Please use the same step key: logoutFromCustomer

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated.

@danmooney2
Copy link
Contributor

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

@danmooney2
Copy link
Contributor

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

@danmooney2
Copy link
Contributor

@magento run Functional Tests CE, Functional Tests EE, Semantic Version Checker

… When Test Logs Out of Storefront After Deleting Customer

- Fixing SVC failures
@dhaecker
Copy link
Contributor

dhaecker commented Dec 1, 2020

@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B, Semantic Version Checker

@dhaecker
Copy link
Contributor

dhaecker commented Dec 2, 2020

@magento run Functional Tests CE, Functional Tests EE, Functional Tests B2B, Semantic Version Checker

@m2-assistant
Copy link

m2-assistant bot commented Dec 10, 2020

Hi @sagar1dahiwala, 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
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants