JUnit and Latches

Question

// improving the description as requested //

The code works fine as it is below. But if I move one assert(Latch) from testA to testB; the assertion fails. No matter how much delay I give it.

Also I did this experiment: if I create a new latch and let one of the @Test methods count it down, the other @Test method does not see it counted down!

The @FixMethodOrder did not help.

I am trying to split the test in different methods, but I also need to keep some synchronization because of the connection to the client that is shared and also sequence of events.

thanks

@FixMethodOrder(MethodSorters.NAME_ASCENDING)
public class IBClientTest implements XStrategy {

private XBroker broker = new IBXClientC();
private final CountDownLatch connectedClient = new CountDownLatch(1);
private final CountDownLatch receivedTICK = new CountDownLatch(1);


@Test
public void testA() throws InterruptedException {

    broker.connect();
    broker.startStrategy(this);
    assertTrue(connectedClient.await(2, TimeUnit.SECONDS));
    assertTrue(broker.isConnected());

    XInstrument instr1 = XInstrument.fromString("EUR/USD");
    XInstrument instr2 = XInstrument.fromString("GBP/USD");
    Set<XInstrument> set = new HashSet<>();
    set.add(instr2);
    set.add(instr1);
    broker.subscribeToInstruments(set);

    assertTrue(receivedTICK.await(2, TimeUnit.SECONDS));

    broker.disconnect();

}

@Test
public void testB() throws InterruptedException {

}

// invoked by broker
@Override
public void onStart(XBroker broker) {

    connectedClient.countDown();
}

@Override
public void onStop() {
}

// invoked by broker
@Override
public void onTick(XInstrument instrument, XTick tick) {

    receivedTICK.countDown();

}

please provide declaration of latches and code where they are counting down. Also provide environment settings: do tests run in multi-threaded mode? — ADS, Mar 22 '18 at 07:59

luide · Accepted Answer · 2018-03-23T07:19:54.117

0

I think I found the answer myself:

JUnit runs each test in a separate instance of the test class. Hence the variable (latches) are not shared between tests.

JUnit is designed to work best with a number of small tests. It executes each test within a separate instance of the test class.

edited Mar 23 '18 at 07:19

answered Mar 23 '18 at 07:08

luide

37
6

JUnit and Latches

1 Answers1