No, at the moment (3.x) it's only failures that reported back. The
successful step is meant to be self-explanatory in its language.
The 4.x refactor of the story execution will make it easier to
incorporate extensions to the data and metadata incurred during execution.
Feel free to share your ideas on what info you'd like to make
available. In particular, please explain your use cases.
The example below is not very illustrative IMO: the info that the
result of the step execution is passed is already there as is the
parameter used.
Why would you feel the need to add more info? I assume you have other
use cases.
Cheers
On 26/10/2012 22:35, Foley, Brooks (GE Healthcare) wrote:
Sorry one more question in the custom-html-output.ftl I would like the
output on success to display a result like the following:
*Scenario: MyTest*
Given I go to "http://www.google.com";
When I sign in with "myaccount" and "mypassword"
Then I expect to see "myacco...@gmail.com" (PASSED Result =
"myacco...@gmail.com")
I can see in the custom-html-output.ftl the line for the failure case.
<#if step.getFailure()??><pre
class="failure">${step.failureCause}</pre></#if>
Is there one for the success case like
<#if step.getSuccess()??><pre
class="success">${step.successCause}</pre></#if>
And how do I write to the step.failureCause/step.successCause from my
stories.java file?
Alternately is there a way to write to the Jbehave project html via
system.out.print ?
Thanks,
Brooks
*From:*Foley, Brooks (GE Healthcare)
*Sent:* Friday, October 26, 2012 2:50 PM
*To:* user@jbehave.codehaus.org
*Subject:* [jbehave-user] How to use a custom report.ftl
I can see from the Trader example how to implement a
custom-html-output.ftl. How would I do this for the a
custom-report.ftl replacing the jbehave-reports.ftl?
Thanks,
Brooks
