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.

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

Removed redundant header issue in grid cells while adding grouped product items after changing attribute set #31142

Merged
merged 11 commits into from
Dec 21, 2020

Conversation

saphaljha
Copy link
Contributor

Description (*)

Removed redundant header issue in grid cells while adding grouped product items after changing attribute set

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Redundant header generated while add a product to grouped product #30911

Manual testing scenarios (*)

  1. Manually tested

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)

@m2-assistant
Copy link

m2-assistant bot commented Dec 2, 2020

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

@m2-community-project m2-community-project bot 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 Dec 2, 2020
@saphaljha
Copy link
Contributor Author

@magento run all tests

@saphaljha
Copy link
Contributor Author

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

Copy link
Contributor

@gabrieldagama gabrieldagama left a comment

Choose a reason for hiding this comment

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

Hi @saphaljha, thanks for your contribution!

Can you cover the changes with automated tests? I would recommend updating the app/code/Magento/GroupedProduct/Test/Unit/Ui/DataProvider/Product/Form/Modifier/GroupedTest.php test to validate/cover your changes.

Thanks.

@gabrieldagama
Copy link
Contributor

@magento run all tests

@engcom-Hotel engcom-Hotel self-assigned this Dec 3, 2020
@engcom-Hotel
Copy link
Contributor

@magento run Functional Tests CE, Functional Tests EE, Integration Tests, Unit Tests

@engcom-Hotel engcom-Hotel added the Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests label Dec 3, 2020
@saphaljha
Copy link
Contributor Author

Hi @saphaljha, thanks for your contribution!

Can you cover the changes with automated tests? I would recommend updating the app/code/Magento/GroupedProduct/Test/Unit/Ui/DataProvider/Product/Form/Modifier/GroupedTest.php test to validate/cover your changes.

Thanks.

Hello @gabrieldagama ,

Ok sure, I'll try to cover it with MFTF, also I'll work necessary update in unit test.

Thank you

@engcom-Hotel
Copy link
Contributor

@magento run Integration Tests

@engcom-Charlie engcom-Charlie self-assigned this Dec 8, 2020
@engcom-Hotel engcom-Hotel removed their assignment Dec 8, 2020
@magento-engcom-team
Copy link
Contributor

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

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Precondition:

Sample Data

Manual testing scenario:

  1. Go Admin > Catalog > Products;
  2. Select Grouped Product from drop-down of Add Product button;
  3. In the new product page, at Attribute Set select, choose Top;
  4. Scroll down to the tab Grouped Products and try to add a new product;

Before: ✖️ Redundant headers generated

2020-12-16_13-04

After: ✔️ Redundant headers were not generated

2020-12-16_13-10

@engcom-Alfa engcom-Alfa added the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Dec 16, 2020
@engcom-Alfa engcom-Alfa added QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) labels Dec 16, 2020
@engcom-Charlie
Copy link
Contributor

@magento run all tests

@m2-assistant
Copy link

m2-assistant bot commented Dec 21, 2020

Hi @saphaljha, 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 Award: bug fix Component: GroupedProduct Partner: Krish TechnoLabs 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 QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Redundant header generated while add a product to grouped product
6 participants