http://permalink.gmane.org/gmane.comp.java.jbehave.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.java.jbehave.user/1321 <pre>Good Morning, thank You for contributing to the first release by reporting bugs and improvements. The first version can be pulled from maven central. Or you can download it from our github project site. &lt;dependency&gt; &lt;groupId&gt;de.codecentric&lt;/groupId&gt; &lt;artifactId&gt;jbehave-junit-runner&lt;/artifactId&gt; &lt;version&gt;1.0.0&lt;/version&gt; &lt;/dependency&gt; Please let us know if you have further suggestions. Andreas Am 13.05.2012 16:42 schrieb "Andreas Ebbert-Karroum" &lt; andreas.ebbert-karroum-yJbiVz8w35r6n8oly/gPIw&lt; at &gt;public.gmane.org&gt;: </pre> Andreas Ebbert-Karroum 2012-05-19T05:45:47 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1320 <pre>Hi Graham, the passing upon pending step is the default. If it fails it means there's something else going on. Try turning on verbose failures. public abstract class MyStory extends JUnitStory { public MyStory() { configuredEmbedder().embedderControls().doVerboseFailures(true); } } Also, there is a pending.story in the trader example that you can run and it shows it doesn't fail the build. Cheers On 16/05/2012 15:12, Graham Abell wrote: </pre> Mauro Talevi 2012-05-17T10:39:20 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1319 <pre>Hi, I'm trying to stop my runs failing when there are pending steps. In my configuration I've added: .usePendingStepStrategy(new PassingUponPendingStep()) .useFailureStrategy(new SilentlyAbsorbingFailure()) but it still fails - is there something else I need to do? org.jbehave.core.embedder.Embedder$RunningStoriesFailed: Failures in running stories: automation/jbehave/smoketest_scenarios.story: org.jbehave.core.embedder.StoryManager$StoryExecutionFailed: automation/jbehave/smoketest_scenarios.story at org.jbehave.core.embedder.Embedder$ThrowingRunningStoriesFailed.handleFailures(Embedder.java:495) at org.jbehave.core.embedder.Embedder.handleFailures(Embedder.java:224) at org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:205) at automation.jbehave.JbehaveRunner.GenericRunner(JbehaveRunner.java:29) thanks, Graham </pre> Graham Abell 2012-05-16T14:12:51 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1318 <pre>You're right. Done: http://jira.codehaus.org/browse/JBEHAVE-781 On 14/05/2012 15:51, Daniel Schneller wrote: </pre> Mauro Talevi 2012-05-15T09:52:38 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1317 <pre>Would you also be so kind an raise an issue on GitHub for this? Thanks a lot! Daniel On Tue, May 15, 2012 at 1:14 AM, Jorge Pombar &lt;Jorge_Pombar-okLH5SSHHyRWk0Htik3J/w&lt; at &gt;public.gmane.org&gt;wrote: </pre> Daniel Schneller 2012-05-15T07:18:26 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1316 <pre>Thanks for the great feature as usual. I’m having some issues integrating this into my code. Here is the stack trace I’m getting: java.lang.NullPointerException: story not setup for CrossReference at org.jbehave.core.reporters.CrossReference$XRefStepMonitor.stepMatchesPattern(CrossReference.java:228) at org.jbehave.core.steps.DelegatingStepMonitor.stepMatchesPattern(DelegatingStepMonitor.java:25) at org.jbehave.core.steps.StepCandidate.matches(StepCandidate.java:135) at de.codecentric.jbehave.junit.monitoring.JUnitDescriptionGenerator.addSteps(JUnitDescriptionGenerator.java:97) at de.codecentric.jbehave.junit.monitoring.JUnitDescriptionGenerator.addScenarioSteps(JUnitDescriptionGenerator.java:90) at de.codecentric.jbehave.junit.monitoring.JUnitDescriptionGenerator.insertDescriptionForExamples(JUnitDescriptionGenerator.java:84) at de.codecentric.jbehave.junit.monitoring.JUnitDescription</pre> Jorge Pombar 2012-05-14T23:14:53 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1315 <pre>Hi Marcin, 2012/5/14 Marcin Zajączkowski &lt;mszpak-5tc4TXWwyLM&lt; at &gt;public.gmane.org&gt; I'm using it myself with Guice DI,so that shouldn't be a problem. And if it's not working yet, please raise an issue and help us fix it :) Oh, amazing. So many people started to work on this already! So maybe this time, we can end up with something that works for most, if not all of the JBehave and JUnit users :) </pre> Andreas Ebbert-Karroum 2012-05-14T21:34:20 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1314 <pre> Hi, It's not mentioned in a project description. Is it possible to use it with [String|Guice]AnnotatedPathRunner do allow to run stories requiring DI/IoC frameworks? Btw, there is an another alternative implementation by Alexander Lehmann: https://jira.codehaus.org/browse/JBEHAVE-703 https://github.com/alexlehm/jbehave-junit-examples Regards Marcin --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Marcin Zajączkowski 2012-05-14T21:18:55 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1313 <pre>Certainly you tried harder to get more advanced features implemented. Our solution is based on our own needs from current projects which are neither multi threaded nor currently annotation driven. If this becomes necessary I am sure we will take another look at your project for inspiration. :-) Daniel On May 14, 2012 5:41 PM, &lt;Lance.Semmens-qaMCw6PCdq4&lt; at &gt;public.gmane.org&gt; wrote: </pre> Daniel Schneller 2012-05-14T15:49:14 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1312 <pre>I'll have to take a look at your approach. I must admit that I am a jbehave novice and you may have found an easier way. Here's a couple of things that I can remember from my implementation. 1. I disliked the StoryReporter interface as it almost forced me to write code that was not thread-safe. I wrote a StoryReporter2 interface (and an adapter with a ThreadLocal) so that I could write "cleaner" code. 2. I seem to remember that I had to do something nasty in order to refresh the steps instance before each test as it could contain "dirty" variables. 3. To get deep integration with JUnit, I needed to extend ParentRunner instead of BlockJUnit4ClassRunner as is done in jbehave 4. My code was able to support a method annotated with &lt; at &gt;Steps which could provide a collection of steps instances. Cheers, Lance. ________________________________ From: daniel.schneller-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org [mailto:daniel.schneller-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org] On Behalf Of Daniel Schneller Sent: 14 May 201</pre> Lance.Semmens-qaMCw6PCdq4< at >public.gmane.org 2012-05-14T15:41:18 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1311 <pre>Then that method should probably be annotated as &lt; at &gt;Deprecated with an appropriate message to point to the preferred way of doing this? On Mon, May 14, 2012 at 3:45 PM, Mauro Talevi &lt;mauro.talevi-hQ+s5KbX5YmGglJvpFV4uA&lt; at &gt;public.gmane.org&gt;wrote: </pre> Daniel Schneller 2012-05-14T13:51:08 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1310 <pre>The recommended way is to use the StepsFactory because that what's used by the runner to support multi-threading. The addSteps() method is still supported for backward compatibility and it creates under the hood a ProvidedStepsFactory. Cheers On 14/05/2012 14:31, HAAS Christian wrote: </pre> Mauro Talevi 2012-05-14T13:45:43 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1309 <pre>Hello again; As for reporting missing steps as error or silently ignoring them: Good idea to base that on JBehaves own configuration settings. Regarding priorities, I’d be happy enough with the JUnitStory based runner; I just saw you already patched that – thanks a lot, works for me now and we can start using it. I still had to modify my setup a bit: So far we were only using JUnitStory.addSteps(), which adds to the list returned from JUnitStory.candidateSteps() . But your runner uses ConfigurableEmbedder.stepsFactory().createCandidateSteps() . In my case, the factory was null. I’m now returning a ProvidedStepsFactory that receives the result of candidateSteps() :) . Apparently, these two methods of steps provision are present in parallel and I still haven’t found out what the intended way to provide them is. I only see Embedder.reportStepdocsAsEmbeddables() in jbehave.core doing a dual variant (if candidateSteps() returns an empty list, it uses the factory). Thanks again! ch _______</pre> HAAS Christian 2012-05-14T12:31:23 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1308 <pre>Hi, thank you for trying it out, and your initial - and very helpful - feedback! 2012/5/14 HAAS Christian &lt;Christian.Haas-USXAA5bZaHGDvotElmWtJA&lt; at &gt;public.gmane.org&gt; I know there are myriad ways to configure JBehave, some are working already, most of them probably are not. Thanks for making us aware of this one :) I agree. Missing steps should be reported. Reporting the scenario as failed or reporting pending steps, should be in line with the general reporting configuration in JBehave (PendingStepsStrategy, ...) Hm, you could possible go through all Step classes and look for annotated methods. Should not be too much work. Thanks for reporting this as issues. What's your order for them? (which one should be first?) </pre> Andreas Ebbert-Karroum 2012-05-14T10:17:56 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1307 <pre>Thanks for creating the issues :) On Mon, May 14, 2012 at 11:25 AM, HAAS Christian &lt; Christian.Haas-USXAA5bZaHGDvotElmWtJA&lt; at &gt;public.gmane.org&gt; wrote: </pre> Daniel Schneller 2012-05-14T09:52:56 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1306 <pre>If it's not too much hassle, would you be so kind to create (ideally 3) issues on GitHub for these topics? Would make it easier for us (and you :-)) to track progress. Daniel On Mon, May 14, 2012 at 11:25 AM, HAAS Christian &lt; Christian.Haas-USXAA5bZaHGDvotElmWtJA&lt; at &gt;public.gmane.org&gt; wrote: </pre> Daniel Schneller 2012-05-14T09:36:47 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1305 <pre>Hello there! Thank you for this – I was about to start creating an own runner for the team I’m in, but your implementation is very close to what I wanted. I did some tests and have found the following things: - JUnitStory is not supported, only JUnitStories We’re using the single-story embedder and while a switch could be done with not much effort, it would be great if your runner would be capable of handling this case on its own. - Missing steps are not reported, related scenarios are OK If a new scenario is added with missing steps (no binding code exists), the steps are not added to the report tree and even worse, the scenario is marked OK. Personally I’d want those to be reported as failures (with a stub implementation text extractable from the failure trace) – but I can imagine others might not want this behaviour; Is there a possibility to add configuration options to the JUnitReportingRunner? The missing steps should at least be reported as pending steps. - After/Before Sto</pre> HAAS Christian 2012-05-14T09:25:33 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1304 <pre>Interesting, for some reason we did not see this when we began moving the old implementation from Google Code forward. Would have been good to know. I downloaded the project and browsed through it. I have not looked in too much detail at your code, but it seems a bit more complicated than what we have done. We only have 4 classes with about 500 LOC total. It is based on the StoryReporter interface in JBehave and does not use much more. We would love to get feedback on how good people think it is and what's missing. We hope we'll be able to keep it so small, because that would (hopefully) keep it more maintainable as well. Currently we were not thinking about getting it included in the main JBehave project, but maybe in the future it could be. Daniel On Mon, May 14, 2012 at 10:00 AM, &lt;Lance.Semmens-qaMCw6PCdq4&lt; at &gt;public.gmane.org&gt; wrote: </pre> Daniel Schneller 2012-05-14T09:23:41 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1303 <pre>I did this myself last year but unfortunately I needed to re-invent the wheel to much for it to be accepted by the jbehave team. I have attached a maven project here http://jira.codehaus.org/browse/JBEHAVE-551 which includes two junit runners and some test cases that use them. My initial driver for doing this was that the jbehave spring runner was not using a new app context for each test run when using &lt; at &gt;DirtiesContext (I'm not sure if this has been fixed by now). I have included a Spring runner which properly cleans up after each test when using &lt; at &gt;DirtiesContext. Cheers, Lance. ________________________________ From: Andreas Ebbert-Karroum [mailto:andreas.ebbert-karroum-yJbiVz8w35r6n8oly/gPIw&lt; at &gt;public.gmane.org] Sent: 13 May 2012 15:43 To: user-b1QraVsTlj/IJWOP8RzEEmD2FQJk+8+b&lt; at &gt;public.gmane.org Cc: Daniel Schneller Subject: [jbehave-user] Announcement: Beta Release of new jbehave-junit-runner Hi, it has always been a problem that when jbehave is run via junit, the reporting to junit was less than h</pre> Lance.Semmens-qaMCw6PCdq4< at >public.gmane.org 2012-05-14T08:00:20 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1302 <pre>Hi, it has always been a problem that when jbehave is run via junit, the reporting to junit was less than helpful. With the jbehave-junit-runner all your stories, scenarios and steps are reported to JUnit. We based the library on the inital work of Mark Burnett and Aaron von der Haar. You find the project now hosted on GitHub. Please feel free to raise issues, when things don't work for you. https://github.com/codecentric/jbehave-junit-runner The final release will be made available on maven central, but we wanted to give the community the possibility to provide early feedback. Have fun. We hope you find that useful! </pre> Andreas Ebbert-Karroum 2012-05-13T14:42:36 http://permalink.gmane.org/gmane.comp.java.jbehave.user/1301 <pre>Simply declare the meta at scenario level, i.e. after the "Scenario:" keyword. The meta properties will be automatically passed to the given stories. Here's an example: https://github.com/jbehave/jbehave-core/blob/master/examples/trader/src/main/java/org/jbehave/examples/trader/stories/given_stories_parametrised_by_examples.story Cheers On 09/05/2012 02:21, Jorge Pombar wrote: </pre> Mauro Talevi 2012-05-09T14:47:07 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.java.jbehave.user