[GTTF] Miscellanous UI tests cleanups:

[GTTF] Miscellanous UI tests cleanups:

- use built-in timeouts instead of "inventing" them in each test case
- avoid unneeded checks and operations
- use automation calls more effectively
- use FLAKY mark instead of DISABLED to maintain test coverage
- split some tests to make the above possible

TEST=UI test based
BUG=39785
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=43070

[brettw, 2010-03-29 16:59:54]

LGTM

http://codereview.chromium.org/1547003/diff/1/5
File chrome/browser/process_singleton_win_uitest.cc (right):

http://codereview.chromium.org/1547003/diff/1/5#newcode94
chrome/browser/process_singleton_win_uitest.cc:94: int timeout_ms_;
Technically member data should go below the functions, so put this below the
destructor.

[Nicolas Sylvain, 2010-03-29 22:54:29]

lgtm

http://codereview.chromium.org/1547003/diff/1/13
File chrome/test/ui/history_uitest.cc (right):

http://codereview.chromium.org/1547003/diff/1/13#newcode47
chrome/test/ui/history_uitest.cc:47: TEST_F(HistoryTester,
DISABLED_VerifyHistoryLength2) {
is there a bug number? Can we write it there?