Add autofill metrics to dig into the failure case.

Add autofill metrics to dig into the failure case.

BUG=none
TEST=unit_tests --gtest_filter=AutoFillMetricsTest.QualityMetricsForFailure

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=71282

[Ilya Sherman, 2010-12-23 23:28:44]

I noticed while working on this patch that the test output is completely
unreadable when the test fails: googlemock likes to print every candidate
expectation that doesn't match, and ends up spewing hundreds of lines to the
console.  This is still a problem when testing as few as three cases (rather
than the full 9 being tested now).  Any suggestions on how to rein in
googlemock's spew?

[vadimb, 2010-12-23 23:48:59]

Did you try flags from "Controlling How Much Information gMock Prints"
section from GMockCookBook?



On Thu, Dec 23, 2010 at 3:28 PM, <isherman@chromium.org> wrote:

> I noticed while working on this patch that the test output is completely
> unreadable when the test fails: googlemock likes to print every candidate
> expectation that doesn't match, and ends up spewing hundreds of lines to
> the
> console.  This is still a problem when testing as few as three cases
> (rather
> than the full 9 being tested now).  Any suggestions on how to rein in
> googlemock's spew?
>
> http://codereview.chromium.org/5963004/
>

[Ilya Sherman, 2011-01-11 00:11:51]

On 2010/12/23 23:48:59, vadimb wrote:
> Did you try flags from "Controlling How Much Information gMock Prints"
> section from GMockCookBook?

Just tried this.  Alas, even at "error" verbosity level, there is a painful
amount of log spew.

[dhollowa, 2011-01-11 01:21:38]

LGTM.  Though I notice some integration conflicts, looks like the trunk has
evolved since this was posted.