Improve the structure of GraphQL tests for Catalog Module

[yaroslavGoncharuk]

Summary (*)

Catalog Module covers a significant number of use-cases and has a lot of GraphQL tests.
However, the structure of test files is unclear and makes navigation through it hard.

Examples (*)

GraphQL tests for Catalog module

Proposed solution

1. Create two sub-folders in Catalog folder: Product and Category
2. Move all product-related tests to created Product sub-folder
3. Move existed CategoriesQuery folder to created Category folder
4. Create two additional sub-folders in Category folder: GategoryQuery and CategoryListQuery
5. Move category() query related tests to CategoryQuery sub-folder
6. Move categoryList() query related tests to CategoryListQuery sub-folder
7. Rename Options (Catalog/Options) folder to CustomizableOptions
8. Move CustomizableOptions folder to Product folder
9. Rename file MediaGalleryTest.php to ProductMediaGalleryTest.php
10. Rename file UrlRewritesTest.php to ProductUrlRewritesTest.php
11. Leave StoreConfigTest.php file in Catalog folder
12. Leave ExceptionFormatterDefaultModeTest.php file in Catalog folder

Expected Files Tree Example:

dev/tests/api-functional/testsuite/Magento/GraphQl/Catalog/

• Category/
  • CategoriesQuery/
    • categories() query related tests
    • ...Test.php
  • CategoryListQuery/
    • categoryList() query related tests
    • ...Test.php
  • CategoryQuery/
    • category() query related tests
    • ...Test.php
• Product/
  • ProductViewTest.php
  • ProductPriceTest.php
  • VirtualProductTest.php
  • ...Test.php
  • CustomizableOptions/
    • Uid/CustomizableOptionsUidTest.php

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users with no workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @yaroslavGoncharuk. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[sasha19957099]

@magento I am working on this