I'm trying to use `SprykerTest\Shared\Sales\Helper\SalesDataHelper->haveOrderFromQuote()` to crea

U01LKKBK97T

I'm trying to use SprykerTest\Shared\Sales\Helper\SalesDataHelper->haveOrderFromQuote() to create a test order. Seems to work basically, but I'm running into issues when using custom pre save plugins.
In Pyz\Zed\Sales\SalesDependencyProvider->getOrderItemExpanderPreSavePlugins() there is a plugin which is located in a different module (ProductAttribute). The plugin itself is calling a function from its module's facade, of course.
When executing the test, it dies telling me that the facade function doesn't exist. This is because the test uses the ProductAttributeFacade from core, not the one on project level.
Any idea what's going wrong here?

Stanislav Matveyev

\SprykerTest\Shared\Sales\Helper\SalesDataHelper::getSalesFacade()

check if your plugin uses locator to get ProductAttributeFacade

return $this->getLocator()->productAttribute()->facade();

U01LKKBK97T

The plugin doesn't have a getLocator function. Only the auto-generated function getFacade.

/**
 * @method ProductAttributeFacadeInterface getFacade()
 */

Stanislav Matveyev

I see, maybe the resolver works in a wrong way in the tests env

\SprykerTest\Shared\Testify\Helper\LocatorHelper::getFacade()

U01LKKBK97T

Might be.
The main point is, that I'm not resolving this facade directly in my test.
In my test I'm using the SalesFacade only. The sales save order stack will then use a plugin which is located in the ProductAttribute module.
I can tell that we're having the SalesFacade on core level only, but the ProductAttributeFacade on project level.

Eugenia Poidenko

Have you defined the project namespaces for tests?

in codeception.yml where you add the helpers, you can configure the locator in the following way:

suites:
    Presentation:
        ...
        modules:
            enabled:
              ...
              - \SprykerTest\Shared\Testify\Helper\LocatorHelper:
                  projectNamespaces: ['Pyz']

U01LKKBK97T

Yes, I did.