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
Proposition
I'm using cucumber + cypress. I think this can apply to any situation though.
The produced .xml file contains tags, one having a file=<scenario-file> attribute (for ex file="cypress\integration\login\api.feature").
It would be really nice to have the option to do: "mochaFile": "<path>/[fileName].xml" -> report named api-034eb437b9bc00a7dc9b7b80924fdbfc.xml
And of course combinations if needed: "mochaFile": "<path>/[fileName]-[hash].xml" -> report named api.xml
That would be really useful.
Cypress make one report per file, so if I have 10 files containing each 20 tests, I get 10 files. The end goal for me would be to have file names (which are displayed in my reports) a bit clearer for an end user.
That PR allows the renaming of the only report file, correct? It doesn't create multiple files (one per testsuite), when using [suiteName], right? Is there a way to split the report into multiple report files?
Hi,
Request Type : Enhancement/Feature request (not a bug :) !)
Today
https://github.com/michaelleeallen/mocha-junit-reporter/blob/master/index.js#L486
By specifying
"mochaFile": "<path>/[hash].xml"
we have a unique file which name is a hashOf course plain strings also work (
"mochaFile": "<path>/test-output[hash].xml"
). There's no other keyword I'm aware of.Proposition
I'm using cucumber + cypress. I think this can apply to any situation though.
The produced .xml file contains tags, one having a
file=<scenario-file>
attribute (for exfile="cypress\integration\login\api.feature"
)."mochaFile": "<path>/[fileName].xml"
-> report named api-034eb437b9bc00a7dc9b7b80924fdbfc.xml"mochaFile": "<path>/[fileName]-[hash].xml"
-> report named api.xmlThat would be really useful.
Cypress make one report per file, so if I have 10 files containing each 20 tests, I get 10 files. The end goal for me would be to have file names (which are displayed in my reports) a bit clearer for an end user.
Here's an xml example this package generates
The text was updated successfully, but these errors were encountered: