Issues
- Scenario title parsed to empty on WindowsJBEHAVE-600Resolved issue: JBEHAVE-600Mauro Talevi
- Failures in view do not cause build to failJBEHAVE-599Resolved issue: JBEHAVE-599Mauro Talevi
- Website Documentation - "Pending Steps page" refers to incorrect strategy class FailingPendingStepStrategyJBEHAVE-587Resolved issue: JBEHAVE-587Mauro Talevi
- StoryReporterBuilder code location should be settable from the output directory by Ant tasks and Maven goalsJBEHAVE-586Resolved issue: JBEHAVE-586
- Of multiple exclusion meta filters only one is evaluatedJBEHAVE-583Resolved issue: JBEHAVE-583Mauro Talevi
- Excluded scenarios should not be included into ScenarioSuccessful countJBEHAVE-570Resolved issue: JBEHAVE-570
- Excluded (filtered-out) scenarios are reported as pending as wellJBEHAVE-567Resolved issue: JBEHAVE-567Paul Hammant
- Better integration with JUnit (Separate results for each story/scenario/example)JBEHAVE-551Resolved issue: JBEHAVE-551Valery Yatsynovich
- StoryReporterBuilder does not have an easy way to provide custom StoryReporter(s)JBEHAVE-550Resolved issue: JBEHAVE-550
- StoryReporter forces me to write non thread safe codeJBEHAVE-549
- Add support for annotated steps before and after example scenariosJBEHAVE-548Resolved issue: JBEHAVE-548Mauro Talevi
- StoryRunner.runParametrisedScenariosByExamples does not execute the examples after the first failureJBEHAVE-547Resolved issue: JBEHAVE-547
- ConcurrentModificationException in xref when run multithreaded.JBEHAVE-539Resolved issue: JBEHAVE-539Paul Hammant
- Wrong encoding in reports running from JUnit (maven failsafe or surefire plugin, not dedicated jebhave maven plugin) on WindowsJBEHAVE-538
14 of 14