Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.4
-
Component/s: Maven Plugin
-
Labels:None
-
Number of attachments :
Description
When you execute JBehave from Maven, a report or set of reports should be written to a sub-directory of the standard maven target directory or target/site directory.
One set of reports should be human-readable (for instance, HTML).
Another set of reports should be machine-readable (for instance, XML).
Both reports should include the same summary and count information about the number of scenarios and steps executed, failed, pending, successful and not executed.
Both reports should contains per-scenario and per-step content and outcomes.
This will greatly aid in the creation of plug-ins that execute JBehave in CI systems and reporting systems such as Hudson, Bamboo and Sonar.
Activity
Mauro Talevi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 2.4 [ 15664 ] |
Mauro Talevi
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
A framework to aggregate reports of different formats (HTML, XML, TXT) and render them
to HTML has been added as part of
JBEHAVE-161. The raw reports are generated during scenario execution and written to a configurable target directory, "target/jbehave-reports" by default.The rendered view is produced from the raw reports via the render-reports Maven goal or Ant task. The rendered view will also include the stats, generated via the statistics scenario reporter.
Scenario reporter added so far include: HTML (
JBEHAVE-161), XML (JBEHAVE-227) and Statistic (JBEHAVE-226).Other reporters for machine and human-readable formats can be easily added.