Description
What kind of issue is this?
-
Question.
This issue tracker is not the place for questions. If you want to ask how to do something,
or to understand why something isn't working the way you expect it to,
use Community Forums or Premium Support -
PlatformIO IDE.
All issues related to PlatformIO IDE should be reported to the
PlatformIO IDE for VSCode repository -
Development Platform or Board.
All issues (building, uploading, adding new boards, etc.) related to PlatformIO development platforms
should be reported to appropriate repository related to your hardware
https://github.com/topics/platformio-platform -
Feature Request.
Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small. -
PlatformIO Core.
If you’ve found a bug, please provide an information below.
You can erase any parts of this template not applicable to your Issue.
Let's say I develop a library with 15 .cpp files. I place all the files in a single lib/x/src directory and everything is compact, simple, and easy to follow. Now I want to unit test these and platform requires that I should place each of the 15 test_xxxx.cpp in a separate directory. This has several drawbacks:
- Unnecessary complexity of the testing directory and burden to the users.
- No clear correlation between the production code structure and the test code structure.
- Difficult to tell which production files have a test and which ones are not.
- No clear place to put testing utilities that are shared by multiple tests.
Request: Please allow to have multiple test_xxxx.cpp files in test directories. When building a specific test, compile the relevant test_xxxx file and exclude the other ones. This will simplify to your users the process of writing tests and will improve the user experience.