From 617f2132fedf74b1e5861fec9d6dd9eda49ef9c0 Mon Sep 17 00:00:00 2001 From: Patrick Ohly Date: Mon, 13 Nov 2023 08:08:09 +0100 Subject: [PATCH] e2e: avoid redundant labels in JUnit file Because labels are currently typically added also to the spec texts, we don't need to write them separately. This redundancy got introduced in f2cfbf44b1 when registering all inline tags also as labels. --- test/e2e/framework/internal/junit/junit.go | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/test/e2e/framework/internal/junit/junit.go b/test/e2e/framework/internal/junit/junit.go index 2f61c869ce8..a33c780d5c3 100644 --- a/test/e2e/framework/internal/junit/junit.go +++ b/test/e2e/framework/internal/junit/junit.go @@ -36,6 +36,10 @@ func WriteJUnitReport(report ginkgo.Report, filename string) error { // both, then tools like kettle and spyglass would concatenate // the two strings and thus show duplicated information. OmitFailureMessageAttr: true, + + // All labels are also part of the spec texts in inline [] tags, + // so we don't need to write them separately. + OmitSpecLabels: true, } return reporters.GenerateJUnitReportWithConfig(report, filename, config)