[jbehave-user] Potential for context view to get real monitoring capabilities

I like the context view feature of JBehave. I mean the LocalFrameContextView. You see what actually happens. But very few information are displayed. Here are some ideas what could be displayed additionally to scenario and step data: * which story is running * how many stories, scenarios and

Re: [jbehave-user] Support for dynamic variables?

Enrique, I was asking for information not demanding a feature. Can you guarantee that that page object implementation works for everyone or works at all? What if JBehave instantiates new Steps from time to time? The dynamic variables would be gone. When implementing dynamic variables JBehave

RE: [jbehave-user] Support for dynamic variables?

Hi Hans, As I mentioned we had the same problem (generating some data dynamically that Step1 uses and then Step2 needs for verification) and I was simply sharing how we solved it in case you find it useful Again we have a static map inside a static class. We call it ThreadLocalUtils the map is

Re: [jbehave-user] Screenshots in test result HTML protocol?

The WebDriverScreenshotOnFailure contains a step which is executed after a failed scenario, with the method annotated by @AfterScenario. As such you cannot pass it a parameter directly. But you can work around it, e.g. you could add a StoryReporter that write the current story path to a

Re: [jbehave-user] Potential for context view to get real monitoring capabilities

Have a look at the execution context in 4.x branch. Patches most welcome! On 05/11/2013 10:39, Hans Schwäbli wrote: I like the context view feature of JBehave. I mean the LocalFrameContextView. You see what actually happens. But very few information are displayed. Here are some ideas what