Skip to content

Commit c74f5c7

Browse files
gchanolyismmbelton-buildkite
committed
Add 'Mandatory JUnit XML Attributes' section
PIE-1252 t log A customer, Robinhood were having issues with uploading their JUnit XML file. They were missing the mandatory attributes from the testcase element. https://3.basecamp.com/3453178/buckets/20365997/messages/5611360141#__recording_5459384344 https://3.basecamp.com/3453178/buckets/20365997/card_tables/cards/5611354161 Co-authored-by: Oly Su <[email protected]> Co-authored-by: mbelton-buildkite <[email protected]>
1 parent 8625ab7 commit c74f5c7

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

pages/test_analytics/importing_junit_xml.md.erb

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,15 @@ While most test frameworks have a built-in JUnit XML export feature, these JUnit
44

55
{:toc}
66

7+
## Mandatory JUnit XML attributes
8+
9+
The following attributes are mandatory for the `<testcase>` element:
10+
11+
* `classname`: full class name for the class the test method is in.
12+
* `name`: name of the test method.
13+
14+
To learn more about the JUnit XML file format, see [JUnit XML reporting file format](https://llg.cubic.org/docs/junit/) from Linux Lighting Group.
15+
716
## How to import JUnit XML in Buildkite
817

918
It's possible to import XML-formatted JUnit (or [JSON](/docs/test-analytics/importing-json#how-to-import-json-in-buildkite)) test results to Buildkite Test Analytics with or without the help of a plugin.

0 commit comments

Comments
 (0)