Does the feature exist in the most recent commit?
no
Why do we need this feature?
Readability when filters get extremely long/ when the output contains uninteresting information
Describe the proposal.
Currently, gtest output is either completely enabled or disabled via --gtest_brief. This also includes the "Note: ..." outputs in PrettyUnitTestResultPrinter::OnTestIterationStart (e.g. "Note: Randomizing tests' orders with a seed of x"). It would be great, if you could enable/disable these outputs individually, e.g. disable the filter output or the seed output.
This is primarily aimed at the filter output - filter strings can get very long and spam dozens or hundreds of lines in the console, disabling it would be great for visibility. Just as an example, I've added a console flag that collects all previously run tests and forbids them via filter, so that only newly added tests run. However, at 7k tests in the project, the filter string is incredibly long, since it contains every single name of these 7k tests.
I don't think this modification must be available from the console via flags, imo it'd be sufficient if a developer was able to modify the UnitTest instance somehow to enable/disable these outputs.
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?
Readability when filters get extremely long/ when the output contains uninteresting information
Describe the proposal.
Currently, gtest output is either completely enabled or disabled via
--gtest_brief. This also includes the "Note: ..." outputs inPrettyUnitTestResultPrinter::OnTestIterationStart(e.g. "Note: Randomizing tests' orders with a seed of x"). It would be great, if you could enable/disable these outputs individually, e.g. disable the filter output or the seed output.This is primarily aimed at the filter output - filter strings can get very long and spam dozens or hundreds of lines in the console, disabling it would be great for visibility. Just as an example, I've added a console flag that collects all previously run tests and forbids them via filter, so that only newly added tests run. However, at 7k tests in the project, the filter string is incredibly long, since it contains every single name of these 7k tests.
I don't think this modification must be available from the console via flags, imo it'd be sufficient if a developer was able to modify the
UnitTestinstance somehow to enable/disable these outputs.Is the feature specific to an operating system, compiler, or build system version?
no