The new ContextStepMonitor works with jbehave 3.9 I discovered now, but not with 4.0-beta-4, at least not with the same code.
Maybe it is just because version 4 is still beta, or it has to be used in another way than in 3.9. I suppose there will be an example project for 4.0, so that I then can see how to use it for that version when it is released. I will use jbehave 3.9 until then. 2014-02-24 9:44 GMT+01:00 Hans Schwäbli <[email protected]>: > I could run that CoreStories, but could not port the example to version > jbehave-beta-4. > > The CoreStories example runs on version 3.10-SNAPSHOT which I cannot > depend in Maven since it is not in the Maven repository. > > Maybe CoreStories works only for 3.10-SNAPSHOT? > > I have to figure this out. It is not so easy with stuggling with Maven and > Java code at the same time to get it working. > > > 2014-02-20 18:53 GMT+01:00 Mauro Talevi <[email protected]>: > > CoreStories has a working example. >> >> On 20 Feb 2014, at 16:56, Hans Schwäbli <[email protected]> >> wrote: >> >> Yes, I want to show the running progress like I could do with >> SeleniumStepMonitor. >> >> I try to figure out how to use that new way. >> >> >> 2014-02-20 1:07 GMT+01:00 Mauro Talevi <[email protected]>: >> >>> The SeleniumStepMonitor should be replaced by the ContextStepMonitor, >>> now in core. >>> >>> What is the objective? Show the running progress? >>> >>> On 19/02/2014 16:34, Hans Schwäbli wrote: >>> >>> I am opening a new topic for the problem with the SeleniumStepMonitor >>> in JBehave 4.0 beta 4 with JBehave-web 3.5.5 and 3.6-beta-1. >>> >>> It does not show up with that version. It works however with JBehave 3.9. >>> >>> I discovered that in method >>> org.jbehave.core.embedder.PerformableTree.RunContext.scenarioSteps(Scenario, >>> Map<String, String>) a MatchingStepMonitor is used instead of the >>> configured step monitor. >>> >>> It can be fixed by creating an anonymous class and overriding >>> org.jbehave.core.steps.MarkUnmatchedStepsAsPending.collectScenarioSteps(List<CandidateSteps>, >>> Scenario, Map<String, String>, StepMonitor) >>> >>> MarkUnmatchedStepsAsPending myStepCollector = new >>> MarkUnmatchedStepsAsPending() { >>> @Override >>> public List<Step> >>> collectScenarioSteps(List<CandidateSteps> candidateSteps, Scenario >>> scenario, Map<String, String> parameters, >>> StepMonitor stepMonitor) { >>> return super.collectScenarioSteps(candidateSteps, >>> scenario, parameters, *mySeleniumStepMonitor*); >>> } >>> }; >>> Then in the configuration I write: .useStepCollector(myStepCollector) >>> >>> It must be an older issue since month ago I had the same problem with >>> JBehave 4.0 beta 3 and switched to version 3.9 because of that. >>> >>> Maybe it is a bug (or you can please tell me how to configure it >>> properly for JBehave 4.x)? >>> >>> >>> >> >
