I'm going to try to put this into a junit test over the weekend. It can run really long or really short. I'm thinking of providing three methods, one that runs all the time and takes 30 seconds? a minute? Label it as "slow" either way.
A nightly that runs for 10 minutes
A weekly that runs for an hour
The background here is that I see issues after 1-2 hours running on my machine, occasionally as little as 30 minutes. I suppose if it runs more often it'd have a better chance of hitting at shorter intervals. I'm open to suggestions, so let me know.... I really don't have a sense of how onerous a really long-running test would be....
When I mentioned "prior art" it was mostly a shorthand to myself that there seemed to be code I could use as a model in TestReplicationHandler in terms of starting up servers and all that rot. But I'll look at JettySolrRunner as you indicated, thanks for the pointer.