Skip to content

Improve JS Translation DataProviderTest #32689

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

Open
wants to merge 3 commits into
base: 2.4-develop
Choose a base branch
from

Conversation

navarr
Copy link
Member

@navarr navarr commented Apr 7, 2021

Description (*)

Currently, DataProviderTest checks that the entire dictionary matches only its translations. When third party extensions are installed that have translation files, this test may fail.

This fix ensures that it is only testing the task it is performing.

Related Pull Requests

  • Test Failure in magento/ext-vertex#96

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)

Resolved issues:

  1. resolves [Issue] Improve JS Translation DataProviderTest #39243: Improve JS Translation DataProviderTest

Currently, DataProviderTest checks that the entire dictionary matches only its translations.  When third party extensions are installed that have translation files, this test may fail.

This fix ensures that it is only testing the task it is performing.
@m2-assistant
Copy link

m2-assistant bot commented Apr 7, 2021

Hi @navarr. Thank you for your contribution
Here are 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
  13. Semantic Version Checker

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

@navarr
Copy link
Member Author

navarr commented Apr 7, 2021

@magento run Integration Tests

@ihor-sviziev
Copy link
Contributor

@magento run all tests

@ihor-sviziev ihor-sviziev added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Apr 8, 2021
@ihor-sviziev
Copy link
Contributor

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

@ihor-sviziev ihor-sviziev added the Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. label Apr 8, 2021
Copy link
Contributor

@eduard13 eduard13 left a comment

Choose a reason for hiding this comment

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

Hi @navarr, could you please check my question below and suggested changes?
Thank you.

@navarr
Copy link
Member Author

navarr commented Apr 8, 2021

@magento run all tests

@navarr
Copy link
Member Author

navarr commented Apr 8, 2021

@eduard13 I've applied your suggestions. I default to static since it's the most flexible, but you're right - there's no real reason for late static binding here.

@eduard13 eduard13 added the Priority: P3 May be fixed according to the position in the backlog. label Apr 8, 2021
@navarr
Copy link
Member Author

navarr commented Apr 8, 2021

@mageto run Functional Tests EE, Functional Tests B2B

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests EE, Functional Tests B2B

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-8995 has been created to process this Pull Request

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B, Functional Tests EE

2 similar comments
@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests B2B, Functional Tests EE

@Den4ik
Copy link
Contributor

Den4ik commented May 5, 2021

@magento run Functional Tests B2B, Functional Tests EE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@ihor-sviziev
Copy link
Contributor

@magento run Functional Tests EE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@navarr navarr requested a review from eduard13 July 15, 2021 12:24
@magento-engcom-team
Copy link
Contributor

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

@magento-engcom-team
Copy link
Contributor

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

@engcom-Charlie engcom-Charlie self-assigned this Oct 1, 2024
@engcom-Charlie
Copy link
Contributor

@magento run all tests

@engcom-Charlie
Copy link
Contributor

@magento create issue

@engcom-Charlie
Copy link
Contributor

Hi @navarr,

Thank you for your contribution!

Manual testing is not required for this PR as its making the changes in test assertions. Code looks good and the build is green, hence considering it as QA passed and moving it to Merge In Progress.

Thank you!

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 Award: bug fix Partner: Blue Acorn iCi partners-contribution Pull Request is created by Magento Partner Priority: P3 May be fixed according to the position in the backlog. Progress: ready for testing Release Line: 2.4 Risk: low Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
Status: Merge in Progress
Development

Successfully merging this pull request may close these issues.

[Issue] Improve JS Translation DataProviderTest
7 participants