The good news is that if you have an fdbserver, whether you built it from source or not, and you are in the source directory, you can run a particular simulation test by just typing something like
bin/fdbserver -r simulation -f tests/fast/Sideband.txt -s 12345
and among other junk it will print out something like
1 tests passed; 0 tests failed; waiting for DD to end…
Unseed: 81362
Elapsed: 118.350939 simsec, 6.486105 real seconds
The bad news is that I don’t think you can really trust that “1 tests passed” business. To trust that a test passed without errors you also need to examine the megabytes of XML log file that it has spit out. Unfortunately, it doesn’t look like the tools for doing that (let alone the tools for diagnosing failed runs, or for running millions of these tests and examining the ensemble of results) have been released, so it might be rough on community developers until we can build some tooling and/or give fdbserver itself some of the key functionality.
Apple folks, do you have a plan for this? Or can you start by taking a look at your tools and tell us what they currently check to determine if a simulation test is successful?