How are the tests in vendor modules executed ?
I have some custom modules that I have created and I would like to use them throughout projects, by making them as composer packages.
I was wondering how to bundle the tests inside the composer package. For inspiration I took a look at how the Spryker vendor modules structure the tests. I used the same structure and I can make simple assertion tests work, but if I want to use database for example, by incudling
TransactionHelper, then when I run the tests, I get an error:
Could not find config key "PROJECT_NAMESPACES" in "Spryker\Shared\Config\Config"
Curiously, when I try to run the tests in Spryker vendor modules, I get the same error.
I use the usual algorithm for testing:
codecept run -c path-to-suite
I see for example that in Availability module there are tests that use product helpers to get a product:
codeception.yml files do not have anything out of the ordinary, besides the fact that
LocatorHelper has no
So can anyone explain how the vendor module tests are executed ?
- All Categories
- 38 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 33 Spryker News
- 549 Developer Corner
- 420 Spryker Development
- 54 Spryker Dev Environment
- 284 Spryker Releases
- 30 Propel ORM
- 46 Community Projects
- 6 Gacela Project
- 3 PHP Bridge
- 21 Hackathon
- 3.2K 📜 Slack Archives
- 115 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random
- 4 Code Testing
- 23 Product & Business Questions
- 44 Spryker Safari Questions
- 36 The Blackhole