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

EQPS-908: Devdocs for EQP MFTF Tests - Editable branch #8738

Merged
merged 25 commits into from
Feb 25, 2021
Merged

Conversation

dobooth
Copy link
Contributor

@dobooth dobooth commented Feb 24, 2021

Purpose of this pull request

This pull request (PR) adds pages for new EQP test types to Marketplace EQP Sellers pages. These Types are MFTF Vendor Supplied tests and MFTF Magento Tests

Affected DevDocs pages

Replaces #8663

whatsnew
Added the MFTF Magento-supplied Tests and MFTF Vendor-supplied Tests topics to the Marketplace Sellers guide.

magterskine and others added 13 commits February 9, 2021 17:08
- Added docs for MFTF Vendor Supplied and MFTF Magento tests in EQP
Added missing content
-Added missing content
Co-authored-by: Barny Shergold <barny.shergold@vaimo.com>
Co-authored-by: Barny Shergold <barny.shergold@vaimo.com>
- Updated Marketplace Sellers TOC to link to new pages
- Updated technical review guidelines page to reference new MFTF tests
Copy link
Contributor

@BarnyShergold BarnyShergold left a comment

Choose a reason for hiding this comment

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

Very minor changes

MFTF Magento supplied Tests will be run for all Marketplace extension submissions for:

- Magento in 2.3 and 2.4 release lines
- OpenSource and Commerce editions
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- OpenSource and Commerce editions
- Open Source and Commerce editions


## Reading the error report

- MFTF returns two types of results
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- MFTF returns two types of results
- MFTF returns two types of results:

- Remember that MFTF tests will be part of the final package that is made available to your customers
- Do not include any sensitive or confidential data in test comments or code
- If necessary, include a README or other instructions, within the `Test` directory, to explain any setup steps or caveats on running your MFTF tests
- Ensure that any necessary credentials, user authorization (e.g. to communicate via API key to your backend) is explained and supported via Credential management in Tests
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Ensure that any necessary credentials, user authorization (e.g. to communicate via API key to your backend) is explained and supported via Credential management in Tests
- Ensure that any necessary credentials, user authorization (e.g. to communicate via API key to your backend) is explained and supported via credential management in Tests

@vkublytskyi
Copy link
Contributor

@dobooth, what are the next steps for this PR? What should be done to have these pages published?

@vkublytskyi
Copy link
Contributor

@dobooth I would ask you to revert your latest structural changes as it breaks semantic and inconsistent with other EQP tools documentation.

We have predefined sections for each tool:

  1. Overview - general description of check
  2. What testing is for - describes why we have this check in place
  3. When testing is done - describes what conditions should be satisfied for check execution or skip
  4. What is being checked - describes the scope of check
  5. Tools and environments used - describes how we build our testing environment
  6. Reading the error report - explain how to interpret information returned by the tool
  7. Troubleshooting - describes how to avoid failures, and what to do if a reported error has no clear root cause

@dobooth
Copy link
Contributor Author

dobooth commented Feb 25, 2021

@magento import code to magento-devdocs/devdocs

@magento-engcom-team
Copy link

@dobooth the branch with code successfully imported intomagento-devdocs/devdocs repository. Branch name: imported-magento-devdocs-8738.

@dobooth dobooth added the New Topic A major update published as an entirely new document label Feb 25, 2021
@dobooth
Copy link
Contributor Author

dobooth commented Feb 25, 2021

running tests

@dobooth dobooth merged commit 5e1411d into master Feb 25, 2021
@dobooth dobooth deleted the db_eqps_edit branch February 25, 2021 22:37
@ghost
Copy link

ghost commented Feb 25, 2021

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

@vkublytskyi
Copy link
Contributor

@dobooth, @keharper During technical review were made following errors which I consider as critical:


Section of "When testing is done" for both new pages are:

The MFTF tests are run as a regular part of the installation and Varnish testing process.

This is technically not correct and misleading users as these checks run in parallel with Installation and Varnish tests and fully isolated from each other

Original text was

MFTF vendor supplied Tests are run only where:

  • There are MFTF tests included in the submission in the correct directory (Tests/Mftf)
  • Only for MFTF v3.0 or greater
  • Only for Magento v2.4.0 or greater

MFTF Magento supplied Tests will be run for all Marketplace extension submissions for:

  • Magento in 2.3 and 2.4 release lines
  • OpenSource and Commerce editions

Page https://devdocs.magento.com/marketplace/sellers/mftf-vendor.html has duplicated section What is being checked


Therefore we will create tomorrow new PR with the necessary fixes. Hope we will be able to process it quickly so users will have the best experience with reading our docs.

CC @magterskine

@jeff-matthews jeff-matthews added the Internal Dev Differentiates work between community and Magento staff label Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Internal Dev Differentiates work between community and Magento staff New Topic A major update published as an entirely new document Progress: done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants