Magento\TestFramework\Annotation\ConfigFixture Error

[SergeLavrentyev]

Preconditions and environment

• Magento version 2.4.6-p3

Steps to reproduce

1. create core_config _data with value = 0.
2. add magentoConfigFixture to integration test @magentoConfigFixture example/path/test 1

Expected result

test passes

Actual result

Magento\TestFramework\App\ApiMutableScopeConfig::persistConfig(): Argument #2 ($value) must be of type string, null given, called in /repo/magento/dev/tests/api-functional/framework/Magento/TestFramework/App/ApiMutableScopeConfig.php on line 79

Additional information

After getting value from db, '0' converts to NULL here magento/dev/tests/api-functional/framework/Magento/TestFramework/Annotation/ApiConfigFixture.php:158

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without 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[bot]]

Hi @SergeLavrentyev. 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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[bot]]

Hi @engcom-Hotel. 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: :point_down:

• [ ] 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

  - 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-Hotel]

Hello @SergeLavrentyev,

Thanks for the report and collaboration!

We have tried to reproduce the issue in the latest development branch i.e. 2.4-develop, but for us, the issue is not reproducible.

As per the main description, first, we tried to create a custom integration test with @magentoConfigFixture example/path/test 1, but the issue is not reproducible for us. Please refer to the below screenshot for reference:

But then we checked the error you mentioned in the main description, and according to the error, it seems you are facing an issue is in api- functional test. So then we tried to reproduce it api-functional test following the below steps:

1. Edit file https://github.com/magento/magento2/blob/a4cf5e62468770fdb9f7b48938f6644ae354a51b/dev/tests/api-functional/testsuite/Magento/Catalog/Api/AttributeSetManagementTest.php#L35
2. Add @magentoConfigFixture example/path/test 1 for testCreate method
3. Ran the test via the below command: ../../../vendor/bin/phpunit -c ../../../dev/tests/api-functional/phpunit_rest.xml --filter 'testCreate' ../../../dev/tests/api-functional/testsuite/Magento/Catalog/Api/AttributeSetManagementTest.php

The test was completed successfully. Please refer to the below screenshot:

Please let us know if we have missed anything.

Thanks

[engcom-Hotel]

Dear @SergeLavrentyev,

We've observed that there haven't been any updates on this issue for quite some time. Therefore, we're assuming it's been resolved and will be closing it. Feel free to open a new ticket or reopen this one if you require further assistance.

Regards