[GraphQl] Adding Wishlist GraphQl coverage

[eduard13]

Description (*)

This PR implements the Wishlist GraphQl

Solution Architecture

Related Pull Requests

https://github.com/magento/partners-magento2ee/pull/247

Fixed Issues (if relevant)

1. Customer :: MyAccount :: Wishlist Management

Manual testing scenarios (*)

Please check the following document, in order to add different types of products to wishlist.

Add products to wishlist

mutation {
  addProductsToWishlist(
    wishlistId: 0, // It may be always 0 for CE version
    wishlistItems: [
      {
        sku: "24-MB01"
        quantity: 3
      }
    ]
) {
    userInputErrors {
      code
      message
    }
    wishlist {
      id
      name
      sharing_code
      items_count
      items {
        id
        description
        qty
        added_at
      }
    }
  }
}

Update wishlist item

mutation {
  updateProductsInWishlist(
    wishlistId: <wishlist_id>,
    wishlistItems: [
    {
  	wishlist_item_id: <wishlist_item_id>,
  	quantity: <quantity>,
        description: "Test Description"
    }
    ]
) {
    userInputErrors {
      code
      message
    }
    wishlist {
      id
      sharing_code
      items_count
      items {
        id
        description
        qty
        added_at
      }
    }
  }
}

Remove wishlist item

mutation {
  removeProductsFromWishlist(
    wishlistId: <wishlist_id>, 
    wishlistItemsIds: [<wishlist_item_id>]
) {
    wishlist {
      name
      items_count
    }
  }
}

Questions or comments

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]

Hi @eduard13. 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.

[eduard13]

@magento run Static Tests

[eduard13]

@magento run Static Tests

[eduard13]

@magento run all tests

[eduard13]

@magento run all tests

[rogyar]

As a rule, we don't prefix resolvers with the "Resolver" keyword. We have some cases but they come from the past. It's not about something critical, but with the prefix we have quite a long class/file name.
I would not put the prefix

[eduard13]

Was checking the resolvers from the same folder. However, the suffixes were removed.

[eduard13]

@magento run Static Tests, Magento Health Index

[eduard13]

@magento run Static Tests, Magento Health Index

[magento-engcom-team]

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

[lenaorobei]

Please check failed web-api tests https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/partners-magento2ee/pull/248/da6b0e91b08de451def0496ff26e663a/WebApi/allure-report-b2b-WebAPI-GRAPHQL/index.html

[eduard13]

@magento run WebAPI Tests

[eduard13]

Hi @lenaorobei those failing tests are caused by MultipleWishlist related PR. Please check this comment for additional information

[lenaorobei]

In this case those PRs should be delivered as related and builds triggered for corresponding ce/ee branches.

[lenaorobei]

@magento run all tests

[eduard13]

@lenaorobei looks like everything is green ✅ here. Are we able to proceed further with this one or are there any additional requirements from my side?
Thank you.

[eduard13]

@magento run all tests

[lenaorobei]

@dthampy this PR is ready for QA.

[keharper]

I sent @eduard13 a schema file that contains updated descriptions.

[eduard13]

Thank you @keharper, I've just updated it.

[eduard13]

@magento run all tests

[m2-assistant]

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