junit report granularity #1523

ajaggapa · 2025-03-04T11:07:26Z

ajaggapa
Mar 4, 2025

Below is my junit report. It shows duration for test (It) along with BeforeAll & JustAfterEach.
I am looking to have a junit report with more granularity which shows time taken for BeforeAll, AfterAll, AfterEach.. etc
Is there any way to get such report ?

<?xml version="1.0" encoding="UTF-8"?>
  <testsuites tests="4" disabled="0" errors="0" failures="0" time="16.962040853">
      <testsuite name="test" package="/home/testuser/tests/" tests="4" disabled="0" skipped="0" errors="0" failures="0" time="16.962040853" timestamp="2025-03-03T15:40:52">
          <properties>
            ...
          </properties>
          <testcase name="[BeforeSuite]" classname="test" status="passed" time="0.337823128">
              <system-err>
              Enter [BeforeSuite]
              ...
              Exit [BeforeSuite] 
              </system-err>
          </testcase>
          <testcase name="[It] should pass" classname="test" status="passed" time="3.607163969">
              <system-err>
              Enter [BeforeAll]
              ...
              Exit [BeforeAll] 
              Enter [It] should pass 
              ...
              Exit [It] should pass
              Enter [JustAfterEach]
              ...
              Exit [JustAfterEach] TOP-LEVEL
              </system-err>
          </testcase>
          <testcase name="[AfterSuite]" classname="test" status="passed" time="13.016693281">
              <system-err>
              Enter [AfterSuite] 
              ...
              Exit [AfterSuite] 
              </system-err>
          </testcase>
          <testcase name="[ReportAfterSuite]" classname="test" status="passed" time="0.000420509">
              <system-err>
                Enter [ReportAfterSuite]
                ...
                Exit [ReportAfterSuite]
                </system-err>
          </testcase>
      </testsuite>
  </testsuites>

Answered by onsi

Mar 5, 2025

hey @ajaggapa the junit report format is quite limited and there is not a formal junit spec that desribes how to add additional metadata.

I recommend generating Ginkgo's json output using --json-report and using that instead of or alongisde the junit output. Each spec in the JSON file includes a SpecEvents entry that looks like this (this is from one of Ginkgo's integration tests):

[
          {
            "SpecEventType": "Node",
            "CodeLocation": {
              "FileName": "/Users/onsi/code/ginkgo/integration/integration_suite_test.go",
              "LineNumber": 49
            },
            "TimelineLocation": {
              "Order": 7,
              "Time": "2025-03-05T…

View full answer

onsi · 2025-03-05T16:35:37Z

onsi
Mar 5, 2025
Maintainer

hey @ajaggapa the junit report format is quite limited and there is not a formal junit spec that desribes how to add additional metadata.

I recommend generating Ginkgo's json output using --json-report and using that instead of or alongisde the junit output. Each spec in the JSON file includes a SpecEvents entry that looks like this (this is from one of Ginkgo's integration tests):

[
          {
            "SpecEventType": "Node",
            "CodeLocation": {
              "FileName": "/Users/onsi/code/ginkgo/integration/integration_suite_test.go",
              "LineNumber": 49
            },
            "TimelineLocation": {
              "Order": 7,
              "Time": "2025-03-05T09:26:49.814826-07:00"
            },
            "Message": "TOP-LEVEL",
            "NodeType": "BeforeEach"
          },
          {
            "SpecEventType": "Node (End)",
            "CodeLocation": {
              "FileName": "/Users/onsi/code/ginkgo/integration/integration_suite_test.go",
              "LineNumber": 49
            },
            "TimelineLocation": {
              "Order": 9,
              "Time": "2025-03-05T09:26:49.814914-07:00"
            },
            "Message": "TOP-LEVEL",
            "Duration": 87542,
            "NodeType": "BeforeEach"
          },
          {
            "SpecEventType": "Node",
            "CodeLocation": {
              "FileName": "/Users/onsi/code/ginkgo/integration/precompiled_test.go",
              "LineNumber": 55
            },
            "TimelineLocation": {
              "Order": 10,
              "Time": "2025-03-05T09:26:49.815011-07:00"
            },
            "Message": "ginkgo build with custom output",
            "NodeType": "BeforeEach"
          },
          {
            "SpecEventType": "Node (End)",
            "CodeLocation": {
              "FileName": "/Users/onsi/code/ginkgo/integration/precompiled_test.go",
              "LineNumber": 55
            },
            "TimelineLocation": {
              "Order": 12,
              "Time": "2025-03-05T09:26:49.815498-07:00"
            },
            "Message": "ginkgo build with custom output",
            "Duration": 486416,
            "NodeType": "BeforeEach"
          },
          {
            "SpecEventType": "Node",
            "CodeLocation": {
              "FileName": "/Users/onsi/code/ginkgo/integration/precompiled_test.go",
              "LineNumber": 65
            },
            "TimelineLocation": {
              "Order": 13,
              "Time": "2025-03-05T09:26:49.815613-07:00"
            },
            "Message": "should build with custom path",
            "NodeType": "It"
          },
          {
            "SpecEventType": "Node (End)",
            "CodeLocation": {
              "FileName": "/Users/onsi/code/ginkgo/integration/precompiled_test.go",
              "LineNumber": 65
            },
            "TimelineLocation": {
              "Offset": 31,
              "Order": 15,
              "Time": "2025-03-05T09:26:51.148815-07:00"
            },
            "Message": "should build with custom path",
            "Duration": 1333200083,
            "NodeType": "It"
          },
          {
            "SpecEventType": "Node",
            "CodeLocation": {
              "FileName": "/Users/onsi/code/ginkgo/integration/integration_suite_test.go",
              "LineNumber": 53
            },
            "TimelineLocation": {
              "Offset": 31,
              "Order": 16,
              "Time": "2025-03-05T09:26:51.151544-07:00"
            },
            "Message": "TOP-LEVEL",
            "NodeType": "AfterEach"
          },
          {
            "SpecEventType": "Node (End)",
            "CodeLocation": {
              "FileName": "/Users/onsi/code/ginkgo/integration/integration_suite_test.go",
              "LineNumber": 53
            },
            "TimelineLocation": {
              "Offset": 31,
              "Order": 18,
              "Time": "2025-03-05T09:26:51.15284-07:00"
            },
            "Message": "TOP-LEVEL",
            "Duration": 1296125,
            "NodeType": "AfterEach"
          },
          {
            "SpecEventType": "Node",
            "CodeLocation": {
              "FileName": "/Users/onsi/code/ginkgo/integration/precompiled_test.go",
              "LineNumber": 60
            },
            "TimelineLocation": {
              "Offset": 31,
              "Order": 19,
              "Time": "2025-03-05T09:26:51.155998-07:00"
            },
            "Message": "ginkgo build with custom output",
            "NodeType": "DeferCleanup (Each)"
          },
          {
            "SpecEventType": "Node (End)",
            "CodeLocation": {
              "FileName": "/Users/onsi/code/ginkgo/integration/precompiled_test.go",
              "LineNumber": 60
            },
            "TimelineLocation": {
              "Offset": 31,
              "Order": 21,
              "Time": "2025-03-05T09:26:51.156054-07:00"
            },
            "Message": "ginkgo build with custom output",
            "Duration": 55625,
            "NodeType": "DeferCleanup (Each)"
          }
        ]

As you can see it includes timestamps for each event and durations (in µs) for the Node (End) events. You can easily write some code to load this up and collect the durations as needed.

1 reply

ajaggapa Mar 5, 2025
Author

Thanks @onsi for your response.
Yeah, Json looks better. I will try with it instead.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

junit report granularity #1523

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment 1 reply

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

junit report granularity #1523

Uh oh!

ajaggapa Mar 4, 2025

Replies: 1 comment · 1 reply

Uh oh!

onsi Mar 5, 2025 Maintainer

Uh oh!

ajaggapa Mar 5, 2025 Author

ajaggapa
Mar 4, 2025

Replies: 1 comment 1 reply

onsi
Mar 5, 2025
Maintainer

ajaggapa Mar 5, 2025
Author