ConcurrentUnit
A simple, zero-dependency toolkit for testing multi-threaded code. Supports Java 1.6+.
Introduction
ConcurrentUnit was created to help developers test multi-threaded or asynchronous code. It allows you to perform assertions and wait for operations in any thread, with failures being properly reported back to the main test thread. If an assertion fails, your test fails, regardless of which thread the assertion came from.
Usage
- Create a
Waiter - Use
Waiter.awaitto block the main test thread. - Use the
Waiter.assertcalls from any thread to perform assertions. - Once expected assertions are completed, use
Waiter.resumecall to unblock theawaiting thread.
When your test runs, assertion failures will result in the main thread being interrupted and the failure thrown. If an await call times out before all expected resume calls occur, the test will fail with a TimeoutException.
Examples
Consider a test for a message bus that delivers messages asynchronously:
@Test
public void shouldDeliverMessage() throws Throwable {
final Waiter waiter = new Waiter();
messageBus.registerHandler(message -> {
// Called on separate thread
waiter.assertEquals(message, "foo");
waiter.resume();
};
messageBus.send("foo");
// Wait for resume() to be called
waiter.await(1000);
}
We can also handle wait for multiple resume calls:
@Test
public void shouldDeliverMessages() throws Throwable {
final Waiter waiter = new Waiter();
messageBus.registerHandler(message -> {
waiter.assertEquals(message, "foo");
waiter.resume();
};
messageBus.send("foo");
messageBus.send("foo");
messageBus.send("foo");
// Wait for resume() to be called 3 times
waiter.await(1000, 3);
}
If an assertion fails in any thread, the test will fail as expected:
@Test(expected = AssertionError.class)
public void shouldFail() throws Throwable {
final Waiter waiter = new Waiter();
new Thread(() -> {
waiter.assertTrue(false);
}).start();
waiter.await();
}
TimeoutException is thrown if resume is not called before the await time is exceeded:
@Test(expected = TimeoutException.class)
public void shouldTimeout() throws Throwable {
new Waiter().await(1);
}
Alternatively
As a more concise alternative to using the Waiter class, you can extend the ConcurrentTestCase:
class SomeTest extends ConcurrentTestCase {
@Test
public void shouldSucceed() throws Throwable {
new Thread(() -> {
doSomeWork();
threadAssertTrue(true);
resume();
}).start();
await(1000);
}
}
Assertions
ConcurrentUnit's Waiter supports the standard assertions along with Hamcrest Matcher assertions:
waiter.assertEquals(expected, result);
waiter.assertThat(result, is(equalTo(expected)));
Since Hamcrest is an optional dependency, users need to explicitly add it to their classpath (via Maven/Gradle/etc).
Other Examples
More example usages can be found in the WaiterTest or in the following projects:
Additional Notes
On await / resume Timing
Since it is not always possible to ensure that resume is called after await in multi-threaded tests, ConcurrentUnit allows them to be called in either order. If resume is called before await, the resume calls are recorded and await will return immediately if the expected number of resumes have already occurred. This ability comes with a caveat though: it is not possible to detect when additional unexpected resume calls are made since ConcurrentUnit allows an await call to follow.
Additional Resources
- Javadocs
- An article describing the motivation for ConcurrentUnit
License
Copyright 2011-2016 Jonathan Halterman - Released under the Apache 2.0 license.
48 Aug 23, 2022
27 Nov 13, 2022
3.3k Dec 31, 2022
962 Dec 31, 2022
250 Sep 12, 2022
3.3k Jan 5, 2023
1.4k Dec 10, 2022
439 Dec 9, 2022
6.2k Dec 31, 2022
100 Oct 18, 2022
167 Dec 26, 2022
215 Jan 1, 2023
8.4k Jan 4, 2023
1.8k Jan 5, 2023
1.7k Jan 1, 2023
1.5k Dec 26, 2022