-
-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable unit tests - ignore a test/
directory in an Arduino library
#990
Comments
Hi @ianfixes , |
I don't require any UI interaction. I think I'm almost better off if the IDE completely ignores the contents of That said, if you do want to consider using But the answer to your question is (TL;DR) just introduce |
I think what is being requested is for some text to be added to the library specification:
Then ensure that the Arduino IDE complies with the specification by ignoring that folder. As far as I know, it will almost do so already. The only exception is that any sketches under the tests folder will be listed under the File > Examples > {library name} > tests. Even without specifically incorporating the
In fact that behavior already violates the specification when sketches are placed under the |
Yes, this suggested text looks perfect! I'm not sure if this would cause a related issue where the IDE would try to pull in |
As the If there is any great objection to calling the directory |
Opened #1125 |
Background
I've developed a system called
arduino_ci
that enables Arduino libraries to be unit tested, both locally and remotely (as part of a service like Travis CI). Among other things, this includes abilities such asmillis()
, pin inputs likedigitalRead()
, serial inputs, etc)Problem
The trick is where (in the library) to put the files that contain the tests. According to the specification:
I would prefer not to put tests in "extras/", both for closer proximity to the code begin tested and because (in my opinion) the ability to run tests is an important and necessary part of any software project. (Similar to how they are organized in modules for Java, Python, NodeJS, etc.)
Question
What chance is there of amending the library specification to ignore (whether that means whitelisting or blacklisting in this context) a directory called "test/" where all the automated tests would live? Alternately, could something similar to
.gitignore
be used for that purpose?See Also:
The text was updated successfully, but these errors were encountered: