Yes, that is what I meant: report rendering would complete but build
would "fail", i.e. it would report build failure, as instructed by the
ignoreFailure=true|false flag. By default it would be false, so after
the rendering it would notify of any build failure.
On 03/05/2010 12:49, Ben Sullivan wrote:
> Sorry not quite.
>
> I want report generation to not stop on failure. I want report rendering to
> not stop if a failure has happened. But I want the Ant build to report as
> build failed instead of build successful right at the end of the build script
> so my CI server can reflect the health of my software and display all error
> reports should a stakeholder drill down onto the failures.
>
> Cheers
>
> Ben
>
> On 03/05/2010, at 7:11 PM, Mauro Talevi wrote:
>
>
>> So, if I understand, what you want is for report generation (ie the
>> scenario runner) to work as is now, ie not stop upon failure (as
>> controlled by ignoreFailure flag), but you'd like the report rendering
>> to be failure-aware and stop if there have been any failures (behaviour
>> which will be controlled by another ignoreFailure flag). OTOH, this
>> should be easily achievable by looking at the stats that have been
>> collected and detecting failures.
>>
>> If so, could you please create a JIRA issue requesting the report
>> rendering to be failure aware?
>>
>> Cheers
>>
>> On 03/05/2010 10:42, Ben Sullivan wrote:
>>
>>> Hi Mauro
>>>
>>> Yeah - I saw the doco. It's nearly what I'm after but not quite. I want
>>> my scenarioRunner and report rendering to run to completion and then the
>>> Ant build to fail. If I did what you say, I wouldn't get to the report
>>> rendering so I can't generate a report artifact detailing my failures
>>> (although my stakeholders could look at the CI server console but I'd
>>> prefer to not go down that path.
>>>
>>> I think we need something like errorProperty or failureProperty that the
>>> ant junit task has:
>>>
>>> http://ant.apache.org/manual/OptionalTasks/junit.html
>>>
>>> Cheers
>>>
>>> Ben
>>>
>>> On 03/05/2010, at 5:50 PM, Mauro Talevi wrote:
>>>
>>>
>>>
>>>> Hi Ben,
>>>>
>>>> you need to set batch="true" and ignoreFailure="false" in the scenario
>>>> runner task to have the scenarios failures be detected after all stories
>>>> have been run. Else, batch="false" and ignoreFailure="false" will
>>>> fail-fast after each story.
>>>>
>>>> http://jbehave.org/reference/stable/running-scenarios.html
>>>>
>>>> Cheers
>>>>
>>>> On 03/05/2010 09:39, Ben Sullivan wrote:
>>>>
>>>>
>>>>> Hi
>>>>>
>>>>> I have switched off fail fast in order to render my reports. How do I
>>>>> ensure my build fails at the end if scenarios have failed? Normally
>>>>> there is an errorProperty and/or failProperty that can be detected at the
>>>>> end. Without this, my CI build always gives me green even if I have
>>>>> failed scenarios.
>>>>>
>>>>> Thanks
>>>>>
>>>>> Ben
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>>
>>
>
> ---------------------------------------------------------------------
> 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
