Bug while write graphql api test with Magento\Customer\Test\Fixture\Customer fixture

[Citizen4our]

Bug while write graphql api test with Magento\Customer\Test\Fixture\Customer fixture

[m2-assistant]

Hi @Citizen4our. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

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, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @Citizen4our,

Thank you for report and collaboration!

We tried to reproduce the issue on 2.4-develop.
But for us, both the test with and without specifying website_id executed without any issues.

Please refer the screenshots below:
Without specifying website_id:

With specifying website_id:

Please let us know if we are missing something.

Thanks.

[Citizen4our]

What is the value in the database in the website_id field are you receiving? I see null in this field for customer during the test, and it is reason bug.
Maybe it related to admin settings to share customer between stores/websites?

[engcom-November]

Hello @Citizen4our,
Thank you for quick response!

We ran the test with both Share Customer Accounts set as Global and Per Website, and the test is being executed successfully for both the cases.
In the customer_entity table the website_id will be null if you do not have any customers.
If you are referring to other table, please let us know which table are you talking about.

Thank you.

[engcom-November]

Hello @Citizen4our ,

We have noticed that this issue has not been updated since long time.
Hence we assume that the issue is fixed now, so we are closing it. Please feel free to raise a new one or reopen this issue if you need more assistance.

Thanks.