[Customer] Cover CustomerData\Customer and CustomerData\JsLayoutDataProviderPool by Unit Test

[edenduong]

Description (*)

Increase Test Coverage by covering class Magento\Customer\CustomerData\JsLayoutDataProviderPool and Magento\Customer\CustomerData\Customer

Fixed Issues (if relevant)

Manual testing scenarios (*)

Covered by Unit Test
vendor/bin/phpunit app/code/Magento/Customer/Test/Unit/CustomerData/CustomerTest.php
vendor/bin/phpunit app/code/Magento/Customer/Test/Unit/CustomerData/JsLayoutDataProviderPoolTest.php

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 @edenduong. 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.

[magento-engcom-team]

Hi @kalpmehta, thank you for the review.
ENGCOM-6446 has been created to process this Pull Request
✳️ @kalpmehta, could you please add one of the following labels to the Pull Request?

Label	Description
Auto-Tests: Covered	All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered	Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required	Changes in Pull Request does not require coverage by auto-tests

[engcom-Alfa]

✔️ QA Passed

[m2-assistant]

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