-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Description
The way I've been adding unit tests (for data-in-data-out functions) to my projects is by putting the data functions and their tests in a separate crate in a cargo workspace. Not sure if that's the best practice, but it seems to work well enough.
Would be nice if there was an example of what the community deams the "best" way to manage such tests in this template by default, with a basic test placeholder, and especially with the tests running in CI.
I'm not talking about the types of functions/tests that require the embedded build target. I'm more talking about tests related to data transfer objects, logical functions, etc. where the function has no embedded dependencies and runs just the same on a Linux host as a Cortex embedded system.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels