You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a Zephyr-based project using the Zephyr workspace application structure, and I'm looking for best practices on organizing integration tests only the application layer e.g. application/src/
What is the best way to organize integration testing?
What about the approach above?
In folder "integration_tests", I have to reach the componentens A to C in folder src via CMakeLists.txt.
I think, that could be a problem.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm working on a Zephyr-based project using the Zephyr workspace application structure, and I'm looking for best practices on organizing integration tests only the application layer e.g. application/src/
What is the best way to organize integration testing?
├── .west/
├── zephyr/
├── bootloader/
├── modules/
├── tools/
├── <vendor/private-repositories>/
└── applications/
├──── app/
├────└── src/
├────────└── component_A/
├────────└── component_B/
├────────└── component_C/
├────└── integration_tests/
├──── arch/
├──── ..
├──── tests/
What about the approach above?
In folder "integration_tests", I have to reach the componentens A to C in folder src via CMakeLists.txt.
I think, that could be a problem.
What is your opinion on this approach?
Beta Was this translation helpful? Give feedback.
All reactions