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 a newcomer to ceedling and I mainly try to use for unit testing.
I have some modules in my project.yml where I need to override or extend some common global include search paths.
I have tried this:
However, the :include: section of :test_module1: will not override nor extend the global :include: section of the global :paths: . :(
I also can't add :test_moduleX: sections to the :include: section of the global :paths:.
I tried to having no global :path: at all and give everything in the module's :path: but then ceedling will not find any paths.
What's the proper way to get ceedling to use custom paths for test modules?
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
-
Hi,
I'm a newcomer to ceedling and I mainly try to use for unit testing.
I have some modules in my project.yml where I need to override or extend some common global include search paths.
I have tried this:
However, the
:include:
section of:test_module1:
will not override nor extend the global:include:
section of the global:paths:
. :(I also can't add
:test_moduleX:
sections to the :include: section of the global:paths:
.I tried to having no global
:path:
at all and give everything in the module's:path:
but then ceedling will not find any paths.What's the proper way to get ceedling to use custom paths for test modules?
Thanks in advance for any suggestions!
Beta Was this translation helpful? Give feedback.
All reactions