[JonChesterfield]

One approach is to build test traversal machinery out of function static variables and have every TEST() macro turn into a function that takes a pointer to some state controlling which test to run next.

You don't need malloc if using local variables either, which is helpful when your target doesn't have malloc or when debugging memory problems on targets that do. It's nice to know the test framework cannot be leaking or use-after-free anything.

[ant6n]

Interesting. But how would one test "know" about the next one, especially if they are in different compilation units.

[JonChesterfield]

Discovery is at runtime. Syntax goes something like MODULE(foo) { DEPENDS(bar); TEST("I like string names") { CHECK(42 == life()); } } where DEPENDS either sends control flow off to bar or onwards towards the test case depending on the value of an argument to the function MODULE created.