Thanks. The last one is believe it or not, not an issue because the tool that consumes this understands $(Configuration).
Taking a step back though, is there a different solution to my problem? The context here is that we have our own internal testing infrastructure (we don’t use ctest). There are various reasons for this, which I can go into if you’re interested, but the TL;DR is that we have something similar to ctest, but not ctest.
It needs to know about every executable which we designate as a test executable, so we auto-generate this manifest file that the tool then consumes when it’s time to run the test. The basic algorithm is simple. It just iterates every executable which was designated as a test executable, and for each one writes a json blob to a single global file that contains information the program needs in order to run all of the tests.