Option two needs more than that:
It needs plugins to be able to force chunks to simulate (normally chunks don't simulate if they have zero players in them).
On the other hand, there's no need for an assert failure, the plugins could either crash the server (yes, it is possible quite simply) or emit a specific message in the log, then stop the server, and the test driver script could look for that output message. Or create a file in case of failure. Anything that the test driver can detect easily.
And we need a way for the external test driver to enable the testing plugins - perhaps feed a "load TestPlugin" through the stdin?
It needs plugins to be able to force chunks to simulate (normally chunks don't simulate if they have zero players in them).
On the other hand, there's no need for an assert failure, the plugins could either crash the server (yes, it is possible quite simply) or emit a specific message in the log, then stop the server, and the test driver script could look for that output message. Or create a file in case of failure. Anything that the test driver can detect easily.
And we need a way for the external test driver to enable the testing plugins - perhaps feed a "load TestPlugin" through the stdin?