from:"mauro"

Title: Message Title










 

 Mauro Talevi created an issue


















 JBehave /  JBEHAVE-1039



  Scenarios not allowed by filter are not skipped and cause NPEs 










Issue Type:

  Bug




Assignee:

 Mauro Talevi




Created:


 16/Aug/14 8:38 AM




Fix Versions:


 4.0




Priority:

  Major




Reporter:

 Mauro Talevi












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1039) Scenarios not allowed by filter are not skipped and cause NPEs

Title: Message Title










 

 Mauro Talevi updated an issue


















 JBehave /  JBEHAVE-1039



  Scenarios not allowed by filter are not skipped and cause NPEs 










Change By:

 Mauro Talevi




Attachment:

 metatags.zip









 Onlyoccursin4.xduringtheexecutionofthePerformableStory.












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1039) Scenarios not allowed by filter are not skipped and cause NPEs

Title: Message Title










 

 Mauro Talevi resolved an issue as Fixed


















 JBehave /  JBEHAVE-1039



  Scenarios not allowed by filter are not skipped and cause NPEs 










Change By:

 Mauro Talevi




Resolution:

 Fixed




Status:

 Open Resolved












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1037) Story duration timeout occurs for not started story

Title: Message Title










 

 Mauro Talevi commented on an issue


















  Re: Story duration timeout occurs for not started story 










Is the time spent in the @Before methods such that it could account for the timeout? 
From the execution point of view, a story duration also includes all before and after steps, so if the before steps take a long time the story itself may not start at all. 
Could you please provide a sample project that reproduces this behaviour?












   

 Add Comment

























 JBehave /  JBEHAVE-1037



  Story duration timeout occurs for not started story 







 Some time (useStoryTimeoutInSecs) after starting my tests web browser is closed with warning [WARNING] Story com/sample/qa/stories/login.story duration of 101 seconds has exceeded timeout of 100 seconds.  No one executed story exceed this time. This is even before login.story execution. The clue is that the story contains all @Before and @After method...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http

[jbehave-dev] [jira] (JBEHAVE-1038) Unable to resolve dependencies using ANT

Title: Message Title










 

 Mauro Talevi updated an issue


















 JBehave /  JBEHAVE-1038



  Unable to resolve dependencies using ANT 










Change By:

 Mauro Talevi




Affects Version/s:

 4.x




Fix Version/s:

 3.9.4












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-scm] [scm-core][1/1] JBEHAVE-1038: Changed Atlassian URL.

2014-08-15 Thread Mauro Talevi

commit a1f244008e3d6d9dcdf949615fda55239be39b9d
Author: Mauro Talevi mauro.tal...@aquilonia.org
AuthorDate: Fri, 15 Aug 2014 15:06:43 +0200
Commit: Mauro Talevi mauro.tal...@aquilonia.org
CommitDate: Fri, 15 Aug 2014 15:06:43 +0200

JBEHAVE-1038:  Changed Atlassian URL.

diff --git a/settings.xml b/settings.xml
index 528f62c..f99454e 100755
--- a/settings.xml
+++ b/settings.xml
@@ -49,13 +49,13 @@
   repositories
 repository
   idatlassian/id
-  urlhttp://maven.atlassian.com/public/url
+  urlhttps://maven.atlassian.com/content/groups/public//url
 /repository
   /repositories
   pluginRepositories
 pluginRepository
   idatlassian/id
-  urlhttp://maven.atlassian.com/public/url
+  urlhttps://maven.atlassian.com/content/groups/public//url
 /pluginRepository
   /pluginRepositories
 /profile

[jbehave-scm] [scm-core/jbehave-4.x][1/1] JBEHAVE-1038: Changed Atlassian URL.

2014-08-15 Thread Mauro Talevi

commit 77c5c62ea28a003571d6bec4669f5ae7d5e9f09b
Author: Mauro Talevi mauro.tal...@aquilonia.org
AuthorDate: Fri, 15 Aug 2014 15:06:43 +0200
Commit: Mauro Talevi mauro.tal...@aquilonia.org
CommitDate: Fri, 15 Aug 2014 15:07:26 +0200

JBEHAVE-1038:  Changed Atlassian URL.

diff --git a/settings.xml b/settings.xml
index 528f62c..f99454e 100755
--- a/settings.xml
+++ b/settings.xml
@@ -49,13 +49,13 @@
   repositories
 repository
   idatlassian/id
-  urlhttp://maven.atlassian.com/public/url
+  urlhttps://maven.atlassian.com/content/groups/public//url
 /repository
   /repositories
   pluginRepositories
 pluginRepository
   idatlassian/id
-  urlhttp://maven.atlassian.com/public/url
+  urlhttps://maven.atlassian.com/content/groups/public//url
 /pluginRepository
   /pluginRepositories
 /profile

[jbehave-dev] [jira] (JBEHAVE-1038) Unable to resolve dependencies using ANT

Title: Message Title










 

 Mauro Talevi resolved an issue as Fixed



















Applied URL changed as suggested, with thanks.









 JBehave /  JBEHAVE-1038



  Unable to resolve dependencies using ANT 










Change By:

 Mauro Talevi




Resolution:

 Fixed




Assignee:

 MauroTalevi




Status:

 Open Resolved












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1037) Story duration timeout occurs for not started story

Title: Message Title










 

 Mauro Talevi commented on an issue


















  Re: Story duration timeout occurs for not started story 










Does this occur with 3.9.x as well?












   

 Add Comment

























 JBehave /  JBEHAVE-1037



  Story duration timeout occurs for not started story 







 Some time (useStoryTimeoutInSecs) after starting my tests web browser is closed with warning [WARNING] Story com/sample/qa/stories/login.story duration of 101 seconds has exceeded timeout of 100 seconds.  No one executed story exceed this time. This is even before login.story execution. The clue is that the story contains all @Before and @After method...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1036) StoryReporterBuilder fails to parse test results if story has GivenStories

Title: Message Title










 

 Mauro Talevi commented on an issue


















  Re: StoryReporterBuilder fails to parse test results if story has GivenStories 










Rather than providing a set of morsels of code and configuration, it'd be much easier if you could provide a simple Maven sample project that reproduced this behaviour. 












   

 Add Comment

























 JBehave /  JBEHAVE-1036



  StoryReporterBuilder fails to parse test results if story has GivenStories 







 In case of story with GivenStories JBehave raport is broken. Although few scenarios has been successfully performed - Scenarios and Steps are missing. Duration is improperly set to zero.   {code:title=Example of problematic story:|borderStyle=solid}  @author Przemyslaw Kwiecien  @organization Example Organization Systems Ltd.   GivenStorie...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: [jbehave-dev] skip scenario based on tags

2014-08-14 Thread Mauro Talevi

Hi Ajay

Thanks for the project. I was able to reproduce the problem which is in effect 
present when using filters with the 4.0 code base.

Need to look into it to find the root cause.   

In the meantime you can use latest 3.9.x release.

Cheers, M

 On 14 Aug 2014, at 02:00, अजय सिंह sir...@gmail.com wrote:
 
 
 Hi Mauro,
 Thanks for your reply
 Please find the project attached
 
 Thanks
 Ajay
 
 
 On Wed, Aug 13, 2014 at 5:01 PM, Mauro Talevi mauro.tal...@aquilonia.org 
 wrote:
 The error does not seem related to meta filters.   But you'll need to 
 provide a way for us to reproduce the issue because it's not possible to 
 help you otherwise. 
 
 Can you share your Maven project reproducing the behaviour?
 
 
 On 13/08/2014 01:56, अजय सिंह wrote:
 
 
 Hi I have three scenario and i would like to run scenarios in different env 
 based on the tags.
 
 I have tagged my 3 scenario as 
 
 @env SIT [to run in SIT]  //.scenario1
 @env QA [to run in QA]  //.scenario2
 @env SITQA [to run in both]//.scenario3
 
 and in my meta filter i use
 metaFilters metaFilter-env QA/metaFilter  /metaFilters
 
 With these i get following exceptions [logs attached]
 (BeforeStories)
 
 [INFO] Running story org/test/sample/stories/my.story
 
 (org/test/sample/stories/my.story)
 Scenario: this scenario should run in SIT
 Given I am a SIT step
 
 Scenario: this scenario should run in QA
 [WARNING] Failed to run story org/test/sample/stories/my.story
 org.jbehave.core.failures.UUIDExceptionWrapper: 
 java.lang.NullPointerException
  at 
 org.jbehave.core.embedder.PerformableTree.perform(PerformableTree.java:366)
  at 
 org.jbehave.core.embedder.StoryManager$EnqueuedStory.call(StoryManager.java:238)
  at 
 org.jbehave.core.embedder.StoryManager$EnqueuedStory.call(StoryManager.java:217)
  at java.util.concurrent.FutureTask.run(FutureTask.java:262)
  at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
  at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
  at java.lang.Thread.run(Thread.java:745)
 
 
 
 Can anyone explain me whats wrong or how can i achieve this including 
 excluding scenario based on tags ?
 
 Thanks
 Ajay
 
 
 
 -
 To unsubscribe from this list, please visit:
 
 http://xircles.codehaus.org/manage_email
 
 metatags.zip
 
 -
 To unsubscribe from this list, please visit:
 
http://xircles.codehaus.org/manage_email

Re: [jbehave-dev] skip scenario based on tags

2014-08-13 Thread Mauro Talevi

The error does not seem related to meta filters.   But you'll need to 
provide a way for us to reproduce the issue because it's not possible to 
help you otherwise.


Can you share your Maven project reproducing the behaviour?

On 13/08/2014 01:56, ???  wrote:



Hi I have three scenario and i would like to run scenarios in 
different env based on the tags.


I have tagged my 3 scenario as

@env SIT [to run in SIT]  //.scenario1
@env QA [to run in QA]  //.scenario2
@env SITQA [to run in both]//.scenario3

and in my meta filter i use
metaFilters metaFilter*-env QA*/metaFilter  /metaFilters

With these i get following exceptions [logs attached]
/(BeforeStories)/
/
/
/[INFO] Running story org/test/sample/stories/my.story/
/
/
/(org/test/sample/stories/my.story)/
/Scenario: this scenario should run in SIT/
/Given I am a SIT step/
/
/
/Scenario: this scenario should run in QA/
/[WARNING] Failed to run story org/test/sample/stories/my.story/
/org.jbehave.core.failures.UUIDExceptionWrapper: 
java.lang.NullPointerException/
/at 
org.jbehave.core.embedder.PerformableTree.perform(PerformableTree.java:366)/
/at 
org.jbehave.core.embedder.StoryManager$EnqueuedStory.call(StoryManager.java:238)/
/at 
org.jbehave.core.embedder.StoryManager$EnqueuedStory.call(StoryManager.java:217)/

/at java.util.concurrent.FutureTask.run(FutureTask.java:262)/
/at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)/
/at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)/

/at java.lang.Thread.run(Thread.java:745)/



Can anyone explain me whats wrong or how can i achieve this including 
excluding scenario based on tags ?


Thanks
Ajay



-
To unsubscribe from this list, please visit:

 http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-712) Spaces in path breaks StoryFinder().findPaths()

2014-08-11 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue


















  Re: Spaces in path breaks StoryFinder().findPaths() 










Can you provide an example or a unit test reproducing the problem?












   

 Add Comment

























 JBehave /  JBEHAVE-712



  Spaces in path breaks StoryFinder().findPaths() 







 Constructions like:  ListString storyPaths = new StoryFinder().findPaths(codeLocationFromClass(getClass()), **/*.story, **/*examples.story);  or  ListString storyPaths = new StoryFinder().findPaths(codeLocationFromPath(somePath), **/*.story, **/*examples.story);  doesn't work when there are spaces in a path (which are replaced to %20).   An...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: [jbehave-dev] ThreadLocal in FluentWebDriverPage

2014-07-31 Thread Mauro Talevi

Hi Emanuel,

thanks for providing this example. The one WebDriver instance is
correctly managed in the WebDriverProvider.end() method.

The FluentWebDriver instances are not managed in the same way - they are
not WebDriver instances and there is no lifecycle management. There
is an instance created for each page, each using the same WebDriver
instance as delegate.

I'm not sure this constitutes a memory leak, simply that the instances
are not removed at the end of the story execution. But that could
easily apply to other objects as well.

Are you experiencing any specific issues as a consequence of this?If
so, I'd would add a FluentLifecycleSteps class method that finds the
ThreadLocal instances of FluentWebDriver and nullifies them, and we can
annotate it @AfterStory.

Cheers

On 30/07/2014 21:39, Emanuel Campolo wrote:

Hi Mauro,

I could reproduce the memory leak. To do that, I created a project
from the jbehave-web archetype and made the some modifications in
order to get some logs.
I also refactored some of the page objects since the default test
cases had some errors due to etsy home page modifications.

This is the project:
https://github.com/emacampolo/etsy-jbehave/tree/jbehave-web-possible-memory-leak

And this is the class that prints the logs:
https://github.com/emacampolo/etsy-jbehave/blob/jbehave-web-possible-memory-leak/src/main/java/org/jbehave/tutorials/etsy/steps/JournaledStoriesSteps.java

Below you can find the output (I print all the ThreadLocal instances
that are subclasses of WebDriver or FluentWebDriver).

*Narrative:*
*In order to show the browsing cart functionality*
*As a user*
*I want to browse in a gallery*
*Scenario: Browsing around the site for items*

*LOGGING BEFORE SCENARIO*
*
*
*Thread name: main*
*DoublyOverriddenFirefoxDriver: firefox on LINUX
(eea68437-dfb6-4783-9ebf-d3b2c95c9f28)*

*Given I am on etsy.com http://etsy.com*
*When I want to browse through an art gallery*
*When I want to buy something from etsy.com http://etsy.com*
*When I want to browse the Art*
*When I choose the first art gallery*
*Then results will be displayed in the gallery*
*
*

*LOGGING BEFORE CALLING END()*
*
*
*Thread name: main*
*org.seleniumhq.selenium.fluent.FluentWebDriver@1570e827*
*Thread name: main*
*org.seleniumhq.selenium.fluent.FluentWebDriver@27996370*
*Thread name: main*
*org.seleniumhq.selenium.fluent.FluentWebDriver@474f625f*
*Thread name: main*
*org.seleniumhq.selenium.fluent.FluentWebDriver@2cc36f8c*
*Thread name: main*
*DoublyOverriddenFirefoxDriver: firefox on LINUX
(eea68437-dfb6-4783-9ebf-d3b2c95c9f28)*

*
*
*[INFO] 2 stories excluded by filter: +category browsing*
*
*
*
*
*(AfterStories)*

*LOGGING AFTER STORIES*
*
*
*Thread name: main*
*org.seleniumhq.selenium.fluent.FluentWebDriver@1570e827*
*Thread name: main*
*org.seleniumhq.selenium.fluent.FluentWebDriver@27996370*
*Thread name: main*
*org.seleniumhq.selenium.fluent.FluentWebDriver@474f625f*
*Thread name: main*
*org.seleniumhq.selenium.fluent.FluentWebDriver@2cc36f8c*

As you can see, by the time the suite is over, there are 4
FluentWebDriver instances (one for each page object that is created)
attached to the current thread.
On the other hand, you may notice that the
*DoublyOverriddenFirefoxDriver *is removed correctly.
There are a couple of approaches to solve this. First, let's validate
this issue.

Note: If you want to run it, please use the following filter since the
other test cases seems not to be working

mvn clean install -Dmeta.filter=+category browsing

2014-07-30 13:47 GMT-03:00 Mauro Talevi mauro.tal...@aquilonia.org
mailto:mauro.tal...@aquilonia.org:

It's your right to use alternative implementations, but at least
the interfaces should be the same and the maven dependencies declared.

If you find there's a bug in an implementation, the best way to
address it is to provide a same project that reproduces it and
perhaps a patch for it.

On 30/07/2014 18:21, Emanuel Campolo wrote:

Please dont get me wrong. I do want to help. I've copied some
classes because i found out that I could have memory leak issues
using the FluentWebDriverPage.
I will send you some logs using a newly created project with the
jbehave-web archetype.

On Jul 30, 2014 1:09 PM, Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org
wrote:

It seems to me that you're not even using jbehave-web.
You've copied selected classes from it into your project and

using them in a way which is different from jbehave-web, e.g.
introducing another factory abstraction.

If you'd help on using jbehave-web, including resolving
issues with its current

Re: [jbehave-dev] ThreadLocal in FluentWebDriverPage

2014-07-30 Thread Mauro Talevi


Hi,

the FluentWebDriverPage is simply a fluent-based facade using a 
FluentWebDriver.   The underlying  WebDriverProvider is the same as a 
non-fluent page and is injected in the constructor.


The PerStoryWebDriverSteps should use exactly the same underlying 
WebDriverProvider (autowired via some dependency-injection mechanism), 
so if the provider end() method is invoked you shouldn't need to do 
anything else.


Are you experiencing or noticing a particular problem?  If so, could you 
share a project that reproduced it?


Cheers

On 29/07/2014 19:14, Emanuel Campolo wrote:

Hi all !

I've added the jbehave-web module to a personal project where I use 
testng. I'm using the FirefoxWebDriverProvider to manage the webdriver 
instances, taking advantage of the ThreadLocal for multithreaded tests.
My question is, even though I call the end() method every time a test 
completes to remove the driver assigned to the current thread, i don't 
know how to the same thing to the FluentWebDriver (a thread local 
variable that the FluentWebDriverPage has).


I noticed that , for example, the PerStoryWebDriverSteps only 
executes driverProvider.end() but as in mentioned above,  i didn't 
find any clean up for the FluentWebDriver instances that 
FluentWebDriverPage creates.


Thanks in advance :)



-
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

Re: [jbehave-dev] ThreadLocal in FluentWebDriverPage

2014-07-30 Thread Mauro Talevi

It seems to me that you're not even using jbehave-web.  You've copied 
selected classes from it into your project and using them in a way which 
is different from jbehave-web, e.g. introducing another factory 
abstraction.


If you'd help on using jbehave-web, including resolving issues with its 
current implementation, we'd be happy to help.


If you're writing your own framework, then we can't help.

Cheers

On 30/07/2014 17:52, Emanuel Campolo wrote:

Hi Mauro, thanks for taking your time to reply.

I mentioned PerStoryWebDriverSteps as an example of how the framework 
cleans up the resources. In this case, when the end() method is 
invoked, the ThreadLocalWebDriver instance associated with the 
current thread is removed but, if you'd used a FluentWebDriverPage 
instead of a WebDriverPage, a ThreadLocalFluentWebDriver will not be 
eliminated from the list of thread locals.
Even though im not using the jbehave-core for running my tests, Im 
coding a lightweight selenium-based framework using testng and the 
jbehave-web project.
As you can see below, I had to re write some of the classes to solve 
this issue where resources are not being removed by 
the DelegatingWebDriverProvider (javadoc and reference to jbehave-web 
will be added):


https://github.com/emacampolo/hatchery/blob/master/src/main/java/com/hatchery/core/DefaultWebDriverProvider.java
https://github.com/emacampolo/hatchery/blob/master/src/main/java/com/hatchery/core/pages/FluentWebDriverPage.java

This is where I invoke the end() method
https://github.com/emacampolo/hatchery/blob/master/src/main/java/com/hatchery/core/Suite.java


2014-07-30 12:06 GMT-03:00 Mauro Talevi mauro.tal...@aquilonia.org 
mailto:mauro.tal...@aquilonia.org:


Hi,

the FluentWebDriverPage is simply a fluent-based facade using a
FluentWebDriver.   The underlying  WebDriverProvider is the same
as a non-fluent page and is injected in the constructor.

The PerStoryWebDriverSteps should use exactly the same underlying
WebDriverProvider (autowired via some dependency-injection
mechanism), so if the provider end() method is invoked you
shouldn't need to do anything else.

Are you experiencing or noticing a particular problem?  If so,
could you share a project that reproduced it?

Cheers


On 29/07/2014 19:14, Emanuel Campolo wrote:

Hi all !

I've added the jbehave-web module to a personal project where
I use testng. I'm using the FirefoxWebDriverProvider to manage
the webdriver instances, taking advantage of the ThreadLocal
for multithreaded tests.
My question is, even though I call the end() method every time
a test completes to remove the driver assigned to the current
thread, i don't know how to the same thing to the
FluentWebDriver (a thread local variable that the
FluentWebDriverPage has).

I noticed that , for example, the PerStoryWebDriverSteps only
executes driverProvider.end() but as in mentioned above,  i
didn't find any clean up for the FluentWebDriver instances
that FluentWebDriverPage creates.

Thanks in advance :)



-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: [jbehave-dev] ThreadLocal in FluentWebDriverPage

2014-07-30 Thread Mauro Talevi

It's your right to use alternative implementations, but at least the 
interfaces should be the same and the maven dependencies declared.


If you find there's a bug in an implementation, the best way to address 
it is to provide a same project that reproduces it and perhaps a patch 
for it.


On 30/07/2014 18:21, Emanuel Campolo wrote:


Please dont get me wrong. I do want to help. I've copied some classes 
because i found out that I could have memory leak issues using the 
FluentWebDriverPage.
I will send you some logs using a newly created project with the 
jbehave-web archetype.


On Jul 30, 2014 1:09 PM, Mauro Talevi mauro.tal...@aquilonia.org 
mailto:mauro.tal...@aquilonia.org wrote:


It seems to me that you're not even using jbehave-web. You've
copied selected classes from it into your project and using them
in a way which is different from jbehave-web, e.g. introducing
another factory abstraction.

If you'd help on using jbehave-web, including resolving issues
with its current implementation, we'd be happy to help.

If you're writing your own framework, then we can't help.

Cheers

On 30/07/2014 17:52, Emanuel Campolo wrote:

Hi Mauro, thanks for taking your time to reply.

I mentioned PerStoryWebDriverSteps as an example of how the
framework cleans up the resources. In this case, when the end()
method is invoked, the ThreadLocalWebDriver instance associated
with the current thread is removed but, if you'd used a
FluentWebDriverPage instead of a WebDriverPage, a
ThreadLocalFluentWebDriver will not be eliminated from the list
of thread locals.
Even though im not using the jbehave-core for running my tests,
Im coding a lightweight selenium-based framework using testng and
the jbehave-web project.
As you can see below, I had to re write some of the classes to
solve this issue where resources are not being removed by
the DelegatingWebDriverProvider (javadoc and reference to
jbehave-web will be added):


https://github.com/emacampolo/hatchery/blob/master/src/main/java/com/hatchery/core/DefaultWebDriverProvider.java

https://github.com/emacampolo/hatchery/blob/master/src/main/java/com/hatchery/core/pages/FluentWebDriverPage.java

This is where I invoke the end() method

https://github.com/emacampolo/hatchery/blob/master/src/main/java/com/hatchery/core/Suite.java


2014-07-30 12:06 GMT-03:00 Mauro Talevi
mauro.tal...@aquilonia.org mailto:mauro.tal...@aquilonia.org:

Hi,

the FluentWebDriverPage is simply a fluent-based facade using
a FluentWebDriver.   The underlying  WebDriverProvider is the
same as a non-fluent page and is injected in the constructor.

The PerStoryWebDriverSteps should use exactly the same
underlying WebDriverProvider (autowired via some
dependency-injection mechanism), so if the provider end()
method is invoked you shouldn't need to do anything else.

Are you experiencing or noticing a particular problem?  If
so, could you share a project that reproduced it?

Cheers


On 29/07/2014 19:14, Emanuel Campolo wrote:

Hi all !

I've added the jbehave-web module to a personal project
where I use testng. I'm using the
FirefoxWebDriverProvider to manage the webdriver
instances, taking advantage of the ThreadLocal for
multithreaded tests.
My question is, even though I call the end() method every
time a test completes to remove the driver assigned to
the current thread, i don't know how to the same thing to
the FluentWebDriver (a thread local variable that the
FluentWebDriverPage has).

I noticed that , for example, the PerStoryWebDriverSteps
only executes driverProvider.end() but as in mentioned
above,  i didn't find any clean up for the
FluentWebDriver instances that FluentWebDriverPage creates.

Thanks in advance :)



-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-scm] [scm-core/jbehave-4.0-beta-9][1/1] [maven-release-plugin] copy for tag jbehave-4.0-beta-9

2014-07-29 Thread Mauro Talevi

Tag:/strong jbehave-4.0-beta-9 (added)
Type: annotated
Commit: 356c1c1d85692ea90de467bc8cb22d0afcea8c83
Tagger: tag_info[:taggername] tag_info[:taggeremail]
Message: [maven-release-plugin]  copy for tag jbehave-4.0-beta-9

[jbehave-dev] [jira] (JBEHAVE-1035) @BeforeStory steps not performed before GivenStories

2014-07-29 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi updated an issue


















 JBehave /  JBEHAVE-1035



  @BeforeStory steps not performed before GivenStories 










Change By:

 Mauro Talevi




Affects Version/s:

 web-3.5.5




Affects Version/s:

 4.x




Fix Version/s:

 4.x




Fix Version/s:

 4.0




Summary:

 DelegateWebDriverNotFound:WebDriverhas @BeforeStorysteps not beenfoundforthisthread. performedbeforeGivenStories












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1035) @BeforeStory steps not performed before GivenStories

2014-07-29 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi resolved an issue as Fixed


















 JBehave /  JBEHAVE-1035



  @BeforeStory steps not performed before GivenStories 










Change By:

 Mauro Talevi




Resolution:

 Fixed




Assignee:

 MauroTalevi




Status:

 Open Resolved












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1035) @BeforeStory steps not performed before GivenStories

2014-07-29 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue


















  Re: @BeforeStory steps not performed before GivenStories 










4.0-beta-9 has been released. 
4.0-SNAPSHOT has also been deployed. The deployment is not automatic as yet because we need to find a way of securing the credentials on the CI server.












   

 Add Comment

























 JBehave /  JBEHAVE-1035



  @BeforeStory steps not performed before GivenStories 







 There seems to be a bug in 4.0-beta-8 concerning the usage of GivenStories.   If I have a story which uses GivenStories then I get this exception:   {noformat}  org.jbehave.web.selenium.DelegatingWebDriverProvider$DelegateWebDriverNotFound: WebDriver has not been found for this thread.  Please verify you are using the correct WebDriverProvider, with t...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1035) DelegateWebDriverNotFound: WebDriver has not been found for this thread.

2014-07-28 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue


















  Re: DelegateWebDriverNotFound: WebDriver has not been found for this thread. 










Does it happen only with GivenStories?












   

 Add Comment

























 JBehave /  JBEHAVE-1035



  DelegateWebDriverNotFound: WebDriver has not been found for this thread. 







 There seems to be a bug in 4.0-beta-8 concerning the usage of GivenStories.   If I have a story which uses GivenStories then I get this exception:   {noformat}  org.jbehave.web.selenium.DelegatingWebDriverProvider$DelegateWebDriverNotFound: WebDriver has not been found for this thread.  Please verify you are using the correct WebDriverProvider, with t...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-scm] [scm-core/jbehave-4.x][1/1] JBEHAVE-1035: Ensure @BeforeStory steps are performed before the GivenStories.

2014-07-28 Thread Mauro Talevi

commit c2f1548f0d48a301fed36d33208ab84fa62efeb5
Author: Mauro Talevi mauro.tal...@aquilonia.org
AuthorDate: Mon, 28 Jul 2014 18:05:43 +0100
Commit: Mauro Talevi mauro.tal...@aquilonia.org
CommitDate: Mon, 28 Jul 2014 18:05:43 +0100

JBEHAVE-1035:  Ensure @BeforeStory steps are performed before the 
GivenStories.

diff --git 
a/jbehave-core/src/main/java/org/jbehave/core/embedder/PerformableTree.java 
b/jbehave-core/src/main/java/org/jbehave/core/embedder/PerformableTree.java
index 6a2345e..3247b10 100644
--- a/jbehave-core/src/main/java/org/jbehave/core/embedder/PerformableTree.java
+++ b/jbehave-core/src/main/java/org/jbehave/core/embedder/PerformableTree.java
@@ -715,8 +715,10 @@ public class PerformableTree {
 State state = context.state();
 Timer timer = new Timer().start();
 try {
+beforeSteps.perform(context);
performGivenStories(context);
 performScenarios(context);
+afterSteps.perform(context);
 } finally {
 timing.setDurationInMillis(timer.stop());
 }
@@ -735,11 +737,9 @@ public class PerformableTree {
}

 private void performScenarios(RunContext context) throws 
InterruptedException {
-beforeSteps.perform(context);
 for (PerformableScenario scenario : scenarios) {
 scenario.perform(context);
 }
-afterSteps.perform(context);
 }
 
 public ListPerformableScenario getScenarios() {

[jbehave-dev] [jira] (JBEHAVE-1035) DelegateWebDriverNotFound: WebDriver has not been found for this thread.

2014-07-28 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue


















  Re: DelegateWebDriverNotFound: WebDriver has not been found for this thread. 










Please pull latest 4.x and try out snapshot.












   

 Add Comment

























 JBehave /  JBEHAVE-1035



  DelegateWebDriverNotFound: WebDriver has not been found for this thread. 







 There seems to be a bug in 4.0-beta-8 concerning the usage of GivenStories.   If I have a story which uses GivenStories then I get this exception:   {noformat}  org.jbehave.web.selenium.DelegatingWebDriverProvider$DelegateWebDriverNotFound: WebDriver has not been found for this thread.  Please verify you are using the correct WebDriverProvider, with t...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1032) Allow MetaMatcher to be injectable

2014-07-12 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi created an issue


















 JBehave /  JBEHAVE-1032



  Allow MetaMatcher to be injectable  










Issue Type:

  Improvement




Assignee:

 Mauro Talevi




Components:


 Core




Created:


 12/Jul/14 2:15 AM




Fix Versions:


 3.9.4




Priority:

  Major




Reporter:

 Mauro Talevi










To support custom implementations and extensibility of the meta matching, the MetaMatcher should be injectable and default to the implementations provided in core if not injected.












   

 Add Comment

[jbehave-dev] [jira] (JBEHAVE-1033) Add JiraMetaMatcher

2014-07-12 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi created an issue


















 JBehave /  JBEHAVE-1033



  Add JiraMetaMatcher 










Issue Type:

  New Feature




Assignee:


 Unassigned




Components:


 REST Support




Created:


 12/Jul/14 2:17 AM




Fix Versions:


 3.9.4




Priority:

  Major




Reporter:

 Mauro Talevi










A MetaMatcher that looks up a JIRA issue via REST and allows the meta if the issue is open.












   

 Add Comment

Re: [jbehave-dev] jbehave plugin configuration

2014-07-10 Thread Mauro Talevi

This should be easily achieved by providing the user the ability to 
specify the custom locale from a free-text field rather than from the 
pre-defined list.   As long as it's in the classpath it will be picked up.


Please raise a JIRA issue for this.

On 10/07/2014 20:25, fernando guallini wrote:
I think the same Brent. I use the JBehave keywords in Spanish (custom 
language, in fact), but the Eclipse plugin does not support the 
Spanish language or custom.



2014-07-10 14:50 GMT-03:00 Brent Barker brentbark...@gmail.com 
mailto:brentbark...@gmail.com:


This would be a really nice feature to have.


On Tue, Jul 8, 2014 at 8:34 AM, Frank Pedroza fpedr...@part.net
mailto:fpedr...@part.net wrote:

Custom story language... for example, I want to define
different Strings as my comments


On Tue, Jul 8, 2014 at 7:42 AM, Mauro Talevi
mauro.tal...@aquilonia.org
mailto:mauro.tal...@aquilonia.org wrote:

You've not answered my question.

What do you mean by a custom language?

On 8 Jul 2014, at 15:37, fernando guallini
fer.wa...@gmail.com mailto:fer.wa...@gmail.com wrote:


I have the same issue, Is there a way to configure
eclipse plugin with a customize language?


2014-07-08 3:57 GMT-03:00 Mauro Talevi
mauro.tal...@aquilonia.org
mailto:mauro.tal...@aquilonia.org:

Preferences  JBehave  Project Settings  Story
Language drop-down list

Or do you mean to support another language than the
one in the list?


On 07/07/2014 21:05, Frank Pedroza wrote:

Is it possible to configure the JBehave eclipse
plugin to use a different/customize 'Story Language'?

http://jbehave.org/eclipse-integration.html




-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email







-- 


Frank M. Pedroza  -  Software Engineer
Partnet  -  Development
801.708.5050 tel:801.708.5050

-
The nice part about being a pessimist is that you are
constantly being either proven right or pleasantly surprised.
-- George F. Will

Re: [jbehave-dev] jbehave plugin configuration

2014-07-08 Thread Mauro Talevi


Preferences  JBehave  Project Settings  Story Language drop-down list

Or do you mean to support another language than the one in the list?

On 07/07/2014 21:05, Frank Pedroza wrote:
Is it possible to configure the JBehave eclipse plugin to use a 
different/customize 'Story Language'?


http://jbehave.org/eclipse-integration.html




-
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-961) Customize JBehave HTML report.

2014-07-08 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue


















  Re: Customize JBehave HTML report. 










Currently, users can provide their own meta properties. 
We could allow these to also be read from other sources, e.g. env variables.












   

 Add Comment

























 JBehave /  JBEHAVE-961



  Customize JBehave HTML report. 







 Is there any way to customize HTML the way we want in JBehave? As per our project requirement, we want to add more information in HTML report such as date time, browser tested etc. We noticed HTMLoutput method in JBehave. If it is possible with this method can you please provide any good example?















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Re: [jbehave-dev] jbehave plugin configuration

2014-07-08 Thread Mauro Talevi

You've not answered my question. 

What do you mean by a custom language?

 On 8 Jul 2014, at 15:37, fernando guallini fer.wa...@gmail.com wrote:
 
 I have the same issue, Is there a way to configure eclipse plugin with a 
 customize language?
 
 
 2014-07-08 3:57 GMT-03:00 Mauro Talevi mauro.tal...@aquilonia.org:
 Preferences  JBehave  Project Settings  Story Language drop-down list
 
 Or do you mean to support another language than the one in the list?
 
 
 On 07/07/2014 21:05, Frank Pedroza wrote:
 Is it possible to configure the JBehave eclipse plugin to use a 
 different/customize 'Story Language'?
 
 http://jbehave.org/eclipse-integration.html
 
 
 -
 To unsubscribe from this list, please visit:
 
http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1028) Add support for Korean locale

2014-06-26 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue


















  Re: Add support for Korean locale  










I understand that an oriental language flow may different from a Latin-based one, but I struggle to understand what's the use of having a Korean locale with keywords in English. Then it's just as well to use the default locale. 
I think it would be beneficial to have the keywords translated in Korean, which can be used regardless of the position in the sentence. 
Then we can try to address the positioning issue separately.












   

 Add Comment

























 JBehave /  JBEHAVE-1028



  Add support for Korean locale  







 While following http://jbehave.org/reference/stable/running-examples.html page, next command failed with following message.  mvn -s settings.xml clean install -Pexamples   Tests run: 11, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.018 sec  FAILURE! - in org.jbehave.core.reporters.StoryReporterBuilderBehaviour  shouldBuildWithReporterOfDiff...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from

[jbehave-dev] [jira] (JBEHAVE-1028) Add support for Korean locale

2014-06-24 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi updated an issue


















 JBehave /  JBEHAVE-1028



  Add support for Korean locale  










Change By:

 Mauro Talevi




Summary:

 runningprofile'examples'failedduetolackofbundlefilewhen AddsupportforKorean locale ko_KR 












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1028) running profile 'examples' failed due to lack of bundle file when locale ko_KR

2014-06-24 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue


















  Re: running profile 'examples' failed due to lack of bundle file when locale ko_KR 










What's the point of adding the Korean bundle with English words? 
If you were to volunteer the bundle with the appropriate Korean translation, we'd be happy to add it. 
If you do, please remember to use Unicode chars with UTF-8 encoding. 












   

 Add Comment

























 JBehave /  JBEHAVE-1028



  running profile 'examples' failed due to lack of bundle file when locale ko_KR 







 While following http://jbehave.org/reference/stable/running-examples.html page, next command failed with following message.  mvn -s settings.xml clean install -Pexamples   Tests run: 11, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.018 sec  FAILURE! - in org.jbehave.core.reporters.StoryReporterBuilderBehaviour  shouldBuildWithReporterOfDiff...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1028) running profile 'examples' failed due to lack of bundle file when locale ko_KR

2014-06-24 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi updated an issue


















 JBehave /  JBEHAVE-1028



  running profile 'examples' failed due to lack of bundle file when locale ko_KR 










Change By:

 Mauro Talevi




Affects Version/s:

 web-3.5.5




Affects Version/s:

 3.9.4












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-987) Plugin execution not covered by lifecycle configuration

2014-06-22 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi resolved an issue as Not A Bug



















http://wiki.eclipse.org/M2E_plugin_execution_not_covered









 JBehave /  JBEHAVE-987



  Plugin execution not covered by lifecycle configuration 










Change By:

 Mauro Talevi




Resolution:

 NotABug




Fix Version/s:

 3.9.4




Status:

 Open Resolved












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-920) Allow @Before/After steps in GivenStories scenarios to not be executed

2014-06-19 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi updated an issue


















 JBehave /  JBEHAVE-920



  Allow @Before/After steps in GivenStories scenarios to not be executed 










Change By:

 Mauro Talevi




Fix Version/s:

 3.9.3




Fix Version/s:

 3.9.4












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-scm] [scm-core][1/1] Updated release notes.

2014-06-19 Thread Mauro Talevi

commit fba9013a609dc08578b609ab7edaa030a138256e
Author: Mauro Talevi mauro.tal...@aquilonia.org
AuthorDate: Thu, 19 Jun 2014 21:12:51 +0200
Commit: Mauro Talevi mauro.tal...@aquilonia.org
CommitDate: Thu, 19 Jun 2014 21:12:51 +0200

Updated release notes.

diff --git a/distribution/src/site/content/release-notes.html 
b/distribution/src/site/content/release-notes.html
index d379f47..de2f8b2 100755
--- a/distribution/src/site/content/release-notes.html
+++ b/distribution/src/site/content/release-notes.html
@@ -5,6 +5,26 @@
 /head
 body
 
+h1JBehave Core - Version 3.9.3 (Jun 19, 2014)/h1 
+
+h2Bug
+/h2
+ul
+li[a href='http://jira.codehaus.org/browse/JBEHAVE-1018'JBEHAVE-1018/a] 
- Parametrised step is  rendered incorrectly if there is more than 1 
parameter and a table 
+/li
+/ul
+
+h2Improvement
+/h2
+ul
+li[a href='http://jira.codehaus.org/browse/JBEHAVE-1014'JBEHAVE-1014/a] 
- Lifecycle steps: after upon outcome
+/li
+li[a href='http://jira.codehaus.org/browse/JBEHAVE-1017'JBEHAVE-1017/a] 
- Update JBehave Needle to support latest version of Needle4J 2.3
+/li
+li[a href='http://jira.codehaus.org/browse/JBEHAVE-1019'JBEHAVE-1019/a] 
- Allow BooleanConverter to accept Boolean.TYPE and return false for 
unknown values
+/li
+/ul
+
 h1JBehave Core - Version 3.9.2 (Apr 12, 2014)/h1 
 
 h2Bug

[jbehave-scm] [scm-core/jbehave-3.9.3][1/1] [maven-release-plugin] copy for tag jbehave-3.9.3

2014-06-19 Thread Mauro Talevi

Tag:/strong jbehave-3.9.3 (added)
Type: annotated
Commit: 642ef0ae3342d3954b352e86aecc4aab9dd6c037
Tagger: tag_info[:taggername] tag_info[:taggeremail]
Message: [maven-release-plugin]  copy for tag jbehave-3.9.3

[jbehave-scm] [scm-core/jbehave-4.x][1/1] Updated release notes.

2014-06-19 Thread Mauro Talevi

commit a8a642a9aa6e5addfed3483c8a09c399c7f14bc3
Author: Mauro Talevi mauro.tal...@aquilonia.org
AuthorDate: Thu, 19 Jun 2014 21:12:51 +0200
Commit: Mauro Talevi mauro.tal...@aquilonia.org
CommitDate: Thu, 19 Jun 2014 21:42:37 +0200

Updated release notes.

diff --git a/distribution/src/site/content/release-notes.html 
b/distribution/src/site/content/release-notes.html
index d379f47..de2f8b2 100755
--- a/distribution/src/site/content/release-notes.html
+++ b/distribution/src/site/content/release-notes.html
@@ -5,6 +5,26 @@
 /head
 body
 
+h1JBehave Core - Version 3.9.3 (Jun 19, 2014)/h1 
+
+h2Bug
+/h2
+ul
+li[a href='http://jira.codehaus.org/browse/JBEHAVE-1018'JBEHAVE-1018/a] 
- Parametrised step is  rendered incorrectly if there is more than 1 
parameter and a table 
+/li
+/ul
+
+h2Improvement
+/h2
+ul
+li[a href='http://jira.codehaus.org/browse/JBEHAVE-1014'JBEHAVE-1014/a] 
- Lifecycle steps: after upon outcome
+/li
+li[a href='http://jira.codehaus.org/browse/JBEHAVE-1017'JBEHAVE-1017/a] 
- Update JBehave Needle to support latest version of Needle4J 2.3
+/li
+li[a href='http://jira.codehaus.org/browse/JBEHAVE-1019'JBEHAVE-1019/a] 
- Allow BooleanConverter to accept Boolean.TYPE and return false for 
unknown values
+/li
+/ul
+
 h1JBehave Core - Version 3.9.2 (Apr 12, 2014)/h1 
 
 h2Bug

[jbehave-scm] [scm-core/jbehave-4.x][1/1] JBEHAVE-1002: Use lazy-loaded story controls.

2014-06-18 Thread Mauro Talevi

commit c665b3264bd53cf8d4d2f4ce449469ed322f8dec
Author: Mauro Talevi mauro.tal...@aquilonia.org
AuthorDate: Wed, 18 Jun 2014 15:37:10 +0200
Commit: Mauro Talevi mauro.tal...@aquilonia.org
CommitDate: Wed, 18 Jun 2014 15:37:10 +0200

JBEHAVE-1002: Use lazy-loaded story controls.

diff --git 
a/jbehave-core/src/main/java/org/jbehave/core/configuration/Configuration.java 
b/jbehave-core/src/main/java/org/jbehave/core/configuration/Configuration.java
index 323d16f..36c8a7e 100755
--- 
a/jbehave-core/src/main/java/org/jbehave/core/configuration/Configuration.java
+++ 
b/jbehave-core/src/main/java/org/jbehave/core/configuration/Configuration.java
@@ -175,7 +175,7 @@ public abstract class Configuration {
}
 
 public boolean dryRun() {
-return storyControls.dryRun();
+return storyControls().dryRun();
 }
 
 public StoryControls storyControls() {
@@ -317,7 +317,7 @@ public abstract class Configuration {
 }
 
 public Configuration doDryRun(Boolean dryRun) {
-this.storyControls.doDryRun(dryRun);
+this.storyControls().doDryRun(dryRun);
 return this;
 }

[jbehave-scm] [scm-core/jbehave-4.0-beta-8][1/1] [maven-release-plugin] copy for tag jbehave-4.0-beta-8

2014-06-18 Thread Mauro Talevi

Tag:/strong jbehave-4.0-beta-8 (added)
Type: annotated
Commit: 3437bc5e5f2a3611c69a4129ce3d1069c495197a
Tagger: tag_info[:taggername] tag_info[:taggeremail]
Message: [maven-release-plugin]  copy for tag jbehave-4.0-beta-8

[jbehave-dev] [jira] (JBEHAVE-1023) Improve responsiveness of editor for large projects by not recreating the same StepMatcher for every candidate step on every keystroke

Title: Message Title










 

 Mauro Talevi updated an issue


















 JBehave /  JBEHAVE-1023



  Improve responsiveness of editor for large projects by not recreating the same StepMatcher for every candidate step on every keystroke 










Change By:

 Mauro Talevi




Affects Version/s:

 eclipse-1.0




Fix Version/s:

 eclipse-1.0












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1023) Improve responsiveness of editor for large projects by not recreating the same StepMatcher for every candidate step on every keystroke

Title: Message Title










 

 Mauro Talevi resolved an issue as Fixed



















Pulled request with thanks and deployed new version.









 JBehave /  JBEHAVE-1023



  Improve responsiveness of editor for large projects by not recreating the same StepMatcher for every candidate step on every keystroke 










Change By:

 Mauro Talevi




Resolution:

 Fixed




Status:

 Open Resolved












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1022) Saucelab implementation for etsy-selenium/ java-spring project in Jbehave tutorial

Title: Message Title










 

 Mauro Talevi commented on an issue


















  Re: Saucelab implementation for etsy-selenium/ java-spring project in Jbehave tutorial 










The configuration for the SauceWebDriverProvider is in Java: 
https://github.com/jbehave/jbehave-tutorial/blob/master/etsy-selenium/groovy-pico/src/main/java/org/jbehave/tutorials/etsy/EtsyDotComStories.java
It is the same regardless of the language used for the steps and the container used to wire them up. 












   

 Add Comment

























 JBehave /  JBEHAVE-1022



  Saucelab implementation for etsy-selenium/ java-spring project in Jbehave tutorial 







 Hi,   Currently I'm able to see the saucelabs implementation only in etsy-selenium/groovy-pico project in github.   But could you please implement the same in etsy-selenium/java-spring project also.   https://github.com/jbehave/jbehave-tutorial/tree/master/etsy-selenium/java-spring   Please let us know how this is going to be work in SauceLabs for ja...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)




 












-
To unsubscribe from this list

[jbehave-dev] [jira] (JBEHAVE-889) Asynchronous cache reload