base: Use TEST() macro when possible.

There is no need to inherit from testing::Test and then have to use TEST_F(),
if you aren't overridding SetUp() or TearDow(). So if you don't need to customize
it, you can use TEST() macro directly and it does that for us automagically.

Fix all the cases found with the following command line:

$ git grep -n1 "public testing::Test" base/ | grep "};"

TEST=base_unittests
R=willchan@chromium.org

Review URL: https://codereview.chromium.org/11308261

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170747 0039d316-1c4b-4281-b951-d872f2087c98


CrOS-Libchrome-Original-Commit: 35dabb168a48a717d9ba0ecabff33295abf9f073
7 files changed
tree: 22cd72514f3f48647a8d0768d3980acb590696d1
  1. base/
  2. build/
  3. dbus/
  4. ipc/
  5. testing/
  6. third_party/