Update dependency org.awaitility:awaitility to v4.3.0#96
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Update dependency org.awaitility:awaitility to v4.3.0#96renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
1eb9120 to
fb39ab9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
4.2.1→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.2Configuration
📅 Schedule: Branch creation - "after 1pm every weekday" in timezone Europe/Bucharest, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.