Initialize CommandLine for JUnit4 Tests

In JUnit3, CommandLine is initialized before a test run, we should do
the same to avoid test flakiness.

Bug: 640116
Change-Id: If9ac3945680060125cfc86b63cf79a91e21d13dc
Reviewed-on: https://chromium-review.googlesource.com/685811
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Yoland Yan <yolandyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#505868}

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