Reference documentation can be found at:

http://jbehave.org/reference/stable/

Reports in particular are found:

http://jbehave.org/reference/stable/reports.html

If you want to just use the reporter that writes to console and report
errors, follow the reports configuration documentation but use

            @Override
            public ScenarioReporter forReportingScenarios() {
                return new PrintStreamScenarioReporter(System.out, new
Properties(), keywords(), true);
            }

Cheers

On 03/06/2010 16:37, Barbara Rosi-Schwartz wrote:
> Thanks for the very quick reply, Mauro.
>
> I am a beginner user and and the moment I am using everything out of the box, 
> i.e. no customised configuration of the reporters. If you can give me a quick 
> example of an appropriate configuration that could help me with this problem, 
> I would be very grateful.
>
> Also, can you point me to suitable documentation, if it exists?
>
> Thanks again,
> B.
>
>   
>> -----Original Message-----
>> From: Mauro Talevi [mailto:[email protected]]
>> Sent: 03 June 2010 15:56
>> To: [email protected]
>> Subject: Re: [jbehave-user] Visibility of actual vs expected values in
>> JBehave reports?
>>
>> Hi Barbara,
>>
>> at the moment, the PrintStreamScenarioReporter (the base for all file-
>> based reporters) allows you to show the failure if the reportErrors
>> boolean flag is turned on (it defaults to false).   This would show you
>> the failure stack trace after the scenario is run.
>>
>> When a step failure occurs (FAILURE)
>> // other steps that are NOT PERFORMED
>> // then print out stack trace that caused failure
>>
>> You may also want to show in the step, eg
>>
>> When a step failure occurs (FAILURE - expected A but got B).
>>
>> Note that "expected A but got B" here would have to be the failure
>> exception message, as generated by say a matcher assert invocation.
>>
>> You can configure the reporter to do that too, by overriding the
>> default behaviour of the reporter.
>>
>> The configuration change is straightforward if you are using a single
>> reporter but a bit more involved if you are using the reporter builder
>> and say you want this change for all file-based reporters.
>>
>> If you send a sample project showing how you configure your reporters
>> we can show you how to change the configuration.
>>
>> Cheers
>>
>> On 03/06/2010 14:36, Barbara Rosi-Schwartz wrote:
>>     
>>> Hi all.
>>>
>>> I am currently using ensureThat(boolean) to test my verification
>>>       
>> points. The problem I have is that, when the test fails, I would like
>> to see the expected and actual values in the reported output, in order
>> to try and better understand what went wrong.
>>     
>>> Is there any way to accomplish this?
>>>
>>> TIA,
>>> B.
>>>
>>> The information contained in this email is strictly confidential and
>>>       
>> for the use of the addressee only, unless otherwise indicated. If you
>> are not the intended recipient, please do not read, copy, use or
>> disclose to others this message or any attachment. Please also notify
>> the sender by replying to this email or by telephone (+44 (0)20 7896
>> 0011) and then delete the email and any copies of it. Opinions,
>> conclusions (etc.) that do not relate to the official business of this
>> company shall be understood as neither given nor endorsed by it. IG
>> Index Ltd is a company registered in England and Wales under number
>> 01190902. VAT registration number 761 2978 07. Registered Office:
>> Friars House, 157-168 Blackfriars Road, London SE1 8EZ. Authorised and
>> regulated by the Financial Services Authority. FSA Register number
>> 114059.
>>     
>>> ---------------------------------------------------------------------
>>> 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
>>
>>     
>
> The information contained in this email is strictly confidential and for the 
> use of the addressee only, unless otherwise indicated. If you are not the 
> intended recipient, please do not read, copy, use or disclose to others this 
> message or any attachment. Please also notify the sender by replying to this 
> email or by telephone (+44 (0)20 7896 0011) and then delete the email and any 
> copies of it. Opinions, conclusions (etc.) that do not relate to the official 
> business of this company shall be understood as neither given nor endorsed by 
> it. IG Index Ltd is a company registered in England and Wales under number 
> 01190902. VAT registration number 761 2978 07. Registered Office: Friars 
> House, 157-168 Blackfriars Road, London SE1 8EZ. Authorised and regulated by 
> the Financial Services Authority. FSA Register number 114059.
>
> ---------------------------------------------------------------------
> 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


Reply via email to