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

[Issue] [MFTF] Refactoring of AdminMassProductPriceUpdateTest #31073

Closed
m2-assistant bot opened this issue Nov 26, 2020 · 1 comment · Fixed by #31057
Closed

[Issue] [MFTF] Refactoring of AdminMassProductPriceUpdateTest #31073

m2-assistant bot opened this issue Nov 26, 2020 · 1 comment · Fixed by #31057
Assignees
Labels
Component: Catalog Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Progress: PR in progress Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.

Comments

@m2-assistant
Copy link

m2-assistant bot commented Nov 26, 2020

This issue is automatically created based on existing pull request: #31057: [MFTF] Refactoring of AdminMassProductPriceUpdateTest


Description (*)

The test is refactored according to the best practices followed by MFTF.

Manual testing scenarios (*)

  1. Create 2 simple products
  2. Go to Admin->Catalog->Products
  3. Update price of the products via mass update
  4. Check if price is updated on the Product Edit page (for both products)
@m2-assistant m2-assistant bot added Component: Catalog Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Nov 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Catalog Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Progress: PR in progress Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Status: Pull Request In Progress
Development

Successfully merging a pull request may close this issue.

2 participants