base: Use TEST() macro when possible.

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

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=170747

[tfarina, 2012-11-29 20:32:12]

Hi Mark, could you check if this is OK?

Thank you,

[tfarina, 2012-11-30 23:52:48]

fiendly ping?

Brett, if you can, could you take a look at this?

Thank you!

[willchan no longer on Chromium, 2012-12-02 23:14:13]

lgtm

[commit-bot: I haz the power, 2012-12-02 23:14:19]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tfarina@chromium.org/11308261/4001

[commit-bot: I haz the power, 2012-12-03 01:03:25]

Sorry for I got bad news for ya.
Compile failed with a clobber build on win_rel.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...
Your code is likely broken or HEAD is junk. Please ensure your
code is not broken then alert the build sheriffs.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2012-12-03 14:10:56]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tfarina@chromium.org/11308261/4001

[commit-bot: I haz the power, 2012-12-03 15:59:16]

Retried try job too often on linux_rel for step(s) ash_unittests

[commit-bot: I haz the power, 2012-12-03 16:01:02]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tfarina@chromium.org/11308261/4001

[commit-bot: I haz the power, 2012-12-03 16:42:40]

Retried try job too often on linux_rel for step(s) ash_unittests