-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
901d1ec
commit b37c0b0
Showing
4 changed files
with
26 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b37c0b0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does not appear to resolve the issue introduced in 3231
For instance this file contains 2 nested test directories:
This single collection contains 2 tests, following this directory hierarchy:
I would expect the JUnit report to output these tests on the report, as well as the collection the tests came from:
Instead, I get this:
As a result, when multiple collections are run they no longer display their respective Collection in the runner
Instead they list a series of directories without separation or punctuation, ending with the name of the failing request & test
This is much less helpful from a diagnostic perspective, where dozens of results for multiple collections are displayed simultaneously, with no additional indication of where each individual failure came from
vs
I would guess that this is the updated
attribs.name.value
displayed in place of the original formattedcollection.name
, but the impact of this change seems to be farther reaching than intended