Use ScopedTaskEnvironment instead of MessageLoop in mojo unit tests.

ScopedTaskEnvironment allows usage of ThreadTaskRunnerHandle and
base/task_scheduler/post_task.h within its scope. It should be
instantiated in every unit test that uses either of these APIs
(i.e. no test should instantiate a MessageLoop directly).

Motivation for ScopedTaskEnvironment can be found in:
https://docs.google.com/document/d/1QabRo8c7D9LsYY3cEcaPQbOCLo8Tu-6VLykYXyl3Pkk/edit

BUG=708584
R=gab@chromium.org
TBR=jam@chromium.org

Review-Url: https://codereview.chromium.org/2799043002
Cr-Commit-Position: refs/heads/master@{#462493}


CrOS-Libchrome-Original-Commit: 6e08ad229b41423e347d43c6ce2a3c46a7715976
1 file changed
tree: 47b24c5c38198d432db6a204c14be50014e834ec
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/