Skip to content
This repository has been archived by the owner on Jan 10, 2020. It is now read-only.

Nested testsuites in XML output are not parseable by Jenkins #18

Open
reid opened this issue Jul 19, 2013 · 2 comments
Open

Nested testsuites in XML output are not parseable by Jenkins #18

reid opened this issue Jul 19, 2013 · 2 comments
Labels

Comments

@reid
Copy link

reid commented Jul 19, 2013

This is a regression in Grover 0.1.16.

Grover 0.1.16 introduced a change that causes additional <testsuites> tags to be nested inside the root <testsuites> tag.

Jenkins will only report tests in <testcase/> tags that are in nested in <testsuite> tags in the root <testsuites> tag. Nested <testsuites> are silently ignored. This comprises the majority of YUI's use of Grover.

(Examples can be found on the internal YUI dev-3.x component build. The regression occurred on build 240. The last correctly working use of Grover was on build 239. Compare the junit.xml artifacts on those builds.)

@reid
Copy link
Author

reid commented Jul 19, 2013

It appears the regression occurred in f5b1f91.

The YUITest.TestRunner.getResults("XML") method appears to return nested <testsuites> because of the change to the results object from data[key] to data[name][key] when results has length !== 1.

@pablolmiranda
Copy link

The same problem is doing the TAP files receive a wrong head ( first line ). All have 6 test suites with 122 tests, but it only shows 2 tests.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants