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: 👇

• 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.

Hello @stollr,

Thanks for the report and collaboration!

We request you please provide us with more details on the fix provided in the PR as below:

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

Thanks

Sorry for not providing all required information.

Magento's integration test framework offers a way to create data fixtures with the Magento\TestFramework\Fixture\DataFixture attribute. The DataFixture's fourth argument in the constructor is $scope. If a value is passed, that does not exist in the DataFixtureStorageManager it will lead to TypeError in this line.

How to reproduce

Add an integration test to your own test suite that uses a data fixture with an invalid config. For example:

<?php

namespace MyVendor\MyModule\Test\Integration;

use Magento\Catalog\Test\Fixture\Product as ProductFixture;
use Magento\TestFramework\Fixture\DataFixture;
use Magento\TestFramework\Fixture\DbIsolation;
use PHPUnit\Framework\TestCase;

class SynchronizerTest extends TestCase
{
    #[DbIsolation(true)]
    #[DataFixture(
        ProductFixture::class,
        ['sku' => 'test', 'name' => 'Test', 'price' => '7.77'],
        'test',
        'invalid_scope_key' // this line results in an error
    )]
    public function testSynchronize(): void
    { }
}

If you'll run the test now, you'll see that an error appears, because the DataFixtureStorageManager does not have an item with the key invalid_scope_key.

Hello @stollr,

Thanks for the reply!

We have tried to reproduce the issue by making a custom module, but we are getting the below error:

Please let us know if we missed anything. We are attaching the custom module as well.
Magz.zip

Thanks

Yes, this is another issue that happens in the 2.4-develop branch. This line is responsible for the error:

In the 2.4-develop branch phpunit was upgraded to v10.5, where the getTestResultObject method was removed from the TestCase class.

So there's another bug in the test framework. The error is not triggered by my PR ;-)

I have added a new issue for the error you have mentioned, @engcom-Hotel.

But to proceed with this issue, can you add a breakpoint to this line, during execution of the test. Then you should see the TypeError mentioned in my comment above.

Thanks @stollr for the information!

We have tried to reproduce the issue by adding the breakpoint mentioned in the above comment and we are able to reproduce the issue. Please refer to the below error we are getting:

Unable to apply fixture: Magento\Catalog\Test\Fixture\Product (test)
#0 app/code/Magz/Issue39427/Test/Integration/SynchronizerTest.php(19): Magz\Issue39427\Test\Integration\SynchronizerTest->testSynchronize()

Caused By: Magento\TestFramework\Store\ScopeSwitcher::switch(): Argument #1 ($scope) must be of type Magento\Framework\App\ScopeInterface, null given, called in dev/tests/integration/framework/Magento/TestFramework/Annotation/DataFixtureSetup.php on line 49

Hence confirming the issue. Thanks for the contribution.

✅ Jira issue https://jira.corp.adobe.com/browse/AC-13503 is successfully created for this GitHub issue.

✅ Confirmed by @engcom-Hotel. Thank you for verifying the issue.
Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.