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

clear errors when apply new filters #28687

Conversation

AbdulRahmanAbouzaid
Copy link
Contributor

Description (*)

Clear error when applying new filters instead of still displaying it which is the wrong behavior as mentioned in this comment

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes No ability to reset filters after an error #8538

Manual testing scenarios (*)

  1. Create a new store view (call it "Second Store View" for example);
  2. Log in to Admin -> Catalog -> Products;
  3. Set up and apply a filter for the newly created store view;
    image
  4. Now, go to Admin->Stores->All Stores;
  5. Delete the created before "Second Store View" store view;
  6. Go to Admin->Catalog->Products again;
  7. Set up and apply a new filter and the error message will be disappeared.

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 Jun 11, 2020

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

@AbdulRahmanAbouzaid
Copy link
Contributor Author

@magento give me test instance

@magento-engcom-team
Copy link
Contributor

Hi @AbdulRahmanAbouzaid. Thank you for your request. I'm working on Magento instance for you

@AbdulRahmanAbouzaid
Copy link
Contributor Author

@magento run all tests

@ghost ghost added Priority: P3 May be fixed according to the position in the backlog. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Jun 25, 2020
Copy link
Contributor

@lenaorobei lenaorobei left a comment

Choose a reason for hiding this comment

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

Thanks for this fix. Please add MFTF test to cover expected behavior.

@AbdulRahmanAbouzaid
Copy link
Contributor Author

@lenaorobei I've provided the mftf using AdminGridFilterDeleteAndVerifyErrorMessageTest
Can you review it please?

Copy link
Contributor

@lenaorobei lenaorobei left a comment

Choose a reason for hiding this comment

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

Thanks a lot!

Please see minor review comments and suggestions.

@AbdulRahmanAbouzaid
Copy link
Contributor Author

@magento run all tests

@lenaorobei
Copy link
Contributor

@magento run Functional Tests EE

@magento-engcom-team
Copy link
Contributor

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

@lenaorobei lenaorobei added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Aug 28, 2020
@engcom-Oscar engcom-Oscar self-assigned this Sep 3, 2020
@engcom-Oscar
Copy link

engcom-Oscar commented Sep 3, 2020

✔️ QA Passed

Tested according manual scenario described in ticket

Before ✖️

Error message persists after a new filter is submitted
Peek 2020-04-08 12-09

After ✔️

Error message disappeared.

image

@engcom-Alfa engcom-Alfa self-assigned this Sep 8, 2020
@engcom-Alfa engcom-Alfa added QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope labels Sep 8, 2020
@engcom-Charlie engcom-Charlie self-assigned this Sep 8, 2020
@engcom-Charlie
Copy link
Contributor

@magento run all tests

@m2-assistant
Copy link

m2-assistant bot commented Sep 10, 2020

Hi @AbdulRahmanAbouzaid, 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
Area: Frontend Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: Ui Partner: Pinpoint partners-contribution Pull Request is created by Magento Partner Priority: P3 May be fixed according to the position in the backlog. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

No ability to reset filters after an error
6 participants