Testing asynchronous systems is hard. Not only does it require handling threads, timeouts and concurrency issues, but the intent of the test code can be obscured by all these details. Awaitility is a DSL that allows you to express expectations of an asynchronous system in a concise and easy to read manner. For example:
@Test
public void updatesCustomerStatus() {
// Publish an asynchronous message to a broker (e.g. RabbitMQ):
messageBroker.publishMessage(updateCustomerStatusMessage);
// Awaitility lets you wait until the asynchronous operation completes:
await().atMost(5, SECONDS).until(customerStatusIsUpdated());
...
}
See getting starting and usage guide for more info.
News
News
- 2020-05-19: Awaitility
4.0.3is released. This release includes updates to ConditionEvaluationLogger as well as several depdency updates. If you’re using the Groovy DSL beaware that Groovy has been upgraded from 2.x to 3.x. See changelog for details. - 2020-01-03: Awaitility
4.0.2is released. This release includes support for asserting that a condition is maintained for specific duration, improvments to ConditionEvaluationListener as well as several bug fixes and other improvements. See changelog for details. - 2019-09-06: Awaitility
4.0.1is released and it fixes a regression issue in which the condition evaluation duration could be evaluated to a negative number of nanoseconds on Windows. It also drops the dependency to objenesis since it’s no longer used after moving to Java 8. See changelog for details.
Release Notes
Docs
Documentation
Who
Who
Awaitility is developed and maintained by Johan Haleby with the help of numerous other contributors over the years. Would you like to contribute to the project in any way? Submit a pull request or contact Johan at Twitter.
Johan started the project with Jan Kronquist when they were both working at Jayway back in January of 2010. The project is now sponsored by Parkster.
