Skip to content

Instantly share code, notes, and snippets.

@systemsincode

systemsincode/Mappings Between Cucumber JUNIT and TestRail via plugin.md

Last active August 1, 2019 00:15
Show Gist options
  • Save systemsincode/702ef84b8483fc171b5ded557af72aa3 to your computer and use it in GitHub Desktop.
Save systemsincode/702ef84b8483fc171b5ded557af72aa3 to your computer and use it in GitHub Desktop.
Download ZIP
Mappings Between Cucumber - JUNIT XML - TestRail for jenkinssco/testrail-plugin
Raw
Mappings Between Cucumber JUNIT and TestRail via plugin.md
Cucmber-jvm Project (via Jekins) JUNIT XML REPORT (in surefire-reports folder)* TestRail UI (as provided by jenkinsci/testrail-plugin)
NameSpace of TestProject class testsuite tag 'Section' (looks like a folder)
Feature testcase tag 'classname' attribute N/A
Scenario testcase tag 'name' attribute Testcase as result (ignores testcases in other 'sections)
Steps Only in failure tags Only refered to in failed result cucumber 'stacktrace'

* Differs from cucumber-junit-report.xml my the root of target dir:

  • testsuite name=cucmber.runtime.formatter.JUnitFormatter
  • each testcase has a nested system-out CDATA section that report on all step results
@systemsincode
Copy link
Author

  • I just noticed testrail-plugin can upload stale results. I had moved a repo which caused my jenkins job to fail and the plugin noticed the xml was old but uploaded a job execution anyway :(

@systemsincode
Copy link
Author

systemsincode commented Aug 1, 2019 •
edited
Loading

I'm trying to identify how to get a folder tree of features to upload to TestRail

This conversation tells me that surefire will only export a xml per test class
cucumber/cucumber-jvm#171
I can't find the surefire bug raised and mentioned in the above.
http://jira.codehaus.org/browse/SUREFIRE-821

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment