Comments (13)
The problem is with the new snapshot version of JBehave. Since 3.9-SNAPSHOT, JBehave defines this method, which is not yet implemented by the Reporter: http://jbehave.org/reference/latest/javadoc/core/org/jbehave/core/reporters/StoryReporter.html#lifecyle(org.jbehave.core.model.Lifecycle)
I'll create a patch and push it tonight.
from jbehave-junit-runner.
Thank you!
from jbehave-junit-runner.
Zambrovski , Is the patch mentioned above is pushed .. Still i am facing the issue .
from jbehave-junit-runner.
Is this a duplicate of #38 ? Then it should be fixed in the latest release. @Kamaraju333 which version of jBehave and jbehave-test-runner are you using?
from jbehave-junit-runner.
I am using 3.9.1 I am unable to run specific scenario in given stories .
from jbehave-junit-runner.
Which version of the jbehave-test-runner are you using?
from jbehave-junit-runner.
Am using thucydidesjunit
On Mar 22, 2014 11:24 AM, "Benedikt Ritter" [email protected]
wrote:
Which version of the behave-test-runner are you using?
Reply to this email directly or view it on GitHubhttps://github.com//issues/34#issuecomment-38355951
.
from jbehave-junit-runner.
I don't know thucydidesjunit, but it doesn't look like it introduces a dependency onto jbehave-test-runner (http://mvnrepository.com/artifact/net.thucydides/thucydides-junit/0.9.235). Are you sure that you're problem is related to this library (the jbehave-test-runner) at all? If you have are using the jbehave-test-runner, please make sure you're using the latest version (which is 1.1.0).
from jbehave-junit-runner.
I am using following dependencies still getting error
compile group: 'junit', name: 'junit', version: '4.12'
compile 'org.jbehave:jbehave-core:4.3.5'
compile group: 'com.github.valfirst', name: 'jbehave-junit-runner', version: '2.2.0'
testCompile group: 'org.mockito', name: 'mockito-core', version: '2.22.0'
Error:- java.lang.AbstractMethodError
at org.jbehave.core.reporters.DelegatingStoryReporter.beforeScenario(DelegatingStoryReporter.java:58)
at org.jbehave.core.reporters.ConcurrentStoryReporter.beforeScenario(ConcurrentStoryReporter.java:174)
at org.jbehave.core.embedder.PerformableTree$PerformableScenario.perform(PerformableTree.java:957)
at org.jbehave.core.embedder.PerformableTree$PerformableStory.performScenarios(PerformableTree.java:858)
at org.jbehave.core.embedder.PerformableTree$PerformableStory.perform(PerformableTree.java:834)
at org.jbehave.core.embedder.PerformableTree.performCancellable(PerformableTree.java:418)
at org.jbehave.core.embedder.PerformableTree.perform(PerformableTree.java:389)
at org.jbehave.core.embedder.StoryManager$EnqueuedStory.call(StoryManager.java:292)
at org.jbehave.core.embedder.StoryManager$EnqueuedStory.call(StoryManager.java:266)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
from jbehave-junit-runner.
@naina971 , could you please provide a small project to reproduce the issue?
from jbehave-junit-runner.
When I use JUnitReportingRunner, only BeforeStories and AfterStories are run and the .feature file is not getting executed.
@RunWith(JUnitReportingRunner.class)
public class StoryConfig extends JUnitStories {
Logger logger = Logger.getLogger(StoryConfig.class.getName());
ReadProperties readProperties = new ReadProperties();
GenerateReport generateReport = new GenerateReport();
public StoryConfig() {
JUnitReportingRunner.recommendedControls(configuredEmbedder());
configuredEmbedder().useExecutorService(new SameThreadExecutors().create(
configuredEmbedder()
.embedderControls()
.useStoryTimeoutInSecs(600)
));
try {
//Required to run stories with annotated meta filters
configuredEmbedder().useMetaFilters(Arrays.asList(getListOfStoriesToRun().split(",")));
} catch (IOException e) {
e.printStackTrace();
}
}
@OverRide
public Configuration configuration() {
Class<? extends Embeddable> embeddableClass = this.getClass();
StepCollector stepCollector = new MarkUnmatchedStepsAsPending(new StepFinder(new StepFinder.ByLevenshteinDistance()));
return new MostUsefulConfiguration()
.useStepCollector(stepCollector)
.useStoryLoader(new LoadFromClasspath(embeddableClass))
.useParameterConverters(new ParameterConverters().addConverters(new ParameterConverters.DateConverter(new SimpleDateFormat("yyyy-MM-dd"))))
.useStoryReporterBuilder(new StoryReporterBuilder()
.withCodeLocation(codeLocationFromClass(embeddableClass))
.withFormats(org.jbehave.core.reporters.Format.STATS,
org.jbehave.core.reporters.Format.CONSOLE,
org.jbehave.core.reporters.Format.HTML,
org.jbehave.core.reporters.Format.XML,
AsciidoctorStoryReporter.ASCIIDOC)
.withDefaultFormats()
.withFailureTrace(true));
}
from jbehave-junit-runner.
@naina971, it seems, you are using old version of AsciidoctorStoryReporter
which is not compatible with JBehave 4.3.5, and as result you see
java.lang.AbstractMethodError
at org.jbehave.core.reporters.DelegatingStoryReporter.beforeScenario(DelegatingStoryReporter.java:58)
...
from jbehave-junit-runner.
Thanks it worked.
from jbehave-junit-runner.
Related Issues (20)
- Move to JUnit 5
- Suggestion on using this with WeldAnnotatedEmbedderRunner
- Handle RestartingScenarioFailure HOT 1
- Filtering out all scenarios in the story file causes NPE HOT 9
- How to make Junit runner read limited words from scenario and create .xml file from it. HOT 4
- I cannot start single scenario in eclipse HOT 5
- NPE on Failure.getTestHeader(Failure.java:44) when step throws assert in Lifecycle>After>FAILURE
- Using JUnitReportingRunner with pitest HOT 2
- Export the report in any other format
- Tests failing on master HOT 2
- How to generate the jbehave-surefire.xml file with parametrised examples HOT 5
- JUnitScenarioReporter throws NPE when story file name contains parentheses HOT 3
- Throws RuntimeException on scenario failure instead of java.lang.AssertionError HOT 2
- jbehave-junit-runner by maven and not from IDE HOT 7
- Jbehave-junit-runner incorrectly shows scenarios being executed when mata keywords applied in Jbehave 4 version HOT 13
- bad checksum on repo1.maven.org HOT 1
- Not showing correct test names in IntelliJ HOT 7
- Customize output monitor HOT 1
- Comments in scenario are reported as ignored HOT 10
- Remove fix for special IntelliJ handling
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jbehave-junit-runner.