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

Fix/inconsistent test names #22853

Conversation

lbajsarowicz
Copy link
Contributor

Description (*)

Extracted the Tests that were coupled several in one file to separate files.

Fixed Issues (if relevant)

Not applicable

Manual testing scenarios (*)

  1. vendor/bin/mftf generate:tests
  2. Enjoy!

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 May 12, 2019

Hi @lbajsarowicz. 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-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

@peterlohaus
Copy link

@magento-engcom-team give me 2.3-develop instance

@magento-engcom-team
Copy link
Contributor

Hi @peterlohaus. Thank you for your request. I'm working on Magento 2.3-develop instance for you

@magento-engcom-team
Copy link
Contributor

Hi @peterlohaus, here is your Magento instance.
Admin access: https://i-22853-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

…nt-test-names

# Conflicts:
#	app/code/Magento/Checkout/Test/Mftf/Test/CheckCheckoutSuccessPageAsRegisterCustomer.xml
@dmytro-ch
Copy link
Contributor

dmytro-ch commented May 27, 2019

Hi @lbajsarowicz,
thank you for your contribution!

Please note, the MFTF tests improvements should be provided in the scope of magento/magento-functional-tests-migration repository.
Could you please move the current pull request to the MFTF project?

The current pull request will be closed.

CC: @okolesnyk

@lbajsarowicz
Copy link
Contributor Author

IMHO This is change to tests coupled with modules, not MFTF itself. If it was related with Testing Framework, I would apply changes to MFTF repository.

@okolesnyk
Copy link
Member

Hi @dmytro-ch

Currently we require to move PRs to magento/magento-functional-tests-migration only if they are related to MTF tests conversion.

Changes related to existing MFTF test should go to magento/magento2 repo.

@ghost
Copy link

ghost commented Jun 4, 2019

@okolesnyk unfortunately, only members of the maintainers team are allowed to remove progress related labels to the pull request

Łukasz Bajsarowicz added 2 commits June 11, 2019 11:45
…nt-test-names

# Conflicts:
#	app/code/Magento/Captcha/Test/Mftf/Test/CaptchaFormsDisplayingTest.xml
#	app/code/Magento/Checkout/Test/Mftf/Test/StorefrontCustomerCheckoutTest.xml
#	app/code/Magento/ConfigurableProduct/Test/Mftf/Test/AdminConfigurableProductUpdateTest.xml
#	app/code/Magento/Customer/Test/Mftf/Test/ChangingSingleCustomerGroupViaGrid.xml
#	app/code/Magento/Tax/Test/Mftf/Test/StorefrontTaxQuoteCartTest.xml
@lbajsarowicz
Copy link
Contributor Author

@okolesnyk Rebased to latest 2.3-develop

@dmytro-ch
Copy link
Contributor

Hi @okolesnyk, thank you for the details! :)

This was referenced Nov 28, 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

10 participants