I suspect I would need to do this each time I run mbed test and undo each time I want to compile. I look forward to support for nested tests, however unfortunately it won't land in time for me to take advantage of it on this project

Do you know if it's possible to set a flag/preprocessor directive from the command line when running tests, then it would be possible to chop main out with directives

Nice idea :) will have to look at how we hook main across different tools and libraries to see how that works

I did some digging of my own and found that there is an undocumented feature where mbed test will accept a -D argument like so: mbed test -t GCC_ARM -m LPC1768 -DMBED_TESTSUITE=1 . With this in mind, I simply wrapped my main() function in #ifndef MBED_TESTSUITE .... #endif and was able to correct the whole issue rather painlessly. This might be a good workaround to put on the wiki.

Just now having the issue that mbed test passes all arguments across to mbedgt/greentea and it doesn't recognize the -D, so I can build the test suite but the automatic runner is not working.

For anyone digging this thread up later, I fixed this by creating a batch file like follows. If all your tests are named like myprefix-somegroup-sometest then tests-myprefix will distinguish them from the massive mbed test suite when running tests. The wildcard seems to be another undocumented feature. The separate compile and run are necessary because the mbed running tool errors out if you pass it -D which seems to happen for some reason with the MBED_TESTSUITE macro which is intended to nop out the main() function in main.cpp. The file touches main.cpp each time just to make sure it is rebuilt

#!/bin/sh
RED='\033[0;31m'
NC='\033[0m'

touch main.cpp
OPTIONS='-n tests-myprefix* -t GCC_ARM -m LPC1768'

printf "${RED}⇒ Building testsuite${NC}\n"
mbed test --compile ${OPTIONS} -DMBED_TESTSUITE=1

printf "\n${RED}⇒ Running testsuite${NC}\n"
mbed test --run ${OPTIONS}