The custom progress reporter gets invoked via ginkgo.ReportAfterEach after each test. The problem was that the e2e framework unconditionally enables Ginkgo's -progress output which shows execution of all nodes, including this ReportAfterEach. The effect were over 1000 lines of useless output at the start of a test run while skipping disabled tests. The solution is to tell Ginkgo that the ReportAfterEach isn't meant to be reported.
5.4 KiB
5.4 KiB