Adding to what Alexander has rightfully said, everything in JBehave
output is stylable via CSS (and you can add javascript to provide a
dynamic look&feel - see the story navigator). In fact, the styling is
separate from the production of the "raw" reports in the different
formats (html, xml, txt), and these are then styled using the
appropriate resources (default or custom) at the end of the execution.
The reports view is also templated.
A wiki format of the reports view is possible via a custom template. If
you are willing to work on it and contribute it, we'd be happy to
include in the core resources for the benefit of others.
Other than this, if you want to bounce some more specific ideas on the
list, I'm sure others will chip in with their experience.
Cheers
On 16/03/2012 13:48, Alex Lehmann wrote:
the styling of the reports is done by freemarker templates and
css/javascript, that should be easy to adapt to other layouts.
wiki integration is not implemented AFAIK, but it should be possible
to create a wiki markup report with freemaker as well that you can
copy into your wiki manually (or you can use a jenkins postprocessor
to publish the wiki documents, I guess)
bye, Alexander
On 16.03.2012 10:32, rakesh mailgroups wrote:
Hi,
I'm hoping to make JBehave story files the main documentation for our
application that I can point other developers to so they can see how to
use our app.
Initially, I plan to make the reports available from our Jenkins server
available but I wanted to know if anyone had any other ideas around:
1. Wiki integration
2. Styling the reports better
3. Anything else
Sorry to be vague but I'm open to ideas!
Thanks
Rakesh
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
