Re: GivenStories @ the end of execution

Hi, there is no such mechanism, but you could: * use the Lifecycle to execute steps (not stories) after the execution of a scenario (executed after each scenario) * have a final scenario which invokes the given stories On 26/10/2015 08:27, igal epshtein wrote: Hi, I'm using a

Re: Eclipse+Maven+JBehave Project

All the examples provided by JBehave are Maven based. Eclipse, IDEA and all major IDEs support Maven. http://jbehave.org/reference/stable/running-examples.html On 16/11/2015 06:38, Shiva Tej wrote: Hi, Could you please share the Eclipse+Maven+JBehave sample Project? Regards, Shivatej k --

Re: Custom StepMonitor doesn't work in version 4.xxx

Please raise a JIRA issue for this: http://jbehave.org/how-to-contribute.html On 03/10/2015 12:28, Irko Kordirko wrote: I created a custom StepMonitor: | privateStepMonitorstp =newNullStepMonitor(){ publicvoidperforming(Stringstep,booleandryRun){ System.err.println("DEBUG - Monitor. Step =

Re: StoryReporter being executed 3 times ...

Hi, thanks for the example. It's a weird one and it requires some debugging. On 29/12/2015 15:12, igal epshtein wrote: I've upload some simple example, pls see that the Before/After stories is being executed several times , same has happens with the rest methods I'm implementing.

Re: StoryReporter being executed 3 times ...

Difficult to help you without a working example that reproduces the problem. Can you please provide this working example project please? On 29/12/2015 09:54, igal epshtein wrote: Hi, I'm implementing my own Reporter by extending StoryReporter. The thing is , each override method being

Re: Scenario level declared meta data do not appear in generated XML report

Hi Damien, welcome to the list! Could you please provide a fully working example reproducing this behaviour? http://jbehave.org/how-to-contribute.html Cheers On 18/11/2015 19:11, Damien Grandemange wrote: Hi, this is my first post, so i may quickly myself : Damien, french guy, using

Re: Rerun failed test with Jbehave and WebDriver, Java

You can throw a RestartingStoryFailure or RestartingScenarioFailure. On 08/03/2016 19:06, Olena Shyshkova wrote: I want to rerun failed end-to-end tests. I'm using Jbehave and WebDriver, Java. Currently I'm using Maven but going to migrate to Gradle. Is there any solution? -- You received

Re: Add new test result status to report

Hi Olena, this behaviour is currently not supported. But you can retrieve the results statistics for each run and keep track of the statistics. You could then define a new report output for these statistics. Feel free to create a new JIRA issue and attach your contribution! Cheers On

Re: story examples

Hi, currently, you can only parametrise given stories by examples http://jbehave.org/reference/stable/given-stories.html > On 23 May 2016, at 07:45, Tibor B wrote: > > Hello, > > I know it is possible to use

Re: Explicit parameters from Context

Hi, The context is a user defined object so it is not known to JBehave. If you want to inject parameters in methods you could use the @Named annotation, specifying the name-value pairs in the Meta: section. That said, it's not clear why you'd want to do this, as the values of the Context

Re: beforeStory method from StoryReporter executed before @BeforeStories

Hi thanks for the sample project.The issue you are seeing is a consequence of the fact that there are two special “stories” called (BeforeStories and AfterStories - used to report issues in the execution of the @BeforeStories and @AfterStories annotated steps).If you disregard

Re: beforeStory method from StoryReporter executed before @BeforeStories

Yes, the beforeStory() event will be invoked for each story and after the @BeforeStories annotated method. But if you don’t share your project which reproduces your behaviour you can’t be helped. Please ensure that it is a self-contained (and as simple as possible) Maven project. > On

Re: beforeStory method from StoryReporter executed before @BeforeStories

BeforeStories events are reported in a separate file from the other story-specific reports. But why are you getting the NPE? > On 7 Aug 2016, at 14:22, jms2m...@gmail.com wrote: > > Yes I did in the configuration part only.I created the custom reporter and > added ib the cobfiguration

Re: Expected Release date for 4.1 version

Hi Rafa, I’d been trying to get the release to work with mvn 3, overcoming the problem of the Jenkins repo: https://issues.jenkins-ci.org/browse/JENKINS-13637 I’ve now sorted out the issue by setting up a local Nexus instance for the

Re: WebDriverScreenshotOnFailure is failing

This typically means that there was an issue with the underlying browser. Try killing all instances of browser (e.g. killall firefox) and run again. > On 23 Jun 2017, at 13:51, shyamkumarraju kandimalla > wrote: > > Hi All, > > I am trying to execute my

Re: Commented line in scenario is reported as skipped test

We could make it a configurable feature. Please raise a JIRA issue for this. > On 4 Apr 2017, at 09:49, Hannes Niederhausen wrote: > > Hi, > > We have a lot of jbehave tests and use jenkins to run them. If we use the !-- > lines they are reported as skipped tests.

Re: Can JBehave be used for testing a batch processing system?

Hi Ken, BDD can be used to verify any system’s behaviour that can be automated. The tricky bit is to describe the behaviour in a way that is intelligible from a business point of view (big files aren’t as you’ve noted).You may try to autogenerate the input files based on templates with

Re: JBehave and version of guava library

Sure, no problem. Please raise a JIRA issue for this. > On 26 Aug 2017, at 07:59, Irko Krokodilko wrote: > > > > W dniu piątek, 25 sierpnia 2017 23:55:06 UTC+2 użytkownik Irko Krokodilko > napisał: > Hi, > > Are there amy plans to upgrade a version of guava library in

Re: When will a new version of JBehave be released ?

Hi Valery, version 4.1.2 has been finally released. Thanks for your patience. I’ve moved one issue to 4.1.3: https://jbehave.atlassian.net/browse/JBEHAVE-1138 I’d like to get this one out quickly but we should devise a better example to

Re: Getting error as pending steps

What have you posted? > On 29 Nov 2017, at 17:34, Maganti Suryanarayana murthy > wrote: > > Posted in stack overflow. Could anyone sort out the issue ? > > -- > You received this message because you are subscribed to the Google Groups > "JBehave User" group. > To

Re: Accessing "Examples" Data at Step Level

Hi, not really sure what you mean. There are several ways to parametrise the scenarios: http://jbehave.org/reference/stable/parametrised-scenarios.html http://jbehave.org/reference/stable/meta-parametrisation.html

Re: Jbehave story report is not showing the time in report i.e., the Duration is shown as 00:00:00.000.

You need to provide a sample project that reproduces the issue for us to help you. > On 21 Feb 2018, at 16:39, Maganti Suryanarayana murthy > wrote: > > Any help on this > ? > > On Tuesday, February 20, 2018 at 10:16:58 AM UTC-6, Maganti Suryanarayana > murthy wrote: >

Re: Jbehave story report is not showing the time in report i.e., the Duration is shown as 00:00:00.000.

Please package all this in a downloadable zip that can be opened and run. Don't forget a readme with tool versions etc > On 23 Feb 2018, at 18:32, Maganti Suryanarayana murthy <suryai...@gmail.com> > wrote: > > Hi Mauro Talevi, > > I have used gradle as a bu

Re: Content Security Policy prohibits inline styles in JBehave reports

Hi, this is an odd one. The CSS styling hasn’t changed for a long time and I’ve not seen this issue (on different platforms, mostly using Chrome). Which platform are you using? Can you provide a project that reproduces it? Or If you can provide a patch that works for you, we can try to

Re: Finding unused steps

Hi Jurgen, this is an interesting use case. Can you please create a JIRA for it and we can satisfy it by adding the appropriate functionality. Thanks > On 23 Apr 2018, at 17:21, Jürgen Schmied wrote: > > I tried to find unused steps and ended up with

Re: JBehave 4+ - After upgrading core to 4.3.5 jbehave is pasrsing the stories 3 times.

What makes you conclude that it’s parsing the story 3 times? > On 10 Nov 2018, at 01:59, Gajendra Sahu wrote: > > Hi All, > > After upgrading core to 4.3.5 jbehave is pasrsing the stories 3 times and so > it is taking too long for actual story to start running. > > I am using below - > >

Re: How can I compress the IDE log while running the Jbehave?

You can define your own reporter based on IdeOnlyConsoleOutput: https://jbehave.org/reference/stable/reporting-stories.html > On 7 Nov 2018, at 02:09, Gajendra Sahu wrote: > > Hi All, > > The runner goes to all the stories to