Skip to content

Conversation

@ajithkumar-maragathavel
Copy link
Contributor

@ajithkumar-maragathavel ajithkumar-maragathavel commented Feb 9, 2020

Description (*)

  1. AdminCreateCmsPageTest doesn't have delete action, after creating a CMS page. Added a CMS page delete action in the existing test.
  2. A single test file contains multiple tests. So moved the test to separate files to follow best practices.

Manual testing scenarios (*)

  1. Run the AdminCreateCmsPageTest in the local environment and verified test is running.
  2. Run the AdminCreateDuplicatedCmsPageTest in the local environment and verified test is running.
  3. Run the AdminConfigDefaultCMSPageLayoutFromConfigurationSettingTest in the local environment and verified test is running.

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 Feb 9, 2020

Hi @ajithkumar-maragathavel. 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

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

@ajithkumar-maragathavel ajithkumar-maragathavel changed the title Delete action added for CMS page creation MTFT test Module_Cms MFTF test improvements Feb 9, 2020
@rogyar rogyar self-assigned this Feb 9, 2020
@rogyar rogyar added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Feb 9, 2020
@rogyar
Copy link
Contributor

rogyar commented Feb 9, 2020

Hi @ajithkumar-maragathavel. Thank you for your collaboration. In your next PRs you can also consider rebuilding the tests according to the best practices. For example, building a test body using action groups only. But keep backward compatibility in mind.

@magento-engcom-team
Copy link
Contributor

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

@ajithkumar-maragathavel
Copy link
Contributor Author

@rogyar I will update the test using only the action group in my next PR. Thanks for the review and providing the best practices link.

</annotations>
<before>
<actionGroup ref="LoginActionGroup" stepKey="loginGetFromGeneralFile"/>
<actionGroup ref="DisabledWYSIWYGActionGroup" stepKey="disableWYSIWYG"/>
Copy link
Contributor

Choose a reason for hiding this comment

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

@rogyar I don't remember, but it's no longer necessary to add this. How do you think?

@ghost ghost assigned lbajsarowicz Feb 9, 2020
@magento-engcom-team
Copy link
Contributor

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

@engcom-Delta engcom-Delta self-assigned this Feb 10, 2020
@engcom-Delta
Copy link
Contributor

Notice: QA not applicable

@engcom-Echo engcom-Echo self-assigned this Feb 10, 2020
@lenaorobei lenaorobei removed the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Feb 10, 2020
@lenaorobei lenaorobei added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Feb 10, 2020
@magento-engcom-team magento-engcom-team merged commit eff07be into magento:2.4-develop Feb 13, 2020
@m2-assistant
Copy link

m2-assistant bot commented Feb 13, 2020

Hi @ajithkumar-maragathavel, 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants