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
You can only use describe to define the name for the test suite.
However, it does not end up in JUnit report.
I wanted to include env name in describe content, to be able to diffentiate tests in CI (Gitlab) reporting tools.
Right now, all generated JUnit xml files contains the same test names, so only one is used in CI.
Setting testsuite name is enough for Gitlab to not merge tests, however tests cannot be differentiated afterward (same suite/name), additionally setting test classname resolve that issue too.
Suggested solution
Use module.describeTitle in main/lib/reporter/reporters/junit.xml.ejs for both testsuite name and testcase classname
Alternatives / Workarounds
Overwriting testsuite name and tests classname allows usable feedback in Gitlab CI.
Additional Information
I have not tested solution outside of Gitlab, so other JUnit parsers may differ.
I can probably provide a PR if required.
The text was updated successfully, but these errors were encountered:
Description
Hello !
describe
content is not used in JUnit reportsBDD documentation indicates that
However, it does not end up in JUnit report.
I wanted to include env name in describe content, to be able to diffentiate tests in CI (Gitlab) reporting tools.
Right now, all generated JUnit xml files contains the same test names, so only one is used in CI.
Setting
testsuite name
is enough for Gitlab to not merge tests, however tests cannot be differentiated afterward (same suite/name), additionally setting testclassname
resolve that issue too.Suggested solution
Use
module.describeTitle
inmain/lib/reporter/reporters/junit.xml.ejs
for bothtestsuite name
andtestcase classname
Alternatives / Workarounds
Overwriting
testsuite name
and testsclassname
allows usable feedback in Gitlab CI.Additional Information
I have not tested solution outside of Gitlab, so other JUnit parsers may differ.
I can probably provide a PR if required.
The text was updated successfully, but these errors were encountered: