Re: Is it possible to have write NonBlocking Junit tests

According to general logic:
You can't access and verify a result, that was not yet produced. :-)
So you will always have to wait, until the result you want to verify, was
produced.
If you have sequential unit tests, you "automatically block" your unit
test, while you call a method/methods that produce the result you want to
verify.
When the method you call in your test produces the result asynchronously,
you'll somehow have to block and wait until the result was produced.
So the only leverage you have is to wait as little as possible.

BTW: Should you find a way to verify a result that was not yet produced,
please let us know, since that could speed up all our tests quite a bit...
;-)

Greetings,
   Malte