expectNoEvents() does not account for terminal events

[saket]

When using expectNoEvents(), the method does consider that the flow's terminal event might have already been consumed.

flowOf("foo").test {
  skipItems(1)
  awaitComplete()
  expectNoEvents()
}

The above code produces this error:

TurbineAssertionError: Expected no events but found Complete

Additionally, it is currently possible to call awaitComplete() multiple times without any restriction. Should this be allowed?

flowOf("foo").test {
  skipItems(1)
  repeat(5) {
    awaitComplete()
  }
}

[JakeWharton]

So I don't forget:

[JakeWharton]

We can't really stop you from calling awaitComplete multiple times. We could have it return Nothing and throw some special internal exception that we catch in test { } and then return normally? But I'd kinda just rather let you do this and get the failure...