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)?
