What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hi all, We created our internal composer module (package) for spryker and now we have little proble

USZB5JN4W
USZB5JN4W Posts: 112 🧑🏻‍🚀 - Cadet
in Help

Hi all,
We created our internal composer module (package) for spryker and now we have little problem with unit tests. One class which we need to test works on and creates transfer objects. As long as this module was just in Pyz namespace, there was no problem, because transfer objects are generated by spryker and visible. But now, when this package is separate one, we don't have access (or we can't do it) to transfer objects generator and tests are failing on "FooTransfer" doesn't exist". Mock won't work in this case, because transfer is created inside class logic. Do you know how can we generate transfers or what can we do to make tests work?

Comments

Categories