Coroutines are great. They allow us to write asynchronous code as if they were synchronous. It lets us avoid callback hell, transform our data easily, thread switching, etc. It’s a pretty sweet deal.

Testing it however, may not be so straightforward from the get go. You may find your data is returning nulls, or it might seem your coroutines aren’t even executing at all.

But once you figure out why, testing coroutines becomes as simple as using them. All you need to do is apply a few basic rules (no pun intended).

Check out this post to find out just what those rules are and how you can turn into a coroutine testing master in just a few minutes.