I'll chime in here, with my (probably limited) understanding. By passing false to ConfigureAwait, we tell the task that we don't need to return to the the thread/sync context that we were in when executing the rest of the async task. This means that it can be executed on any thread in the threadpool. For a unit testing framework, that seems like the right call, though I could see how async stuff related to UI might at some point need the option of modifying that parameter. I believe that  `await setupAction();` is equivalent to `await setupAction().ConfigureAwait(true)`. @dpbackes can probably correct any of what I just said if it's off base...