You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 16, 2022. It is now read-only.
The two options I can see for this are to either put the fullName of the spec (including all parent describes) in the name attribute or taking what we used to have as the name of the suite (fullName with the name of the test removed) and put that all in classname.
My concern with the second is that with nested describes or just a longer description, the classname could end up with whitespace in it, which seems weird to me for an attribute called classname.
I would be happy to review a pull request that implements either of these solutions.
Given the following jasmine file
The old xml format would result in the following.
Which when viewed using the jenkins junit plugin creates a hierarchy like
The format that 1.0 creates is
Which leaves you with a hierarchy like
I believe the proper way to do it with junit xml is to add the classname attribute
The text was updated successfully, but these errors were encountered: