The Codehaus JBehave JIRA instance
(http://jira.codehaus.org/browse/JBEHAVE) has been disactivated.
JBehave JIRA has migrated from Codehaus to Atlassian Cloud:
https://jbehave.atlassian.net/projects/JBEHAVE
The existing user names have been maintained but no user information
such as
As Codehaus is closing down, the JBehave mailing lists have been
migrated to Google Groups.
Unfortunately, Google Groups imposes a limit on the number of members
that can be manually added each day.
So you should subscribe to the new lists of interest:
Hi Brian,
the upcoming releases will be JDK 8 compatible.
https://jira.codehaus.org/browse/JBEHAVE-1066
Cheers, M
On 13/05/2015 18:38, Brian Jordan wrote:
Hi,
We have a walking skeleton using Jbehave, Spring4, and Java 1.8. We
had to modify the Spring release to 4.1.1.RELEASE in
Yes, keyword synonyms are supported:
http://jbehave.org/reference/stable/keyword-synonyms.html
On 06/05/2015 18:03, Attila Franczen wrote:
Hello guys,
Is it possible to assign to one keyword multiple localized variants of
the translation just like in cucumber?
.
Thanks,
Phong
From: Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
Sent: Saturday, March 28, 2015 1:56 AM
To: user@jbehave.codehaus.org
Subject: Re: [jbehave-user] Story duration are not calculated correctly in
multi-thread execution
Hi Phong,
I would imagine you're running
2015
total=175161000
Do you have any idea what could be causing the much higher story
duration reported in storyDurations.props? Is there any JBehave
configuration I should check in our setup?
Thanks,
Phong
*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Saturday, March 21
) with JBehave 3.9.4+
(https://jira.codehaus.org/browse/JBEHAVE-1041), and if I want to use
and access the story duration available in storyDurations.props file
from the same FreeMarker template file, how can I do this?
Thanks,
Phong
*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent
Can you provide a sample project reproducting this behaviour.
This problem should be fixed in latest release.
On 17/03/2015 22:39, tran, phong wrote:
When I ran stories with a single thread (serial), the story duration
in reports looked correct. The duration time is in minutes as
expected.
You can use the parametrisation by name delimiters, as explained in the
doc page cited by you:
http://jbehave.org/reference/stable/parametrised-scenarios.html
On 12/03/2015 15:37, Teriblus wrote:
Hi everyone,
I posted something on stackoverflow regarding an issue my team is
having with
Hi Brent,
the license of JBehave is BSD-style license - a rather standard and
liberal license.
It means that you cannot provide a product or consulting service and
claim it is on behalf of the JBehave project or its contributors.
It does allow you to build on top of JBehave extension tools
Can you please provide an example reproducing this behaviour?
On 09/02/2015 22:37, Mark Derricutt wrote:
Hi all,
I'm using 4.0-beta-11 in our tests and on one of our developers
machine we seem to randomly get the following enum conversion error:
|When we update the agreement with:
Hi,
most people download from Maven Central.You could try getting some
statistics from there.
The mailing lists and user groups are http://jbehave.org/mailing-lists.html
Cheers
On 07/01/2015 20:10, Senaratne, Niranjala wrote:
Hi, I would like to find our some statistics about JBehave.
Hi,
there is currently no way to parallelise the running of the scenarios
parametrised in the examples table, because the concurrency is managed
at story level.
You could break down your 50+ examples in smaller scenarios and run them
as different stories.
Cheers
On 07/01/2015 08:50,
I meant to write spot-on :-)
On 20/12/2014 17:36, Mauro Talevi wrote:
Hi,
your contribution was stop-on! Many thanks for it.
We welcome any more that you'd feel like contributing.
In general, the affected version is seldom used and only typically
applies to bugs.
What is more
No, GivenStories can only be used at the start of the scenario.
Yes, composite steps is a viable option for your need.
Alternatively, we could envisage defining composite steps in the textual
scenario where the source is a snippet of steps.
Given file://path/to/some.steps
Just an idea, not
Hi,
if you are using the Console report format, you can simply write to
System.out.
Otherwise, if you want a more fine-grained solution that applies to
multiple reporters, you can decorate any existing reporter extending
PrintStreamOutput and use the method
protected void print(String
Hi
can you provide an example project with your configuration that
reproduces this behaviour?
Cheers
On 10/11/2014 18:30, Simon Kent wrote:
Hi
We were testing out an upgrade to JBehave 3.9.5 and noticed that our
story reports only showed the duration of the last story run (we run
all
Hi
you're trying to employ two different uses of GivenStories anchors which
are not meant to used together.
If you want to use parametrised GivenStories by examples row, you should
specify the examples table in the scenario that invokes the given story
and use the anchor to specify the row:
when run from maven, but passes when run as junit from the IDE.
Give it a go, and please let me know if you find anything interesting.
Cheers,
Dariusz
On Tue, Oct 7, 2014 at 6:14 PM, Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org wrote:
There's nothing dodgy about
There's nothing dodgy about log-related in JBehave, simply because there
is no logging framework used.
What's usually quite dodgy is the logging frameworks' classloading and
dynamic lookups, which don't play well with Maven's rather strict
classloading.
To overcome classloading issues, it
a
reference to the example table in the second call.)
Cheers
*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* den 19 september 2014 17:36
*To:* user@jbehave.codehaus.org
*Subject:* Re: [jbehave-user] Parametrised scenario problem
It's not a bug, it's the current behaviour of the system
I don't think there is a way to solve it except to have two facade
methods that use the appropriately names variable that invoke a third
common method that does the check.
On 19/09/2014 11:23, Zheng, Ayesha(AWF) wrote:
Hi all,
I have a scenario:
Given a user open homepage
Then should see
It's not a bug, it's the current behaviour of the system. Nothing
prevents us from evolving this behaviour.
Feel free to raise the JIRA issue, describing how you'd like to see it
evolve.
Cheers
On 19/09/2014 16:12, Anders wrote:
I would argue that this is a serious bug, a bug that has
with the code here.
Chad
On 9/14/2014 11:57 PM, Mauro Talevi wrote:
I'm not sure I understand how you use mocks. In any case, it's a BDD
anti-pattern to hide away in some logic that is executed at every step
because you lose the communication aspect.
It'd be much better if you could express
Hi Viktor,
the app looks very interesting, but the installation curve seems pretty steep.
It would great if you could produce an installer that minimes built-time tools
and only requires runtime ones.
By the way, can the app be packaged as a stardard java webapp?
An example of how users can
of
time which mocks will need to be setup, it would simplify things if we
could just iterate over their builders and register them accordingly
before the when steps.
Chad
On 9/13/2014 1:34 AM, Mauro Talevi wrote:
No, but why would you want to do that?
Can you explain your usecase?
On 13/09
No, but why would you want to do that?
Can you explain your usecase?
On 13/09/2014 02:46, Chad Wilson wrote:
Is there any way to run something before all When steps?
Chad
-
To unsubscribe from this list, please visit:
We could add an anchor to the given story path that indicates that it
should only be executed once per run context.
On 12/09/2014 16:06, Mauro Talevi wrote:
There is no such behaviour built-in.
You can nonetheless implement some state logic in your story A so that
if successful it won't get
There is no such behaviour built-in.
You can nonetheless implement some state logic in your story A so that if
successful it won't get repeated more than once.
Think about setting up a context object.
On 12 Sep 2014, at 11:50, Zheng, Ayesha(AWF) xuzh...@ebay.com wrote:
Thanks for your
You need to create a Codehaus account:
http://jbehave.org/how-to-contribute.html
On 01/09/2014 18:10, Anders wrote:
Message Title
I'd like to be able to participate in the JBehave community, so how do
I gain access to Jira?
/Anders
The Web Runner provides a simple web interface to explore existing steps
by matching the input provided:
http://jbehave.org/reference/web/stable/using-web-runner.html
On 01/09/2014 18:12, Frank Pedroza wrote:
As we write more and more stories, we obviously accumulate a growing
number of
Scanning is now supported without a DI container:
http://jira.codehaus.org/browse/JBEHAVE-1042
On 21/08/2014 00:51, Mauro Talevi wrote:
Typically, you'd use a DI container to achieve this, via the
corresponding implementation of the InjectableStepsFactory.
On 20/08/2014 22:23, Chad Wilson
looks correct.
I'll try to get a example project put together.
On Wed, Aug 20, 2014 at 1:10 AM, Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org wrote:
Reproduced and fixed: https://jira.codehaus.org/browse/JBEHAVE-1041
Can you try out latest snapshot
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 of varying from 1-10 minutes, they say the
execute in
Typically, you'd use a DI container to achieve this, via the
corresponding implementation of the InjectableStepsFactory.
On 20/08/2014 22:23, Chad Wilson wrote:
Hello all,
I'm not sure if I'm missing something here. According to the
documentation in order to register Step class instances,
Could you provide a simple example reproducing this behaviour?
On 11/08/2014 18:10, Brent Barker wrote:
Hi,
When executing reports in multiple threads, the execution times are
not correct. Instead of varying from 1-10 minutes, they say the
execute in microseconds (which i know is not the
Hi Brent,
this feature is not currently supported.It actually does a first
pass trying to match the story and then a second pass trying to match
the scenarios. It may not be the best way to do it so we could rethink
it trying do match the scenarios directly and inherit from the story
Hi,
Currently the timeout is global, not per story. If the docs suggest
otherwise, it was not intended. Correspondingly only a single
storyTimeoutInSecs parameter is provided.
Could you please create a JIRA issue detailing your usecase for the improvement
to make this story specific? How
The recommended way is to implement your own MetaMatcher.
Currently, you 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
Do you mean that jbehave-web somehow causes this issue in the 4.x
branch because of WIP?
By the way, when do you expect that the 4.x branch will become non-beta?
On Mon, Jun 30, 2014 at 1:21 PM, Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org wrote:
Thanks
.
On Mon, Jun 30, 2014 at 1:23 PM, Mauro Talevi mauro.tal...@aquilonia.org
wrote:
Not sure I understand. That's the nature of Java annotations.
On 30 Jun 2014, at 09:52, Hans Schwäbli bugs.need.love@gmail.com
wrote:
I have subclassed WebDriverScreenshotOnFailure and overridden
Can you please raise a JIRA issue for this so it doesn't get lost in
translation? :-)
On 24 Jun 2014, at 08:40, Hans Schwäbli bugs.need.love@gmail.com wrote:
It also occurs with 4.0-beta-8.
Did you have a chance to reproduce this issue with the information I posted
before?
On
Can you share a sample project with the configuration that you're using?
On 23/06/2014 00:56, Jonathan Gray wrote:
Hi,
I have a multi-module project which looks something
like the following (it happens to be Maven based).
project
- pom.xml
- app
+- pom.xml
- app-test
+- pom.xml
If I run
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 similar to this:
Meta:
@bug JBEHAVE-281
The issue is when I try to filter on that, using
-bug JBEHAVE-281
Applied with thanks.
On 18/06/2014 08:53, Hans Schwäbli wrote:
I attached a patch for this in this email (for 4.x branch).
On Wed, Jun 11, 2014 at 11:41 AM, Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org wrote:
Lazy init may still have some teething issues
of July.
On Wed, May 21, 2014 at 8:50 AM, Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org wrote:
Sold! To the German-speaking gentleman at the back of the room :-)
On 20/05/2014 21:00, Mirko Friedenhagen wrote:
Hans,
I stand corrected
Use scopetest/scope
On 17 Jun 2014, at 20:51, Brent Barker brentbark...@gmail.com wrote:
I am trying to use the Maven plugin for StoryMapping found here:
http://jbehave.org/reference/stable/story-mapping.html
However, it appears that the include tag only looks in src/main/java/
This
Lazy init may still have some teething issues. Please provide a patch.
On 11 Jun 2014, at 10:46, Hans Schwäbli bugs.need.love@gmail.com wrote:
Hello Mauro,
today I had a NullPointerException at
org.jbehave.core.configuration.Configuration.doDryRun(Boolean) with JBehave
beta-6.
Try adding the dependency at plugin level:
http://jbehave.org/reference/stable/maven-goals.html
On 10 Jun 2014, at 10:53, Jonathan Gray jonny.g...@gmail.com wrote:
Hi,
I'm currently seeing the following error when trying to run JBehave using
the maven plugin against a Spring Batch
Can you provide a sample project?
On 3 Jun 2014, at 18:36, Corbin, J.D. jd.cor...@pearson.com wrote:
I am using the maven-failsafe-plugin (as opposed to the jbehave-maven-plugin)
to run our JBehave integration tests. I appears to run the test fine, but
when there is an error it goes
it to be non-agile in its full extent. I take only the good from
it.
On Tue, May 20, 2014 at 8:42 AM, Mauro Talevi mauro.tal...@aquilonia.org
wrote:
So, what's the consensus then with the keywords?
On 16/05/2014 18:42, Mauro Talevi wrote:
I'll defer to whatever you guys decide is best. We can
So, what's the consensus then with the keywords?
On 16/05/2014 18:42, Mauro Talevi wrote:
I'll defer to whatever you guys decide is best. We can always change
it later.
On 15/05/2014 18:27, Mirko Friedenhagen wrote:
Hans,
I am not sure I agree :-). JEDES would be EVERY IMO.
According
It's a design philosophy ... with its pros and cons. The risk of
creating a uber class is that you loose touch of what configuration is
relevant to what component.
But in fact, the Configuration class allows you access to all the
different bits, the Controls, the Builders etc ... so that
be Ergebnis FEHLER.
Maybe some other German speaking guys can share their opinions
about a translation for ANY and FAILURE?
On Thu, May 15, 2014 at 12:08 AM, Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org
wrote:
There was an issue
Mauro Talevi mauro.tal...@aquilonia.org
mailto:mauro.tal...@aquilonia.org:
You need a space after the !-- (the comment keyword is treated
like at any other keyword, thus separated by a space from the
comment)
On 13/05/2014 13:51, Hans Schwäbli wrote:
In 4.x branch comments
You need a space after the !-- (the comment keyword is treated like at
any other keyword, thus separated by a space from the comment)
On 13/05/2014 13:51, Hans Schwäbli wrote:
In 4.x branch comments doen't seem to be allowed where they used to be
allowed in version 3.x.
Lets take this example
concerning the problem with the examples table.
Thank you!
But there is a problem with comments. I will write a posting just on that.
On Thu, May 8, 2014 at 10:51 AM, Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org wrote:
No, a new beta has not been deployed yet
/content/groups/public/org/jbehave/jbehave-core/4.0-beta-7/
The last snapshot there is from 2nd of May.
The same snapshot date is on:
http://mvnrepository.com/artifact/org.jbehave/jbehave-maven-plugin/4.0-beta-7/
On Wed, May 7, 2014 at 11:25 PM, Mauro Talevi mauro.tal...@aquilonia.org
wrote
Yes, it looks likely to be unrelated to given stories and such.
Could you please add a scenario reproducing the behaviour to the
meta_filtering.story in the core examples (preferably in English)?
Does it work with 3.x?
On 06/05/2014 11:34, Hans Schwäbli wrote:
I already use
Use StoryControls().doIgnoreMetaFiltersIfGivenStory(true)
On 5 May 2014, at 15:33, Hans Schwäbli bugs.need.love@gmail.com wrote:
I discovered an unexpected behavior when I used meta filtering and a given
story.
The meta filter looks like this: +component sales
This runs a story
Please don't address emails to individuals and only use the mailing lists.
On 5 May 2014, at 11:33, Kaustubh Joshi kashu.jo...@gmail.com wrote:
Hi Dev/Jbehave users,
Sorry to bother again!
I wanted to incorporate Grid feature in selenium based Jbehave project but
currently facing
The examples form an integral part of the project, ensuring the correct
behaviour of the releasable modules. They're not just examples, but
more akin to acceptance/integration tests.
If you are looking for examples that are not connected to the code, then
the jbehave-tutorial is place to
Hi Hans,
the issue has been noted and fixed. The given stories were only
executed at scenario level but not at story level.
A new 4.0-beta-7 is being released.
Cheers
On 02/05/2014 11:36, Hans Schwäbli wrote:
Somehow GivenStories does not work as expected in the 4.x branch. It
is not
The unbearable emptiness of being :-)
The idea is to try and encourage partial story writing. E.g. once
might only write a description and a narrative, but not yet have any
scenarios to add.
If one write a scenario though, at least one step must be present.
We could add a warning saying
The meta at story level is always merged with the meta at scenario level.
This is why only the resulting meta is reported.
We could add the reporting of story level meta, but what is your use-case?
On 02/05/2014 14:22, Hans Schwäbli wrote:
org.jbehave.core.reporters.StoryReporter contains a
ignore/ignore
/action
/pluginExecution
/pluginExecutions
/lifecycleMappingMetadata
On Mon, Apr 28, 2014 at 11:02 PM, Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org wrote:
Yes, the m2e plugin is very annoying in this. IMO it's one
It's rather debatable whether one sounds more natural or technical than
the other. Also, background tends to suggest concurrency - which is
not the case.
In any case, it's all subjective. If you prefer, you can configure
your own custom company locale (akin to a new language) with the
Yes, the m2e plugin is very annoying in this. IMO it's one of the
worst design decisions they've made when migrating from the original
m2eclipse plugin. But with recent versions, Eclipse allows you to mark
as ignored these errors without modifying the pom.xml. The feature is
marked as
Yes a Codehaus Confluence wiki space exists for JBehave and can be used
for user contributions.
We'd need to check on permissions and all that for contributors.
On 28/04/2014 17:00, Mirko Friedenhagen wrote:
Hello,
what about http://docs.codehaus.org/display/JBEHAVE/? I do not know
about the
@AfterScenario supports the variable uponOutcome to determine if the
scenario has failed or not.
Else you can parse the XML of the story and extract the scenario info.
On 10/04/2014 13:42, Hans Schwäbli wrote:
I achieved to create Java classes which can export test results into
HP Quality
Could you please raise a JIRA issue for this?
On 28/03/2014 11:59, Hans Schwäbli wrote:
I could cache the embedder myself by using lazy initialization in my
class which extends JUnitStories.
But that has a side effect: the meta filtering does not work then for
some unknown reason.
On Wed,
There is already a separate project for this:
https://github.com/jbehave/jbehave-site/tree/master/site-frontend/src/site/content
It is the overall doc front-end published to jbehave.org. There we can
develop a less-technical and more user-oriented (cross module,
core/web/etc ...)
PropertyWebDriverProvider();
2.How can i add capabilities to the driver which is instantiated?
3.How can i instantiate a remote webdriver?
4. Is there a way to pass the browsername as parameter to driver?
Thanks in advance.
On Wed, Mar 12, 2014 at 1:45 PM, Mauro Talevi
mauro.tal...@aquilonia.org
){
manage().timeouts().implicitlyWait(35, TimeUnit.SECONDS);
findElement(By.xpath(locator.getLocator().toString())).click();
}
}
Or Shd i go ahead like etsy.com http://etsy.com example.Please suggest.
On Thu, Mar 13, 2014 at 4:45 PM, Mauro Talevi
mauro.tal...@aquilonia.org
run my testcases , I need to run macro
on excel ,which will fill in the details into excel from db.
Can this be done using jbehave.
On Tue, Mar 11, 2014 at 5:46 AM, Mauro Talevi mauro.tal...@aquilonia.org
wrote:
http://jbehave.org/reference/stable/parametrised-scenarios.html
On 11/03
Hi Andreas,
it does seem a bug, which needs further investigation. Please raise a
JIRA issue and attach project.
If the step is not matched is should provide a pending method stub with
the real annotation, e.g. @Given.
It's a smell, probably why it's not matching the step.
In the mean
Latest master also builds with mvn 3.1+
Tested on OSX, Linux and Windows.
On 8 Mar 2014, at 16:08, Mauro Talevi mauro.tal...@aquilonia.org wrote:
I've tested the build starting from an empty Maven repo with Maven
3.0.5 and it works fine.
On the other hand, it fails with Maven
i accomplish that.
Thanks in advance.
On Mon, Mar 3, 2014 at 2:29 PM, Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org wrote:
1. You can implement your own ViewGenerator to store to DB
2. It's possible, but you need to pass it to the ViewGenerator
via
http://jbehave.org/reference/stable/parametrised-scenarios.html
On 11/03/2014 01:15, Mauro Talevi wrote:
The parametrised scenario does allow to repeat the scenario for each
row of the Examples table. The table can be read from an external CSV
file.
Was this the question? If not, can you
I
can raise the JIRA issue according to
http://jbehave.org/reference/stable/how-to-contribute.html
Thanks, all. Have a great weekend.
Best regards, best wishes,
Josef
*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Freitag, 7. März 2014 09:17
*To:* user@jbehave.codehaus.org
... it is downloading a
bunch of jars now.
RTFM. :)
Thanks,
Craig
*From:* Mauro Talevi mauro.tal...@aquilonia.org
*To:* user@jbehave.codehaus.org user@jbehave.codehaus.org
*Sent:* Friday, March 7, 2014 12:53 PM
*Subject:* Re
As of 3.9 JDK 1.7 is required to build (JBEHAVE-913).
JDK 1.5+ is still supported at runtime.
Cheers
On 7 Mar 2014, at 17:36, Craig Comstock craig_comst...@yahoo.com wrote:
I'm having a hard time figuring out how to get started with jbehave. The two
examples of setup I see are:
... FAILURE
[1:38.787s]
[INFO] JBehave Weld Example .. FAILURE [0.822s]
Cheers,
J
On 7 March 2014 08:20, Mauro Talevi mauro.tal...@aquilonia.org wrote:
Please refrain from this unpleasant abusive rant.
Learn some netiquette and you'll find
I would recommend not managing page objects directly in your DI
container. Rather having a PageObjectFactory that you inject in all
your steps classes.
Have a look at the tutorial for an example:
https://github.com/jbehave/jbehave-tutorial/tree/master/etsy-selenium/java-spring
It uses
Yes, it should be possible provided the candidate steps are collected before
the composite steps.
You need to ensure this in your steps factory. Try putting the composite step
in a separate steps class.
Else please attach a sample project reproducing the issue to a new JIRA.
On 3 Mar
cannot depend
in Maven since it is not in the Maven repository.
Maybe CoreStories works only for 3.10-SNAPSHOT?
I have to figure this out. It is not so easy with stuggling with Maven and
Java code at the same time to get it working.
2014-02-20 18:53 GMT+01:00 Mauro Talevi mauro.tal
It's a bug. The lifecycle phases should be applied before/after each
example scenario.
Can you please raise a JIRA issue for this?
On 24/02/2014 13:33, Bernardo Pinto wrote:
I have the following story:
Meta: Story proof of concept
Lifecycle:
Before:
Given I have a bank account
And my
CoreStories has a working example.
On 20 Feb 2014, at 16:56, Hans Schwäbli bugs.need.love@gmail.com wrote:
Yes, I want to show the running progress like I could do with
SeleniumStepMonitor.
I try to figure out how to use that new way.
2014-02-20 1:07 GMT+01:00 Mauro Talevi
with JBehave 4. Has something changed with how the
StepMonitor is configured or something like that? It seems to use
MatchingStepMonitor or NullStepMonitor instead of SeleniumStepMonitor.
2014-02-19 9:24 GMT+01:00 Mauro Talevi mauro.tal...@aquilonia.org
mailto:mauro.tal...@aquilonia.org
Configuration.storyReporterBuilder().withFailureTrace(true)
On 13 Feb 2014, at 13:41, Hans Schwäbli bugs.need.love@gmail.com wrote:
If an exception occurs while a step is being executed, JBehave only prints
the type of exception and its message.
It does not print the stacktrace,
Wrap in quotes: When a client posts a response pattern of '1,0,0,0,0'
@When(a client posts a response pattern of '$value')
public void whenAClientPostsValue(String value){
}
The same applies if you want to have a value with spaces.
On 13/02/2014 21:53, Corbin, J.D. wrote:
I have a scenario
into the step method instead of the actual
values from the examples table.
I hope you can help me to achieve my goal.
2014-02-06 Mauro Talevi mauro.tal...@aquilonia.org:
Hi
what is the stated intention here? You want two steps to match the same
method with different parameter names
Hi
what is the stated intention here? You want two steps to match the
same method with different parameter names?
Can you please provide a sample project - inclusive of textual stories
and steps class that reproduces your issue?
Thanks
On 06/02/2014 16:52, Hans Schwäbli wrote:
I have
You'd want to use parametrised scenarios when there is a need to repeat the
execution of the scenario for different combinations of parameters.
Using it with only row of data is redundant and impacts readability.
If you want to avoid specifying the username or other reusable parameter you
More generally, you could extend JUnitStories to provide a common configuration
and steps context to different set of stories.
On 5 Feb 2014, at 11:29, Hans Schwäbli bugs.need.love@gmail.com wrote:
Great idea, thank you!
As it seems the JBehave editor uses the input from the
);
//resetting code here
}
else
logger.debug([resetAcctPolsToDefaulsOnFailure] MetaTag
resetVipAcctPolsToDefaulsOnFailure [{}] NOT RESETING VIP Account tab policies
back to default, resetVipAcctPolsToDefaulsOnFailure);
}
Thanks,
Enrique
From: Mauro Talevi [mailto:mauro.tal
:21 AM, Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org wrote:
Use annotation specifying the scenario type
@BeforeScenario(uponType=ScenarioType.EXAMPLE)
Cheers
On 24/01/2014 23:14, Corbin, J.D. wrote:
We are using the tabular scenario format
Use annotation specifying the scenario type
@BeforeScenario(uponType=ScenarioType.EXAMPLE)
Cheers
On 24/01/2014 23:14, Corbin, J.D. wrote:
We are using the tabular scenario format to run multiple sets of data
through a single jbehave scenario using the Examples: tabular format.
We are using
a feature list for 4.0? Also do you have an ETA of a non Beta release?
Thanks,
Enrique
-Original Message-
From: Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
Sent: Sunday, January 19, 2014 8:42 AM
To: user@jbehave.codehaus.org
Subject: Re: [jbehave-user] Differentiating between test
JBehave supports the definition of a custom and configurable
FailureStrategy, which defaults to RethrowingFailure.
You can provide your own implementation which can check if the Throwable
is an UnexpectedContentException or not and decide how to handle it,
e.g. log a message and swallow the
1 - 100 of 495 matches
Mail list logo
