gmane.comp.java.jbehave.user

Announcement: Release 1.0.0 of new jbehave-junit-runner

Andreas Ebbert-Karroum — 2012-05-19T05:45:47

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.

<dependency>
    <groupId>de.codecentric</groupId>
    <artifactId>jbehave-junit-runner</artifactId>
    <version>1.0.0</version>
</dependency>

Please let us know if you have further suggestions.

Andreas
Am 13.05.2012 16:42 schrieb "Andreas Ebbert-Karroum" <
andreas.ebbert-karroum-yJbiVz8w35r6n8oly/gPIw< at >public.gmane.org>:

Re: don't fail for pending steps

Mauro Talevi — 2012-05-17T10:39:20

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:

don't fail for pending steps

Graham Abell — 2012-05-16T14:12:51

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

Re: Announcement: Beta Release of new jbehave-junit-runner

Mauro Talevi — 2012-05-15T09:52:38

You're right.  Done:  http://jira.codehaus.org/browse/JBEHAVE-781

On 14/05/2012 15:51, Daniel Schneller wrote:

Re: Announcement: Beta Release of new jbehave-junit-runner

Daniel Schneller — 2012-05-15T07:18:26

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 <Jorge_Pombar-okLH5SSHHyRWk0Htik3J/w< at >public.gmane.org>wrote:

RE: Announcement: Beta Release of new jbehave-junit-runner

Jorge Pombar — 2012-05-14T23:14:53

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.JUnitDescriptionGenerator.createDescriptionFrom(JUnitDescriptionGenerator.java:50)
                at de.codecentric.jbehave.junit.monitoring.JUnitDescriptionGenerator.createDescriptionFrom(JUnitDescriptionGenerator.java:38)
                at de.codecentric.jbehave.junit.monitoring.JUnitReportingRunner.buildDescriptionFromStories(JUnitReportingRunner.java:100)
                at de.codecentric.jbehave.junit.monitoring.JUnitReportingRunner.<init>(JUnitReportingRunner.java:57)
                at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
                at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
                at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
                at java.lang.reflect.Constructor.newInstance(Unknown Source)
                at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31)
                at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24)
                at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
                at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
                at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
                at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24)
                at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init>(JUnit4TestReference.java:33)
                at org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassReference.<init>(JUnit4TestClassReference.java:25)
                at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.createTest(JUnit4TestLoader.java:48)
                at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.loadTests(JUnit4TestLoader.java:38)
                at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:452)
                at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
                at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
                at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

Here is my config code:
< at >RunWith(JUnitReportingRunner.class)
public class AwesomeNameStories extends JUnitStories {

    public AwesomeNameStories() {
        CrossReference crossReference = new CrossReference().withJsonOnly().withOutputAfterEachStory(true)
                .excludingStoriesWithNoExecutedScenarios(true);
        ContextView contextView = new LocalFrameContextView().sized(640, 120);
        SeleniumContext seleniumContext = new SeleniumContext();
        SeleniumStepMonitor stepMonitor = new SeleniumStepMonitor(contextView, seleniumContext,
                crossReference.getStepMonitor());
        Format[] formats = new Format[] { new SeleniumContextOutput(seleniumContext), CONSOLE, WEB_DRIVER_HTML };
        StoryReporterBuilder reporterBuilder = new StoryReporterBuilder()
                .withCodeLocation(codeLocationFromClass(AwesomeNameStories.class)).withFailureTrace(true)
                .withFailureTraceCompression(true).withDefaultFormats().withFormats(formats)
                .withCrossReference(crossReference);

        Configuration configuration = new SeleniumConfiguration().useSeleniumContext(seleniumContext)
                .useFailureStrategy(new FailingUponPendingStep())
                .useStoryControls(new StoryControls().doResetStateBeforeScenario(false)).useStepMonitor(stepMonitor)
                .useStoryLoader(new LoadFromClasspath(AwesomeNameStories.class))
                .useStoryReporterBuilder(reporterBuilder);
        useConfiguration(configuration);

        ApplicationContext context = new SpringApplicationContextFactory("vipmgr-steps.xml").createApplicationContext();
        useStepsFactory(new SpringStepsFactory(configuration, context));
    }

I don’t have any issues when I comment out the “< at >RunWith(JUnitReportingRunner.class)”

Thanks,
Enrique

From: Andreas Ebbert-Karroum [mailto:andreas.ebbert-karroum< at >codecentric.de]
Sent: Monday, May 14, 2012 2:34 PM
To: user< at >jbehave.codehaus.org
Subject: Re: [jbehave-user] Announcement: Beta Release of new jbehave-junit-runner

Hi Marcin,
2012/5/14 Marcin Zajączkowski <mszpak< at >wp.pl<mailto:mszpak< at >wp.pl>>

with [String|Guice]AnnotatedPathRunner do allow to run stories requiring
DI/IoC frameworks?

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

Btw, there is an another alternative implementation by Alexander Lehmann:
https://jira.codehaus.org/browse/JBEHAVE-703
https://github.com/alexlehm/jbehave-junit-examples

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

--
Mit freundlichen Grüßen / Best regards

Andreas Ebbert-Karroum | Bereichsleiter der Agilen Software Factory

codecentric AG | Merscheider Straße 1 | 42699 Solingen | Deutschland
tel: +49 (0) 212.23362825 | fax: +49 (0) 212.23362879 | mobil: +49 (0) 175.2664109
www.codecentric.de<http://www.codecentric.de> | blog.codecentric.de<http://blog.codecentric.de> | www.meettheexperts.de<http://www.meettheexperts.de> | www.more4fi.de<http://www.more4fi.de>

Sitz der Gesellschaft: Düsseldorf | HRB 63043
Vorstand: Klaus Jäger (Vorsitzender) | Mirko Novakovic . Rainer Vehns
Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Bernd Klinkmann . Jürgen Schütz

Diese E-Mail einschließlich evtl. beigefügter Dateien enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und löschen Sie diese E-Mail und evtl. beigefügter Dateien umgehend. Das unerlaubte Kopieren, Nutzen oder Öffnen evtl. beigefügter Dateien sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

Re: Announcement: Beta Release of new jbehave-junit-runner

Andreas Ebbert-Karroum — 2012-05-14T21:34:20

Hi Marcin,

2012/5/14 Marcin Zajączkowski <mszpak-5tc4TXWwyLM< at >public.gmane.org>


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

Re: Announcement: Beta Release of new jbehave-junit-runner

Marcin Zajączkowski — 2012-05-14T21:18:55

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

RE: Announcement: Beta Release of new jbehave-junit-runner

Daniel Schneller — 2012-05-14T15:49:14

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, <Lance.Semmens-qaMCw6PCdq4< at >public.gmane.org> wrote:

RE: Announcement: Beta Release of new jbehave-junit-runner

2012-05-14T15:41:18

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 < at >Steps which could provide a collection of steps instances.
 
Cheers,
Lance.
________________________________

From: daniel.schneller-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org [mailto:daniel.schneller-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org] On Behalf Of Daniel Schneller
Sent: 14 May 2012 10:24
To: user-b1QraVsTlj/IJWOP8RzEEmD2FQJk+8+b< at >public.gmane.org
Subject: Re: [jbehave-user] Announcement: Beta Release of new jbehave-junit-runner


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, <Lance.Semmens-qaMCw6PCdq4< at >public.gmane.org> wrote:



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 < at >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 < at >DirtiesContext. 
 
Cheers,
Lance.
 
________________________________

From: Andreas Ebbert-Karroum [mailto:andreas.ebbert-karroum-yJbiVz8w35r6n8oly/gPIw< at >public.gmane.org] 
Sent: 13 May 2012 15:43
To: user-b1QraVsTlj/IJWOP8RzEEmD2FQJk+8+b< at >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 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!

-- 
Mit freundlichen Grüßen / Best regards

Andreas Ebbert-Karroum | Bereichsleiter der Agilen Software Factory

codecentric AG | Merscheider Straße 1 | 42699 Solingen | Deutschland
tel: +49 (0) 212.23362825 | fax: +49 (0) 212.23362879 <tel:%2B49%20%280%29%20212.23362879>  | mobil: +49 (0) 175.2664109 <tel:%2B49%20%280%29%20175.2664109> 
www.codecentric.de | blog.codecentric.de | www.meettheexperts.de | www.more4fi.de

Sitz der Gesellschaft: Düsseldorf | HRB 63043
Vorstand: Klaus Jäger (Vorsitzender) | Mirko Novakovic . Rainer Vehns
Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Bernd Klinkmann . Jürgen Schütz

Diese E-Mail einschließlich evtl. beigefügter Dateien enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und löschen Sie diese E-Mail und evtl. beigefügter Dateien umgehend. Das unerlaubte Kopieren, Nutzen oder Öffnen evtl. beigefügter Dateien sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.



Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mails are not encrypted and cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The sender
therefore does not accept liability for any errors or omissions in the
contents of this message which arise as a result of e-mail transmission.
If verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities
or related financial instruments.

UBS Limited is a company limited by shares incorporated in the United
Kingdom registered in England and Wales with number 2035362.
Registered office: 1 Finsbury Avenue, London EC2M 2PP.  UBS Limited
is authorised and regulated by the Financial Services Authority.

UBS AG is a public company incorporated with limited liability in
Switzerland domiciled in the Canton of Basel-City and the Canton of
Zurich respectively registered at the Commercial Registry offices in
those Cantons with Identification No: CH-270.3.004.646-4 and having
respective head offices at Aeschenvorstadt 1, 4051 Basel and
Bahnhofstrasse 45, 8001 Zurich, Switzerland.  Registered in the
United Kingdom as a foreign company with No: FC021146 and having a
UK Establishment registered at Companies House, Cardiff, with No:
BR 004507.  The principal office of UK Establishment: 1 Finsbury Avenue,
London EC2M 2PP.  In the United Kingdom, UBS AG is authorised and
regulated by the Financial Services Authority.

UBS reserves the right to retain all messages. Messages are protected
and accessed only in legally justified cases.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

Re: Announcement: Beta Release of new jbehave-junit-runner

Daniel Schneller — 2012-05-14T13:51:08

Then that method should probably be annotated as < at >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 <mauro.talevi-hQ+s5KbX5YmGglJvpFV4uA< at >public.gmane.org>wrote:

Re: Announcement: Beta Release of new jbehave-junit-runner

Mauro Talevi — 2012-05-14T13:45:43

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:

RE: Announcement: Beta Release of new jbehave-junit-runner

HAAS Christian — 2012-05-14T12:31:23

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
____________________________________________________
Christian Haas
Software Engineer
FREQUENTIS AG

Innovationsstraße 1, 1100 Vienna, Austria
Phone   +43-1-811 50 – 8353
Mobile   +43-664-60 850 – 8353
Fax       +43-1-811 50 – 77 8353
Web      www.frequentis.com
E-Mail    christian.haas< at >frequentis.com<mailto:christian.haas< at >frequentis.com>

Handelsgericht Wien (Vienna Commercial Court): FN 72115 b
DVR 0364797, ATU 14715600
____________________________________________________
Diese E-Mail könnte vertrauliche und/oder rechtlich geschützte Informationen enthalten. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

From: Andreas Ebbert-Karroum [mailto:andreas.ebbert-karroum< at >codecentric.de]
Sent: Montag, 14. Mai 2012 12:18
To: user< at >jbehave.codehaus.org
Subject: Re: [jbehave-user] Announcement: Beta Release of new jbehave-junit-runner

Hi,

thank you for trying it out, and your initial - and very helpful - feedback!
2012/5/14 HAAS Christian <Christian.Haas< at >frequentis.com<mailto:Christian.Haas< at >frequentis.com>>

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.

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


- 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.

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, ...)

- After/Before Story/Scenario not listed
For me a minor issue: “After/Before Stories” is always listed although not present, but for Story or Scenario they are not listed, even when present.
I guess this stems from the problem not to know which steps class has (or hasn’t) such methods and which one of them failed.

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

--
Mit freundlichen Grüßen / Best regards

Andreas Ebbert-Karroum | Bereichsleiter der Agilen Software Factory

codecentric AG | Merscheider Straße 1 | 42699 Solingen | Deutschland
tel: +49 (0) 212.23362825 | fax: +49 (0) 212.23362879 | mobil: +49 (0) 175.2664109
www.codecentric.de<http://www.codecentric.de> | blog.codecentric.de<http://blog.codecentric.de> | www.meettheexperts.de<http://www.meettheexperts.de> | www.more4fi.de<http://www.more4fi.de>

Sitz der Gesellschaft: Düsseldorf | HRB 63043
Vorstand: Klaus Jäger (Vorsitzender) | Mirko Novakovic . Rainer Vehns
Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Bernd Klinkmann . Jürgen Schütz

Diese E-Mail einschließlich evtl. beigefügter Dateien enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und löschen Sie diese E-Mail und evtl. beigefügter Dateien umgehend. Das unerlaubte Kopieren, Nutzen oder Öffnen evtl. beigefügter Dateien sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

Re: Announcement: Beta Release of new jbehave-junit-runner

Andreas Ebbert-Karroum — 2012-05-14T10:17:56

Hi,

thank you for trying it out, and your initial - and very helpful - feedback!

2012/5/14 HAAS Christian <Christian.Haas-USXAA5bZaHGDvotElmWtJA< at >public.gmane.org>



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

Re: Announcement: Beta Release of new jbehave-junit-runner

Daniel Schneller — 2012-05-14T09:52:56

Thanks for creating the issues :)

On Mon, May 14, 2012 at 11:25 AM, HAAS Christian <
Christian.Haas-USXAA5bZaHGDvotElmWtJA< at >public.gmane.org> wrote:

Re: Announcement: Beta Release of new jbehave-junit-runner

Daniel Schneller — 2012-05-14T09:36:47

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 <
Christian.Haas-USXAA5bZaHGDvotElmWtJA< at >public.gmane.org> wrote:

RE: Announcement: Beta Release of new jbehave-junit-runner

HAAS Christian — 2012-05-14T09:25:33

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 Story/Scenario not listed
For me a minor issue: “After/Before Stories” is always listed although not present, but for Story or Scenario they are not listed, even when present.
I guess this stems from the problem not to know which steps class has (or hasn’t) such methods and which one of them failed.

Thanks again and kind regards,
ch
____________________________________________________
Christian Haas
Software Engineer
FREQUENTIS AG

Innovationsstraße 1, 1100 Vienna, Austria
Phone   +43-1-811 50 – 8353
Mobile   +43-664-60 850 – 8353
Fax       +43-1-811 50 – 77 8353
Web      www.frequentis.com
E-Mail    christian.haas< at >frequentis.com<mailto:christian.haas< at >frequentis.com>

Handelsgericht Wien (Vienna Commercial Court): FN 72115 b
DVR 0364797, ATU 14715600
____________________________________________________
Diese E-Mail könnte vertrauliche und/oder rechtlich geschützte Informationen enthalten. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

From: Andreas Ebbert-Karroum [mailto:andreas.ebbert-karroum< at >codecentric.de]
Sent: Sonntag, 13. Mai 2012 16:43
To: user< at >jbehave.codehaus.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 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!

--
Mit freundlichen Grüßen / Best regards

Andreas Ebbert-Karroum | Bereichsleiter der Agilen Software Factory

codecentric AG | Merscheider Straße 1 | 42699 Solingen | Deutschland
tel: +49 (0) 212.23362825 | fax: +49 (0) 212.23362879 | mobil: +49 (0) 175.2664109
www.codecentric.de<http://www.codecentric.de> | blog.codecentric.de<http://blog.codecentric.de> | www.meettheexperts.de<http://www.meettheexperts.de> | www.more4fi.de<http://www.more4fi.de>

Sitz der Gesellschaft: Düsseldorf | HRB 63043
Vorstand: Klaus Jäger (Vorsitzender) | Mirko Novakovic . Rainer Vehns
Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Bernd Klinkmann . Jürgen Schütz

Diese E-Mail einschließlich evtl. beigefügter Dateien enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und löschen Sie diese E-Mail und evtl. beigefügter Dateien umgehend. Das unerlaubte Kopieren, Nutzen oder Öffnen evtl. beigefügter Dateien sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

Re: Announcement: Beta Release of new jbehave-junit-runner

Daniel Schneller — 2012-05-14T09:23:41

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, <Lance.Semmens-qaMCw6PCdq4< at >public.gmane.org> wrote:

RE: Announcement: Beta Release of new jbehave-junit-runner

2012-05-14T08:00:20

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 < at >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 < at >DirtiesContext. 
 
Cheers,
Lance.
 
________________________________

From: Andreas Ebbert-Karroum [mailto:andreas.ebbert-karroum-yJbiVz8w35r6n8oly/gPIw< at >public.gmane.org] 
Sent: 13 May 2012 15:43
To: user-b1QraVsTlj/IJWOP8RzEEmD2FQJk+8+b< at >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 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!

Announcement: Beta Release of new jbehave-junit-runner

Andreas Ebbert-Karroum — 2012-05-13T14:42:36

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!

Re: Using GivenStories can I turn off execution of GivenStories ran using a Meta tag?

Mauro Talevi — 2012-05-09T14:47:07

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: