Okay,
let's say I use a new feature branch for my new feature (of course). There I will still have to put my testing code somewhere. Probably this will not be any code which can be tested using the unit test, because it's hardware dependent for example. In order to test my code I would write a file containing a main function. And because the development of this specific feature would take some time, I would be glad to save it in the git branch.
1. I can't place it, where the rest of the code belongs. (It's not a part of the lib) 2. I can't place it, in a test folder (these are reserved for the unit tests) 3. I can't place it in an example folder, because it does not belong there.
So you still have not answered, where the place to put this kind of code would be.
Thorsten
On 01.08.2013 23:30, Niklas Hauser wrote:
Hi,
there should be a place for saving code for testing purposes.
We have `scons check` which compiles everything in xpcc/examples. The idea is to move this to xpcc/release to test periodically in a CI environment.
At the moment testing examples are misused for this kind of code, because there simply is no other place to put this code. A top-Level sandbox folder would be nice.
No sandbox folder. We already have enough top-level folders. Do not commit half finished code as *examples*. Use a branch and make the code work, then write a nice example about it.
Niklas _______________________________________________ xpcc-dev mailing list xpcc-dev@lists.rwth-aachen.de http://mailman.rwth-aachen.de/mailman/listinfo/xpcc-dev