This is a good idea - I would really like this feature as well.

Cheers

Ben

On 31/10/2009, at 5:01 AM, Ravi Varanasi wrote:

Mauro -

Thanks for the pointer for the decorator.

As far as my requirement - it is mainly a build verification requirement. I like the summary report at end (numbers). It is a nice one line indicator instead of scrolling through the console log.

However, the requirement for a Business Analyst/Customer having in- sight into all the passing stories and their scenarios, some kind of a hierarchical view would be useful

Story <description>
      Scenario <description> <Pass/Fail>


Provided tags to the story would also be beneficial if the number of stories get into 100's range and if there are any cross-cutting aspects to the stories. One of the tags can be iteration #/

Ravi


On Fri, Oct 30, 2009 at 1:29 PM, Mauro Talevi <[email protected] > wrote:
Hi,

To print out all the steps - see question

"How do I output all my scenario steps - and not just when a scenario fails?"

in http://jbehave.org/reference/stable/faq.html

ATM, to count the number of scenarios you may write a decorator for the ScenarioReporter that holds a counter that is incremented in say the afterScenario() method.

But yes, WRT to reporting JBehave has a lot of potential for improvement. IMO, the scenario reporter is appropriate for a CI setting in which the main focus is to highlight what's been run and if there any failures.

There are many ways to improve the scenario output. Myself and Paul had an very interesting chat with Ward Cunningham at Agile conf this year where he was explaining a new "swim lane" reporting paradigm, that seemed very promising to us.

As usual, JBehave is very much driven by user demand. So I would suggest that we start a thread collecting the requirement for more expressing scenario reporting.

Cheers



Hitesh Sarda wrote:
was thinking about this myself as well.

The reporter prints Pending steps but not passed steps. Anyway to
configure it to print everything? This will create a good test-result
artifact that the business users can understand and signoff a release.

- Hitesh



2009/10/30 Ravi Varanasi <[email protected]>:
This might be a newbie question. Is there anyway to have the scenario reporter to report number of scenarios run, how many passed, how many failed (similar to the surefire plugin) ? Wanted to make sure there isn't something obvious in configuration missed by me or should override the PrintStreamScenario ?

Thanks,
Ravi



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

  http://xircles.codehaus.org/manage_email




Reply via email to