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

Extending MFTF Tests #656

Merged
merged 6 commits into from
Oct 21, 2020
Merged

Extending MFTF Tests #656

merged 6 commits into from
Oct 21, 2020

Conversation

bluemwhitew
Copy link
Contributor

@bluemwhitew bluemwhitew commented Oct 20, 2020

Description (*)

Extends MFTF tests based on the Manual Testing Scenarios in #558.

Fixed Issues

  1. Fixes Developer can style content types output differently per viewport #558

Related Pull Requests

magento/magento2#30565
https://github.com/magento/partners-magento2ee/pull/387
https://github.com/magento/magento2-page-builder-ee/pull/171

Manual Testing Scenarios (*)

N/A

Questions or Comments

N/A

Contribution Checklist (*)

  • Author has signed the Adobe CLA
  • 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)

- Extending MFTF Tests for CSS Specificity
- Extending MFTF Tests for CSS Responsive Styling
- Removing Heading Type in CSS Specificity
@bluemwhitew bluemwhitew requested review from dhaecker and omiroshnichenko and removed request for dhaecker and omiroshnichenko October 20, 2020 13:52
@bluemwhitew
Copy link
Contributor Author

@magento run all tests

@bluemwhitew
Copy link
Contributor Author

@magento run Functional Tests B2B, Functional Tests EE

1 similar comment
@omiroshnichenko
Copy link
Contributor

@magento run Functional Tests B2B, Functional Tests EE

@omiroshnichenko
Copy link
Contributor

@magento run Functional Tests B2B, Functional Tests EE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

Developer can style content types output differently per viewport
3 participants