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

Uses > Used for Yes/No column in coupons grid #25658

Merged
merged 3 commits into from Nov 24, 2019
Merged

Uses > Used for Yes/No column in coupons grid #25658

merged 3 commits into from Nov 24, 2019

Conversation

sta1r
Copy link
Contributor

@sta1r sta1r commented Nov 19, 2019

Description (*)

In the grid for coupon codes on each Cart Price Rule entry, there is a column for 'Uses' with options for Yes/No. This column is intended to indicate if a coupon has been used or not, so the header should be 'Used'.

Screenshot 2019-11-19 16 13 04

Manual testing scenarios (*)

  1. Go to Marketing > Promotions > Cart Price Rules
  2. Create a new rule and save it
  3. Generate some coupons against the rule
  4. See amended 'Used' column header

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)

@sta1r sta1r requested a review from akaplya as a code owner November 19, 2019 16:18
@m2-assistant
Copy link

m2-assistant bot commented Nov 19, 2019

Hi @sta1r. 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.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Guide documentation.

@magento-engcom-team
Copy link
Contributor

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

@engcom-Alfa engcom-Alfa self-assigned this Nov 20, 2019
@engcom-Alfa engcom-Alfa added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Nov 20, 2019
@engcom-Alfa
Copy link
Contributor

Hi, @sta1r Could you change this word and in the translation file?
Thanks!

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

@lbajsarowicz
Copy link
Contributor

About MFTF coverage: I'm not convinced to use that kind of tests, as it expects to have 'Used' at 4th position and it's really coupled with language, so when someone wants to test specific language - this will be another stepKey to customize.

CC: @okolesnyk

@okolesnyk
Copy link
Member

Hi @lbajsarowicz
We should provide possibility to use translations in MFTF tests. We have an issue#484 opened in MFTF repo and our team will provide solution for this. As for now I think we can move forward with current solution.
The only one comment I have is try to avoid using indices in selectors. In current situation I do recommend to create separate element only for Used column header which can look like this: #couponCodesGrid thead th[data-sort='used']

@VladimirZaets VladimirZaets added Auto-Tests: Covered All changes in Pull Request is covered by auto-tests and removed Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests labels Nov 20, 2019
@ghost ghost assigned VladimirZaets Nov 20, 2019
@magento-engcom-team
Copy link
Contributor

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

@m2-assistant
Copy link

m2-assistant bot commented Nov 24, 2019

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

@magento-engcom-team magento-engcom-team added this to the Release: 2.3.5 milestone Nov 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants