jbehave-junit-runner
jbehave-junit-runner copied to clipboard
valfirst
Integrate JBehave better with JUnit. Reports all Stories, Scenarios and Steps as JUnit Suites and Test Cases.
We are using `JBehave` with `Examples` ([parametrised](https://jbehave.org/reference/stable/parametrised-scenarios.html)) scenarios. But, when we generate the SurefireReporter file (`withSurefireReporter(new SurefireReporter(this.getClass()))`), the Examples are not inside this file. Do you have any idea why?...
Bumps [jbehave-core](https://bitbucket.org/jbehave/jbehave-core) from 4.8.2 to 5.0. Commits 8829506 JBEHAVE-1540 Fix flaky examples be460e5 JBEHAVE-1541 Fix flaky unit tests 6c5ac36 JBEHAVE-1542 Fix handling of IgnoringStepsFailure thrown by composite steps ce8bb66 JBEHAVE-1544...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project. #### Changes included in this PR - Changes to the following...
Is there a way to **export the report** rather than displaying it in the IDE. Or some method to override and **get report data and manipulate** to any other format...
When a scenario would have been filtered out the reporting would still process the Description of it. This commit filters out unwanted scenarios from the rootDescription
I use with my students JUnit 4.12, JBehave 4.3.5 and pitest 1.4.5. Without using JUnitReportingRunner, I can run pitest on my test suite (with both JUnit and JBehave test cases)....
Hi, When a step inside Lifecycle>After>FAILURE throws an assertion, you get a NPE: ``` Caused by: java.lang.NullPointerException at org.junit.runner.notification.Failure.getTestHeader(Failure.java:44) ... at com.github.valfirst.jbehave.junit.monitoring.JUnitScenarioReporter.failed(JUnitScenarioReporter.java:273) ... ``` Full stack trace here: [mvn_NPE.txt](https://github.com/valfirst/jbehave-junit-runner/files/2654372/mvn_NPE.txt) I...
It currently appears as if we do not handle the RestartingScenarioFailure properly. The test/step is marked as 'passed' if it indeed failed after a restart. We should handle this case.
I'm trying to integrate this project into my existing framework using Weld, with the `@RunWith(WeldAnnotatedEmbedderRunner.class)` Are there any suggestions for going about this? Thanks