Improve MongoDriverRecoveryTest

Author: prdoyle

bosk-mongo/src/test/java/works/bosk/drivers/mongo/internal/MongoDriverRecoveryTest.java

@@ -102,6 +102,7 @@ enum FlushOrWait {
 	}
 
 
+	@Slow // Takes 14*timescale for FLUSH and 44*timescale for WAIT
 	@InjectedTest
 	@DisruptsMongoProxy
 	void initialOutage_recovers() throws InvalidTypeException, InterruptedException, IOException {
@@ -114,6 +115,7 @@ void initialOutage_recovers() throws InvalidTypeException, InterruptedException,
 
 		LOGGER.debug("Create a new bosk that can't connect");
 		Bosk<TestEntity> bosk = new Bosk<>(getClass().getSimpleName() + boskCounter.incrementAndGet(), TestEntity.class, AbstractMongoDriverTest::initialRoot, BoskConfig.<TestEntity>builder().driverFactory(driverFactory).build());
+		LOGGER.debug("Done creating bosk");
 
 		MongoDriverSpecialTest.Refs refs = bosk.buildReferences(MongoDriverSpecialTest.Refs.class);
 		BoskDriver driver = bosk.driver();
@@ -133,7 +135,9 @@ void initialOutage_recovers() throws InvalidTypeException, InterruptedException,
 		LOGGER.debug("Restore mongo connection");
 		mongoService.restoreConnection();
 
-		LOGGER.debug("Flush and check that the state updates");
+		LOGGER.debug("Wait and check that the state updates");
+		// With FLUSH this succeeds almost immediately.
+		// With WAIT it is artificially delayed.
 		waitFor(driver);
 		try (var _ = bosk.readContext()) {
 			assertEquals(initialState, bosk.rootReference().value(),
@@ -160,13 +164,16 @@ private void waitFor(BoskDriver driver) throws IOException, InterruptedException
 				break;
 			case WAIT:
 				// The user really has no business expecting updates to occur promptly.
-				// Let's wait several times the timescale so that the test
-				// can set a short timescale to make FLUSH fast without risking
-				// failures in the WAIT tests.
+				// Because this is sometimes used when the bosk is (deliberately)
+				// malfunctioning, we should wait much longer than the recovery time,
+				// which (as I write this) is 5*timescale.
 				//
 				// Unfortunately, this makes these tests inevitably slow.
 				//
-				Thread.sleep(10L * driverSettings.timescaleMS());
+				long sleepTime = 10L * driverSettings.timescaleMS();
+				LOGGER.debug("Waiting for {} ms", sleepTime);
+				Thread.sleep(sleepTime);
+				LOGGER.debug("...done waiting");
 				break;
 		}
 	}