Does the feature exist in the most recent commit?
No
Why do we need this feature?
The "Uninteresting mock function call" warnings are useful when your test is not doing what you expect.
However, if you want to read your own extra output from the tests, this can clutter the output a lot.
This makes reading your own output close to impossible.
Another use-case is when running the gtest on repeat, where you are not interested in this information.
Describe the proposal.
Add the value "ignore" to --gmock_verbose=ignore to not get the warning printed, such that the output is more clean to read.
Is the feature specific to an operating system, compiler, or build system version?
No
Does the feature exist in the most recent commit?
No
Why do we need this feature?
The "Uninteresting mock function call" warnings are useful when your test is not doing what you expect.
However, if you want to read your own extra output from the tests, this can clutter the output a lot.
This makes reading your own output close to impossible.
Another use-case is when running the gtest on repeat, where you are not interested in this information.
Describe the proposal.
Add the value "ignore" to --gmock_verbose=ignore to not get the warning printed, such that the output is more clean to read.
Is the feature specific to an operating system, compiler, or build system version?
No