gtest: The "new" output is too distracting and can be improved
Maybe this works great for smaller test suits, but I have like 157 tests in one executable and the "new" format (I do not know since which version it is) is way harder to decipher than the previous:
/test/name OK
How the end fo the test look like can be seen below. it contains some debug prints from WebKitGTK too, but I'm used to those. I'm more unhappy of the GLib-DEBUG
lines and those Start/End of xxx
. The -q
argument doesn't seem to cause any change.
Also, when you know that there are 157 tests, why do you not print the summary of the test run, please? How can one pass a test failure you ask? Just use --keep-going
argument for the test program. Such statistics are common in other tools, more important than GLib-DEBUG messages.
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 139 /bug/772513
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 140 /bug/772918
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 141 /bug/773164
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 142 /bug/775042
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 143 /bug/775691
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 144 /bug/779707
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 145 /bug/780275-html
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 146 /bug/780275-plain
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 147 /bug/781722
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 148 /bug/781116
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 149 /bug/780088
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 150 /bug/788829
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 151 /bug/750636
# End of bug tests
# Start of issue tests
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 152 /issue/86
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 153 /issue/103
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 154 /issue/104
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 155 /issue/107
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 156 /issue/884
# GLib-DEBUG: posix_spawn avoided (child_setup specified)
Warning: disabling gigacage because GIGACAGE_ENABLED=0!
ok 157 /issue/783
# End of issue tests
These are only results of the last 19 tests. Imagine to check the result of all 157 tests. It's not good for my eyes. Unless the test failure has a lengthy message about the cause of the failure it's very easy to overlook that the test failed.