Skip to content

Conversation

@pm47
Copy link
Member

@pm47 pm47 commented Jun 3, 2021

With the move to akka typed, we will be using more and more
scalatest's eventually as a replacement for akka's awaitCond
(which isn't available in testkit.typed).

But there is a catch:

  • awaitCond expects a boolean
  • eventually expects a non-failure

Which means that we must use eventually(assert(cond)), and not
eventually(cond).

With the move to akka _typed_, we will be using more and more
scalatest's `eventually` as a replacement for akka's `awaitCond`
(which isn't available in `testkit.typed`).

But there is a catch:
- `awaitCond` expects a boolean
- `eventually` expects a non-failure

Which means that we must use `eventually(assert(cond))`, and not
`eventually(cond)`.
Copy link
Member

@t-bast t-bast left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, we need to get used to that change in behavior

@pm47 pm47 merged commit bd6bad1 into master Jun 7, 2021
@pm47 pm47 deleted the fix-eventually branch June 7, 2021 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants