Gwen Report Portal Integration

Gwen now provides seamless integration with report portal for centralised reporting and analytics.

To send all your Gwen evaluation results to a report portal server, just add the following settings to your Gwen properties file and invoke Gwen on your existing feature suite with the -f rp option:


rp.endpoint = http://[host]:[port]
rp.uuid = [report-portal-api-key]
rp.launch = [launch-name]
rp.project = [project-name]
  • Set [host] and [port] to the host and port of your report portal server
  • Set [report-portal-api-key] to the unique key of your report portal instance
  • Set [launch-name] to your desired launch name
  • Set [project-name] to your desired project name

These are the minimal settings required to achieve integration. Once you’ve configured the above settings, simply include rp in your -f/--format option when you invoke Gwen.

Example: ./gwen -b -f rp features

And if you want to also generate HTML reports:

./gwen -b -r target/reports -f rp,html features

The results of all evaluated Gherkin nodes in your features will then be asynchronously sent to report portal during execution. The complete Gherkin syntax is supported and reported (including Rules, Scenarios, Outlines/Templates, steps, data tables, doc strings, etc, etc..). That’s all there is to it! You will now be able to visualise all your Gwen results in report portal and utilise its analytics features to track and manage results.

Supported options and features

  • Reruns
  • Merges
  • Source references
  • File attachments
  • Error traces (inlined or attached)
  • Screenshots
  • Optional logging of Gwen meta
  • Optional logging of StepDefs (inlined or nested)
  • Optional logging of tags and annotations (as attributes)
  • Heartbeat for monitoring connection availability
  • Various test case ID generation strategies (better history association for Gherkin)
  • And more