fix(deps): update dependency org.awaitility:awaitility to v4.3.0 #708
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot].This notice will be removed on 2025-10-07.
This PR contains the following updates:
4.0.3->4.3.0Release Notes
awaitility/awaitility (org.awaitility:awaitility)
v4.3.0Support for kotlin.time.Duration in Kotlin DSL (thanks to Ivo Šmíd for PR)
Upgraded kotlin version in the awaitility-kotlin module to 2.1.10
Using a more descriptive error message when using VERY long wait conditions or poll durations (issue 290)
Added an overloaded method of untilAsserted(..) that takes a supplier and a consumer. For example, lets say you have a class like this:
public class MyClass {
public String myFunction() {
// Imagine stuff being executed in asynchronously here and the result of this
// operation is a string called "my value"
return "my value"
}
}
// Then in your test you can wait for the "myFunction" to be asserted by a "consumer" that uses
// assertj to make sure that "myFunction" returns ""my value"
await().untilAsserted(myClass::myFunction, value -> Assertions.assertThat(value).isEqualTo("my value"));
This has also been implemented for all atomic, adder, and accumulator methods.
v4.2.2v4.2.1Upgraded Kotlin to 1.9.22
Added extension properties forever, then, and, given to the Kotlin extension. This allows you to do e.g.:
await.forever until { .. }
Added shortcut for enabling logging. Before you had to do e.g.
await()
.with()
.conditionEvaluationListener(new ConditionEvaluationLogger(log::info))
.pollInterval(ONE_HUNDRED_MILLISECONDS)
.until(logs::size, is(4));
You can now instead use the "logging" shortcut:
await()
.with()
.logging(log::info)
.pollInterval(ONE_HUNDRED_MILLISECONDS)
.until(logs::size, is(4));
or simply ".logging()" for "System.out".
This shortcut has also been added globally:
Awaitility.setLogging(log::info);
or
Awaitility.setDefaultLogging();
Improved lambda detection for Java 17 and Java 21
Upgraded Groovy to 4.0.19
v4.2.0Fixed a bug in the shutdown behavior of a polling thread. The wrong time unit was used causing executor shutdown to take way more time than expected in cases where it's stuck. Thanks to Claus Näveke for spotting this and for the initial PR.
Fixed a bug in which condition was not evaluated correctly with small intervals, such as:
await().atMost(Duration.ofMillis(10)).pollInterval(Duration.ofMillis(5)).until(..);
(issue 224). Thanks to Robby Decosemaeker for PR.
Upgraded the awaitility-kotlin module to use kotlin 1.6.10
Fail fast conditions can now be specified with assertions. For example:
await().failFast(() -> assertThat(state).isNotEqualTo("Failed")).until(..);
(issue 238)
v4.1.1v4.1.0Upgraded to Scala from 2.13.3 to 2.13.5 (thanks to sullis for pull request)
Upgraded Kotlin from 1.3.72 to 1.5.0
Added support for fail-fast conditions. This is a special condition that, if fulfilled, will throw a "org.awaitility.core.TerminalFailureException" immediately, thus failing the test.
This is good when you have a condition that you know beforehand should never be fulfilled. So instead of waiting the full duration of a normal condition evaluation period, the test will fail
faster if this (fail fast) condition evaluates to true. For example:
await().timeout(Duration.ofSeconds(5)).failFast(() -> orders.findById(1234).state == PAID).until(() -> orders.findById(1234).state == CLOSED);
This will fail-fast if the state of order 1234 is ever equal to "PAID" during the 5 second evaluation of the condition specified in "until".
(Thanks to Antony Stubbs for initial pull request) (issue 178)
Upgraded Groovy from version 3.0.4 to 3.0.8
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.