Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[MFTF] Refactoring AdminValidateShippingTrackingNumberTest #31488

Merged
merged 3 commits into from
Feb 5, 2021
Merged

[MFTF] Refactoring AdminValidateShippingTrackingNumberTest #31488

merged 3 commits into from
Feb 5, 2021

Conversation

AnnaAPak
Copy link
Contributor

@AnnaAPak AnnaAPak commented Dec 29, 2020 •
edited by m2-assistant bot
Loading

Description (*)

The test is refactored to improve execution time

Manual testing scenarios (*)

  1. Create an order
  2. Create a shipment
  3. Add tracking number for the shipment
  4. Make assertions

Resolved issues:

  1. resolves [Issue] [MFTF] Refactoring AdminValidateShippingTrackingNumberTest #31520: [MFTF] Refactoring AdminValidateShippingTrackingNumberTest

@m2-assistant
Copy link

m2-assistant bot commented Dec 29, 2020

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

@magento-engcom-team magento-engcom-team added Component: Shipping Release Line: 2.4 Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner labels Dec 29, 2020
@AnnaAPak
Copy link
Contributor Author

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

@AnnaAPak AnnaAPak force-pushed the ref-AdminValidateShippingTrackingNumberTes branch from 60822d5 to 4fb3216 Compare January 4, 2021 09:55
@AnnaAPak AnnaAPak force-pushed the ref-AdminValidateShippingTrackingNumberTes branch from 4fb3216 to 0406e76 Compare January 4, 2021 09:59
@AnnaAPak
Copy link
Contributor Author

AnnaAPak commented Jan 4, 2021

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

@rogyar rogyar added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Jan 4, 2021
@rogyar rogyar self-assigned this Jan 4, 2021
@m2-community-project m2-community-project bot added this to Review in Progress in Pull Requests Dashboard Jan 4, 2021
@m2-community-project m2-community-project bot moved this from Review in Progress to Ready for Testing in Pull Requests Dashboard Jan 4, 2021
@magento-engcom-team
Copy link
Contributor

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

@sidolov sidolov added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Jan 4, 2021
@sidolov
Copy link
Contributor

sidolov commented Jan 4, 2021

@magento create issue

@m2-assistant m2-assistant bot mentioned this pull request Jan 4, 2021
Closed
@m2-community-project m2-community-project bot removed this from Ready for Testing in Pull Requests Dashboard Jan 4, 2021
@engcom-Alfa engcom-Alfa self-assigned this Jan 5, 2021
@engcom-Alfa
Copy link
Contributor

QA not applicable

@engcom-Alfa engcom-Alfa moved this from Ready for Testing to Testing in Progress in High Priority Pull Requests Dashboard Jan 5, 2021
@engcom-Alfa engcom-Alfa moved this from Testing in Progress to Extended Testing (optional) in High Priority Pull Requests Dashboard Jan 5, 2021
@engcom-Foxtrot engcom-Foxtrot self-assigned this Jan 5, 2021
@m2-community-project m2-community-project bot moved this from Extended Testing (optional) to Ready for Testing in High Priority Pull Requests Dashboard Jan 5, 2021
@engcom-Foxtrot
Copy link
Contributor

@magento run all tests

@engcom-Bravo engcom-Bravo moved this from Ready for Testing to Extended Testing (optional) in High Priority Pull Requests Dashboard Jan 5, 2021
@engcom-Foxtrot
Copy link
Contributor

@magento run all tests

@engcom-Foxtrot engcom-Foxtrot moved this from Extended Testing (optional) to Merge in Progress in High Priority Pull Requests Dashboard Jan 6, 2021
@gabrieldagama
Copy link
Contributor

@magento run all tests

@gabrieldagama
Copy link
Contributor

@magento run Functional Tests EE

@gabrieldagama
Copy link
Contributor

@magento run Functional Tests EE, Integration Tests

@gabrieldagama
Copy link
Contributor

@magento run Functional Tests EE

1 similar comment
@gabrieldagama
Copy link
Contributor

@magento run Functional Tests EE

magento-engcom-team pushed a commit that referenced this pull request Feb 5, 2021
@gabrieldagama
ENGCOM-8593: [MFTF] Refactoring AdminValidateShippingTrackingNumberTest
0d98fdc 
#31488
@magento-engcom-team magento-engcom-team merged commit 99a1d01 into magento:2.4-develop Feb 5, 2021
@m2-assistant
Copy link

m2-assistant bot commented Feb 5, 2021

Hi @AnnaAPak, 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.

@gabrieldagama gabrieldagama moved this from Merge in Progress to Recently Merged in High Priority Pull Requests Dashboard Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rogyar rogyar rogyar approved these changes

Assignees

@rogyar rogyar

@engcom-Alfa engcom-Alfa

@engcom-Foxtrot engcom-Foxtrot

Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: Shipping Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Issue] [MFTF] Refactoring AdminValidateShippingTrackingNumberTest
7 participants
@AnnaAPak @magento-engcom-team @sidolov @engcom-Alfa @engcom-Foxtrot @gabrieldagama @rogyar