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 passwords
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:
https://groups.google.com/forum/#!forum
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 jbehave-sp
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? And=LocalizedAnd1|LocalizedAnd2
, tran, phong wrote:
Hi Mauro,
I just opened a JIRA issue as suggested.
https://jira.codehaus.org/browse/JBEHAVE-1073
Thanks again for your help!
Cheers,
Phong
*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Wednesday, April 01, 2015 5:03 PM
*To:* user
account?
Thanks,
Phong
*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Wednesday, April 01, 2015 4:03 PM
*To:* user@jbehave.codehaus.org
*Subject:* Re: [jbehave-user] Story duration are not calculated
correctly in multi-thread execution
Sure, easy enough to do!
Can you please
ork level to handle the multi-threading
> execution mode.
>
> 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 ca
e Mar 24 15:20:14 PDT 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
ger available in the stats object
(story .stats file) 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:
storyDurations.props file created with
expected story duration time now. My next question is how I can take
the information in storyDurations.props file and make them available
for access in the FreeMarker templates (.ftl) to produce the HTML views?
Thanks,
Phong
*From:*Mauro Talevi
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. S
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 jBeha
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: SAME_DATE
e row. It's actually much simpler than it sounds with
> the help of JBehave functions.
>
> Zoltan
>
>> On Thu, Jan 8, 2015 at 10:14 PM, Mauro Talevi
>> wrote:
>> Hi,
>>
>> there is currently no way to parallelise the running of the scenarios
>
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, Venka
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
that.
I am also looking forward for more contribution, but I am a beginner
in contribution for open source projects, so will take some time to
warm-up.
Regards,
rSzabi
*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Wednesday, December 17, 2014 2:19 PM
*To:* user@jbehave.codehau
Hi
I don't see any problem with the proposed solution.
Can you please contribute it following:
http://jbehave.org/how-to-contribute.html
Cheers
On 17/12/2014 08:45, RUGINA Szabolcs-Gavril wrote:
Hi guys,
I have a situation where I need to use in an examples table values
containing backsl
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 q
Hi,
candidate steps can only be set for each set of stories to run. If you
need to, you can define the steps as facades acting as a proxies towards
different actions.So in your case the loging step would invoke
different underlying APIs depending on the app it's connecting to.
Cheers
On
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 text
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 te
Hi Brent,
no, this feature is only available at scenario level. Can you not use
it restart the single scenario rather than the whole story?
If you have 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 Barke
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:
examples for the syntax.
> On 10 Oct 2014, at 08:39, kvitaliy wrote:
>
> Hi!
> Mauro, thanks a lot for response.
>
> I'm not sure I understand your second answer: its about meta-filtering or
> something else?
>
> Best regards,
> Vitaliy
>
> 09
Hi,
Answers to your questions:
1) no, there is no mechanism to skip lines in the examples table, except to
comment them (|-- prefix)
2) simply exclude the path to UserLogin.story from the execution. It will only
be looked up via the GivenStories.
Cheers
> On 9 Oct 2014, at 12:15, kvitaliy
me in another step. And that seems to fail
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
mailto:mauro.tal...@aquilonia.org>> wrote:
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 sh
llo|
(specifying a literal in the first call ("Welcome"), and specifying 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-u
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 be
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
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 c
viding you 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 be
. Because we don't know ahead 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
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'
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:
htt
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)" wrote:
>
> Thanks for your answer.
> Seems
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 annota
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 report looks correct.
I'll try to get a example project put together.
On Wed, Aug 20, 2014 at 1:10 AM, Mauro Talevi
mailto:mauro.tal...@aquilonia.org>> wrote:
Reproduced and fixed: https://jira.codehaus.org/browse/JBEHAVE-1041
Can you try out latest snapshot?
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 W
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, an
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 micr
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 case)
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 tag
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
l a class in my
local repo, but the groovy script is not able to resolve the class.
I am trying to access Jira though Rest to see if a bug for the
scenario is closed or open, and skip or run the scenario depending on
that.
On Fri, Jul 11, 2014 at 12:21 AM, Mauro Talevi
mailto:mauro.tal..
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 19:49
ilure.
Jon
On 23/06/2014 08:12, Mauro Talevi wrote:
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
text class: org.jbehave.core.context.Context
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
mailto:mauro.tal...@aquilonia.org>> wrote:
Thanks, started look
>
>
>> On Mon, Jun 30, 2014 at 1:23 PM, Mauro Talevi
>> wrote:
>> Not sure I understand. That's the nature of Java annotations.
>>
>> > On 30 Jun 2014, at 09:52, Hans Schwäbli
>> > wrote:
>> >
>> > I have subclass
Not sure I understand. That's the nature of Java annotations.
> On 30 Jun 2014, at 09:52, Hans Schwäbli wrote:
>
> I have subclassed WebDriverScreenshotOnFailure and overridden
> afterScenarioFailure(UUIDExceptionWrapper).
>
> I wondered why my class never was used. Then I discovered that I
ehaus.org/browse/JBEHAVE-1030
>
> In the second part of the article I wrote that in 4.x the context view can be
> still used like in JBehave 3.9.2. I hope that will be okay.
>
>
>> On Tue, Jun 24, 2014 at 11:33 AM, Mauro Talevi
>> wrote:
>> Can you please raise a
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 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 Mon, Jun 16, 2014 at
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 "clea
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
July.
On Wed, May 21, 2014 at 8:50 AM, Mauro Talevi
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, in this case JEDES is a
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
mailto:mauro.tal...@aquilonia.org>> wrote:
Lazy init may still have some teething issues. Please pro
Use test
> On 17 Jun 2014, at 20:51, Brent Barker 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 tag only looks in src/main/java/
>
> This is the exact maven tag I'm using:
Please provide a sample project to reproduce.
> On 11 Jun 2014, at 11:26, Hans Schwäbli wrote:
>
> Hello Mauro,
>
> I extend a class from org.jbehave.web.selenium.PerStoryWebDriverSteps where I
> want to use the methode beforeStory() for some purpose.
>
> But when I do this, the extension i
Lazy init may still have some teething issues. Please provide a patch.
> On 11 Jun 2014, at 10:46, Hans Schwäbli wrote:
>
> Hello Mauro,
>
> today I had a NullPointerException at
> org.jbehave.core.configuration.Configuration.doDryRun(Boolean) with JBehave
> beta-6.
>
> It was because th
Comment it, by prefixing it with !--
> On 10 Jun 2014, at 17:31, Frank Pedroza wrote:
>
> I don't want to skip the entire scenario, just one step.
>
>
>> On Tue, Jun 10, 2014 at 9:26 AM, Mauro Talevi
>> wrote:
>> Annotate the scenario with a meta p
Annotate the scenario with a meta property, eg @skip, and set meta filter -skip.
> On 10 Jun 2014, at 16:59, Frank Pedroza wrote:
>
> Is it possible to skip single steps of a given story/scenario? I don't think
> it is, but I'm wondering if there is a recommended approach. I have a story
> w
Try adding the dependency at plugin level:
http://jbehave.org/reference/stable/maven-goals.html
> On 10 Jun 2014, at 10:53, Jonathan Gray wrote:
>
> Hi,
>
> I'm currently seeing the following error when trying to run JBehave using
> the maven plugin against a Spring Batch project.
>
> [ERR
Can you provide a sample project?
> On 3 Jun 2014, at 18:36, "Corbin, J.D." 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 unreported. I'm
ul to some degree in its basic teachings,
I consider 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
wrote:
So, what's the consensus then with the keywords?
On 16/05/2014 18:42, Mauro Talevi wrote:
I'll defer to whatever
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 sho
We could return the File(path), that given that it'd be simply the file
of the path that you provide, what would be the advantage?
On 19/05/2014 13:28, Hans Schwäbli wrote:
I seen that it originates from Selenium in the end:
org.jbehave.web.selenium.WebDriverProvider.saveScreenshotTo(String)
B
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.
Ac
n too.
I think better would 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
mailto:mauro.tal...@aquilonia.org>>
wrote:
There
ghly.
On Tue, May 13, 2014 at 8:00 PM, Mauro Talevi
mailto:mauro.tal...@aquilonia.org>> wrote:
Cool, we'll push out new beta soon.
Can you also take the Lifecycle After upon outcome functionality
for a spin while you're at it?
On 13/05/2014 13:42, Hans Schwä
02:00 Mauro Talevi <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 doen't
s expected
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
mailto:mauro.tal...@aquilonia.org>> wrote:
No, a new beta has not been deployed yet. In t
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 (
oups/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
>> wrot
JBehave by the way.
On Tue, May 6, 2014 at 3:04 PM, Mauro Talevi
mailto: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.
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 StoryControls.doIg
Groovy meta matcher supports regex:
http://jbehave.org/reference/stable/meta-filtering.html
On 06/05/2014 08:46, Hans Schwäbli wrote:
I tried to use a regular expression as a meta info value: +component
sales|purchasing
With this I intend to run all the stories which are either declared as
"@c
Please don't address emails to individuals and only use the mailing lists.
> On 5 May 2014, at 11:33, Kaustubh Joshi wrote:
>
> Hi Dev/Jbehave users,
>
> Sorry to bother again!
>
> I wanted to incorporate Grid feature in selenium based Jbehave project but
> currently facing
> below mentioned
Use StoryControls().doIgnoreMetaFiltersIfGivenStory(true)
> On 5 May 2014, at 15:33, Hans Schwäbli 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 (lets call it sales.sto
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 sce
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 th
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 exec
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 sta
Hi,
ignorable are steps to be parsed but ignored in the execution, i.e
starting with the comment keyword (!--). These steps are not executed
but reported in the story output.
skipped steps are not used anymore - they should be deprecated and removed.
silent steps don't exist. There is a Si
On Mon, Apr 28, 2014 at 11:02 PM, Mauro Talevi
mailto:mauro.tal...@aquilonia.org>>
wrote:
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 m2e
compile
On Mon, Apr 28, 2014 at 11:02 PM, Mauro Talevi
mailto:mauro.tal...@aquilonia.org>> wrote:
Yes, the m2e plugin is very annoying in this. IMO it's one of
the worst design decisions they've made when migrating
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
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 expe
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 na
A step that is not found (or whose signature is not matched which is the same)
is considered pending. You can think pending as synonymous to not found.
Passing nulls around is not a safe nor good practice as it simply shifts the
problem without solving it. You can activate the step monitor to
st in HP QC (and perhaps also in many other
test managment tools) is best represented by a JBehave scenario.
Is it possible to configure JBehave so that it produces XML result
files per scenario?
On Thu, Apr 10, 2014 at 11:21 PM, Mauro Talevi
mailto:mauro.tal...@aquilonia
@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 Cen
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, Ma
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 ...) documentation
Parameter values are always identified by surrounding spaces. That's
why it interprets the value as "homepage_".
Your solutions seems the most logical one.
On 14/03/2014 15:44, Hans Schwäbli wrote:
I stumpled upon an issue where I cannot use the parameters as I expected.
See the example belo
or,$valueToBeSelected")
public void selects (ObjectIdentifier locator,String textToBeEntered){
manage().timeouts().implicitlyWait(35, TimeUnit.SECONDS);
findElement(By.xpath(locator.getLocator().toString())).click();
}
}
Or Shd i go ahead like etsy.com <http://etsy.com>
ider = new
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
mailto:mauro.tal...@aquilonia.o
1 - 100 of 830 matches
Mail list logo
