Is it possible to run a story as a Story object, and not have to specify a
path?
Currently I'm retrieving stories from a online editor in the form of a
json, and parsing that text into a story object via..
embedder.storyRunner().storyOfText(embedder.configuration(),
storyText.toString(), story
I have a meta filter on a story similar to this:
Meta:
@bug JBEHAVE-281
The issue is when I try to filter on that, using
-bug JBEHAVE-281
it does not match, but only matches to similar items when I do
-bug JBEHAVE*
Is there a way to escape the dash in the meta filter so I can filter for
That worked, Thanks!
On Sat, Jun 21, 2014 at 9:45 AM, Mauro Talevi mauro.tal...@aquilonia.org
wrote:
You can use -bug JBEHAVE*281.
Or use the Groovy Matcher
http://jbehave.org/reference/stable/meta-filtering.html
On 18/06/2014 00:28, Brent Barker wrote:
I have a meta filter on a story
Hi
I'm trying to configure the number of threads to run via maven, however the
number of threads does not seem to be picked up. If i directly edit the
annotation in WeldAnnotatedStoryRunner, I am able to get the tests to run
with multiple threads.
Here is my configuration:
execution
A feature that would be really nice and would give a huge advantage over
other framework's plugins would be the ability to navigate from an
annotated step method to the story/stories it is being used in. Currently I
have only seen the ability to navigate from a story to a step.
Is this possible
Bump, do people think this feature is very beneficial or do people think it
wouldn't be useful? The company I'm working at right now would love to have
this feature and they are looking for a plugin that supports it.
On Wed, Jun 25, 2014 at 12:08 PM, Brent Barker brentbark...@gmail.com
wrote
Hi everyone!
Is there a easy way to conditionally skip a story using a meta tag? For
example, I want to annotate my story with @bug BUG- and then check if
that bug is still open or not. If it is still open, skip the scenario/story.
Right now I am extending RegexStoryParser, calling
need to extend createMetaMatcher(String) method in
MetaFilter although we could make it injectable.
Alternatively, use the GroovyMetaMatcher to invoke a groovy script that
will do you check.
Cheers
On 10/07/2014 19:49, Brent Barker wrote:
Hi everyone!
Is there a easy way
-1033 to add JiraMetaMatcher in
jbehave-rest.
If you could provide a pull request for JBEHAVE-1033 it'd be most great!
Cheers
On 12/07/2014 00:51, Brent Barker wrote:
Great thank you for your response!
I'd like to avoid editing the MetaFilter class if I can. Making it
injectable would
HI again,
I am using the story mapping feature with Maven. I am wondering if it is
possible to map stories with meta tags at the scenario level, not only at
the story level.
For example, I have a scenario inside of a story annotated with @bug. I'd
like the map reports view to show that a
, Mauro Talevi mauro.tal...@aquilonia.org
wrote:
Reproduced and fixed: https://jira.codehaus.org/browse/JBEHAVE-1041
Can you try out latest snapshot?
On 11/08/2014 18:10, Brent Barker wrote:
Hi,
When executing reports in multiple threads, the execution times are not
correct. Instead
this, and all of your hard work!
On Mon, Aug 25, 2014 at 3:18 PM, Mauro Talevi mauro.tal...@aquilonia.org
wrote:
Try with latest releases: 3.9.4 or 4.0-beta-10.
On 25/08/2014 21:03, Brent Barker wrote:
Thanks for looking into that!
I tried the latest snapshot. However, it still doesn't
Hi again,
I noticed from upgrading JBehave 3.9.2 to 3.9.3, the order which
AfterScenario was executed changed.
Our method annotated with @AfterScenario() takes a screenshot of the
failure in the scenario, and continues on to the next scenario.
A story with this:
Lifecycle:
After:
Outcome:
This would be a excellent thing to have! I always have to open a class, hit
CTRL + F, then use that window in a story file.
On Wed, Sep 17, 2014 at 1:33 AM, Hans Schwäbli bugs.need.love@gmail.com
wrote:
As it seems CTRL+F for searching text does not work inside the JBehave
editor.
will be taken on Google's website.
Thanks in advance!
-Brent
On Thu, Sep 25, 2014 at 2:21 PM, Brent Barker brentbark...@gmail.com
wrote:
Hi again,
I noticed from upgrading JBehave 3.9.2 to 3.9.3, the order which
AfterScenario was executed changed.
Our method annotated with @AfterScenario() takes
Hi again,
Is there a way to restart a story if it has failed once before? I know
there is a way to restart a scenario by throwing a
RestartingScenarioFailure exception.
This would be useful for our selenium tests. There are countless things
that can go wrong when running these browser tests.
a usecase for the need to restart the story please create a
JIRA for this and describe it there.
Cheers
On 29/10/2014 22:08, Brent Barker wrote:
Hi again,
Is there a way to restart a story if it has failed once before? I know
there is a way to restart a scenario by throwing
Is it possible to run a GivenStories in the middle of a scenario?
My use case is, there are parts of the application that has steps that need
to be performed to get to the correct area, but the test in that area is
the same. Then, there are some steps afterwards that needs to be performed.
It
Hi Everyone,
Who would I contact to talk about the license of JBehave? The license
specifically states:
Neither the name of JBehave nor the names of its contributors may be used
to endorse or promote products derived from this software without specific
prior written permission.
What we are
19 matches
Mail list logo