from:"mauro"

commit d82ba195d1087193f0f2b8743c8e48bca53f0b30
Author: Mauro Talevi 
AuthorDate: Sat, 18 Apr 2015 10:57:04 +0200
Commit: Mauro Talevi 
CommitDate: Sat, 18 Apr 2015 11:00:53 +0200

JBEHAVE-1066:  Upgraded maven dependencies.

diff --git a/pom.xml b/pom.xml
index e8fd08b..51a9b4e 100755
--- a/pom.xml
+++ b/pom.xml
@@ -93,7 +93,7 @@
 
   org.apache.maven.plugins
   maven-compiler-plugin
-  3.1
+  3.2
   
 ${jdk.version}
 ${jdk.version}
@@ -102,12 +102,12 @@
 
   org.apache.maven.plugins
   maven-enforcer-plugin
-  1.3.1
+  1.4
 
 
   org.apache.maven.plugins
   maven-surefire-plugin
-  2.17
+  2.18.1
   
 junit:junit
 
@@ -127,17 +127,17 @@
 
   org.apache.maven.plugins
   maven-surefire-report-plugin
-  2.17
+  2.18.1
 
 
   org.apache.maven.plugins
   maven-project-info-reports-plugin
-  2.7
+  2.8
 
 
   org.apache.maven.plugins
   maven-javadoc-plugin
-  2.9.1
+  2.10.3
   
 
   attach-javadoc
@@ -146,6 +146,7 @@
 jar
   
   
+false  
 
   http://java.sun.com/j2se/1.5/docs/api
 
@@ -156,7 +157,7 @@
 
   org.apache.maven.plugins
   maven-source-plugin
-  2.2.1
+  2.4
   
 
   attach-sources
@@ -170,7 +171,7 @@
 
   org.apache.maven.plugins
   maven-resources-plugin
-  2.5
+  2.7
   
 ${resource.encoding}
   
@@ -178,7 +179,7 @@
 
   org.apache.maven.plugins
   maven-release-plugin
-  2.5
+  2.5.1
   
 true
 clean install
@@ -191,22 +192,22 @@
 
   org.apache.maven.plugins
   maven-assembly-plugin
-  2.4
+  2.5.3
 
 
   org.apache.maven.plugins
   maven-dependency-plugin
-  2.8
+  2.10
 
 
   org.apache.maven.plugins
   maven-antrun-plugin
-  1.7
+  1.8
 
 
   org.apache.maven.plugins
   maven-site-plugin
-  3.3
+  3.4
 
 
   org.codehaus.mojo

[jbehave-scm] [scm-core][1/1] JBEHAVE-1066: Upgraded maven dependencies.

commit 164edafd533d05c3af22025fa0b0b948f60aa0b8
Author: Mauro Talevi 
AuthorDate: Sat, 18 Apr 2015 10:57:04 +0200
Commit: Mauro Talevi 
CommitDate: Sat, 18 Apr 2015 10:57:04 +0200

JBEHAVE-1066:  Upgraded maven dependencies.

diff --git a/pom.xml b/pom.xml
index 7ca893f..495f20b 100755
--- a/pom.xml
+++ b/pom.xml
@@ -93,7 +93,7 @@
 
   org.apache.maven.plugins
   maven-compiler-plugin
-  3.1
+  3.2
   
 ${jdk.version}
 ${jdk.version}
@@ -102,12 +102,12 @@
 
   org.apache.maven.plugins
   maven-enforcer-plugin
-  1.3.1
+  1.4
 
 
   org.apache.maven.plugins
   maven-surefire-plugin
-  2.17
+  2.18.1
   
 junit:junit
 
@@ -127,17 +127,17 @@
 
   org.apache.maven.plugins
   maven-surefire-report-plugin
-  2.17
+  2.18.1
 
 
   org.apache.maven.plugins
   maven-project-info-reports-plugin
-  2.7
+  2.8
 
 
   org.apache.maven.plugins
   maven-javadoc-plugin
-  2.9.1
+  2.10.3
   
 
   attach-javadoc
@@ -146,6 +146,7 @@
 jar
   
   
+false  
 
   http://java.sun.com/j2se/1.5/docs/api
 
@@ -156,7 +157,7 @@
 
   org.apache.maven.plugins
   maven-source-plugin
-  2.2.1
+  2.4
   
 
   attach-sources
@@ -170,7 +171,7 @@
 
   org.apache.maven.plugins
   maven-resources-plugin
-  2.5
+  2.7
   
 ${resource.encoding}
   
@@ -178,7 +179,7 @@
 
   org.apache.maven.plugins
   maven-release-plugin
-  2.5
+  2.5.1
   
 true
 clean install
@@ -190,22 +191,22 @@
 
   org.apache.maven.plugins
   maven-assembly-plugin
-  2.4
+  2.5.3
 
 
   org.apache.maven.plugins
   maven-dependency-plugin
-  2.8
+  2.10
 
 
   org.apache.maven.plugins
   maven-antrun-plugin
-  1.7
+  1.8
 
 
   org.apache.maven.plugins
   maven-site-plugin
-  3.3
+  3.4
 
 
   org.codehaus.mojo

[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time

2015-04-18 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










Hi Christopher, 
I've committed a fix to support both ant-style patterns (a la StoryFinder) and regex patterns. 
I've also updated the core examples pom.xml with story timeouts.
Can you please give it a whirl and let me know if we can resolve this issue? 












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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][2/2] JBEHAVE-833: Added StoryManagerBehaviour to unit test timeout patterns.

commit 27908fed69413ce1f95dfab71fe93b5e5d5f
Author: Mauro Talevi 
AuthorDate: Sat, 18 Apr 2015 09:33:47 +0200
Commit: Mauro Talevi 
CommitDate: Sat, 18 Apr 2015 09:33:47 +0200

JBEHAVE-833: Added StoryManagerBehaviour to unit test timeout patterns.

diff --git 
a/jbehave-core/src/test/java/org/jbehave/core/embedder/StoryManagerBehaviour.java
 
b/jbehave-core/src/test/java/org/jbehave/core/embedder/StoryManagerBehaviour.java
new file mode 100644
index 000..d9f27a6
--- /dev/null
+++ 
b/jbehave-core/src/test/java/org/jbehave/core/embedder/StoryManagerBehaviour.java
@@ -0,0 +1,57 @@
+package org.jbehave.core.embedder;
+
+import static org.hamcrest.CoreMatchers.is;
+import static org.hamcrest.MatcherAssert.assertThat;
+import static org.mockito.Mockito.mock;
+import static org.mockito.Mockito.when;
+
+import org.jbehave.core.embedder.PerformableTree.RunContext;
+import org.jbehave.core.embedder.StoryManager.EnqueuedStory;
+import org.jbehave.core.model.Story;
+import org.junit.Test;
+
+public class StoryManagerBehaviour {
+
+   private PerformableTree performableTree = new PerformableTree();
+   private RunContext context = mock(RunContext.class);
+   private EmbedderMonitor embedderMonitor = new NullEmbedderMonitor(); 
+   private EmbedderControls embedderControls = new EmbedderControls();
+   private Story story = mock(Story.class);
+
+   @Test
+   public void shouldSupportDefaultStoryTimeout(){
+   assertThat(enqueuedStory(embedderMonitor, 
story).getTimeoutInSecs(), is(300L));
+   }
+
+   @Test
+   public void shouldSupportStoryTimeoutsByPathUsingAntPatterns(){
+   
embedderControls.useStoryTimeoutInSecsByPath("**/*short*:50,**/*long*:500");
+   
when(story.getPath()).thenReturn("/path/to/a_short_and_sweet.story");
+   assertThat(enqueuedStory(embedderMonitor, 
story).getTimeoutInSecs(), is(50L));
+   
when(story.getPath()).thenReturn("/path/to/a_long_and_winding.story");
+   assertThat(enqueuedStory(embedderMonitor, 
story).getTimeoutInSecs(), is(500L));
+   }
+
+   @Test
+   public void shouldSupportStoryTimeoutsByPathUsingRegexPatterns(){
+   
embedderControls.useStoryTimeoutInSecsByPath("/[a-z]+/.*short.*:50,/[a-z]+/.*long.*:500");
+   
when(story.getPath()).thenReturn("/path/to/a_short_and_sweet.story");
+   assertThat(enqueuedStory(embedderMonitor, 
story).getTimeoutInSecs(), is(50L));
+   
when(story.getPath()).thenReturn("/path/to/a_long_and_winding.story");
+   assertThat(enqueuedStory(embedderMonitor, 
story).getTimeoutInSecs(), is(500L));
+   }
+
+   @Test
+   public void shouldSupportStoryTimeoutsByPathUsingMixedPatterns(){
+   
embedderControls.useStoryTimeoutInSecsByPath("/[a-z]+/.*short.*:50,**/*long*:500");
+   
when(story.getPath()).thenReturn("/path/to/a_short_and_sweet.story");
+   assertThat(enqueuedStory(embedderMonitor, 
story).getTimeoutInSecs(), is(50L));
+   
when(story.getPath()).thenReturn("/path/to/a_long_and_winding.story");
+   assertThat(enqueuedStory(embedderMonitor, 
story).getTimeoutInSecs(), is(500L));
+   }
+
+   private EnqueuedStory enqueuedStory(EmbedderMonitor embedderMonitor, 
Story story) {
+   return new EnqueuedStory(performableTree, context, 
embedderControls, embedderMonitor, story);
+   }
+
+}

[jbehave-scm] [scm-core/jbehave-4.x][1/2] JBEHAVE-833: Support both Ant-style and regex pattern syntaxes. Added Christopher Aguirre's example configuration to core example pom.xml.

commit b8ad7ded5cfb09c7ede127d5a996e2c564ab2d2d
Author: Mauro Talevi 
AuthorDate: Sat, 18 Apr 2015 09:32:06 +0200
Commit: Mauro Talevi 
CommitDate: Sat, 18 Apr 2015 09:32:54 +0200

JBEHAVE-833:  Support both Ant-style and regex pattern syntaxes.  Added 
Christopher Aguirre's example configuration to core example pom.xml.

diff --git a/examples/core/pom.xml b/examples/core/pom.xml
index 73815ca..dd67d6e 100755
--- a/examples/core/pom.xml
+++ b/examples/core/pom.xml
@@ -36,6 +36,8 @@
   true
   
${ignore.failure.in.stories}
   
${ignore.failure.in.view}
+  300  
+  
**/and_*.story:8,**/*calendar.story:15
  
   ${threads}
   
 ${meta.filter}
diff --git 
a/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java 
b/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java
index 73c2f3b..ca12f79 100644
--- a/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java
+++ b/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java
@@ -14,6 +14,7 @@ import java.util.concurrent.ExecutionException;
 import java.util.concurrent.ExecutorService;
 import java.util.concurrent.Future;
 import java.util.regex.Pattern;
+import java.util.regex.PatternSyntaxException;
 
 import org.codehaus.plexus.util.StringUtils;
 import org.jbehave.core.configuration.Configuration;
@@ -251,7 +252,7 @@ public class StoryManager {
return new RunningStory(enqueuedStory, 
executorService.submit(enqueuedStory));
}
 
-   private static class EnqueuedStory implements Callable {
+   static class EnqueuedStory implements Callable {
 
private final PerformableTree performableTree;
private final RunContext context;
@@ -323,7 +324,14 @@ public class StoryManager {
}
 
private String regexOf(String storyPattern) {
-   return storyPattern.replace("**", ".*");
+   try {
+   // check if pattern is already a valid regex
+   Pattern.compile(storyPattern);
+   return storyPattern;
+   } catch (PatternSyntaxException e) {
+   // assume Ant-style pattern:  **/path/*.story
+   return storyPattern.replace("*", ".*");
+   }   
}
}

Re: [jbehave-dev] Override step in Jbehave

2015-04-13 Thread Mauro Talevi

You could convert it from your own file format using a table transformer.

http://jbehave.org/reference/stable/tabular-parameters.html

On 13/04/2015 17:24, Patel, Nikunj (GE Healthcare) wrote:

I thought about parametrized scenarios option to read table values
from a file but then looks like we need to create external resource
file in table format and maintain. Is there any way we can read from
our existing data source (file or database) directly without
converting to table format?

*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Monday, April 13, 2015 3:54 AM
*To:* dev@jbehave.codehaus.org
*Subject:* Re: [jbehave-dev] Override step in Jbehave

Hi,

Sorry but I had misunderstood the usecase, the report will show the
original textual value.

What you might consider is parametrised scenarios, where the values
are replaced at the each execution. The table values can be read
from a file.

If you can provide a simplified example of your usecase we can add it
our core examples.

Cheers

On 12 Apr 2015, at 17:56, Patel, Nikunj (GE Healthcare)
mailto:nikunj.pa...@ge.com>> wrote:

Mauro,

I tried just simple String conversion using @AsParameterConverter
(haven’t created ErrorCode type yet) . It is returning converted
string fine but I don’t see converted string in HTML report.
Report still showing original string from feature file in report.
How can I replace converted string in report?

Thanks,

Nikunj

*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Tuesday, April 07, 2015 3:30 AM
*To:* dev@jbehave.codehaus.org <mailto:dev@jbehave.codehaus.org>
*Subject:* Re: [jbehave-dev] Override step in Jbehave

Here's an example of dynamic lookup via a parameter converter method:

https://github.com/jbehave/jbehave-core/blob/master/examples/core/src/main/java/org/jbehave/examples/core/steps/TraderSteps.java

Look for:

publicTrader retrieveTrader(Stringname);

On 05/04/2015 16:07, Patel, Nikunj (GE Healthcare) wrote:

Thanks Mauro.

Can you please guide to the example (if any)?

Thanks,

Nikunj

*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Saturday, April 04, 2015 11:01 AM
*To:* dev@jbehave.codehaus.org <mailto:dev@jbehave.codehaus.org>
*Subject:* Re: [jbehave-dev] Override step in Jbehave

Hi,

thanks for explaining your scenario. In this case, a custom
ErrorMessage type and a custom converter that looks up the
translation in a file or database would seem your best option.

Let use know if you encounter problems in its implementation.

Cheers

On 03/04/2015 14:38, Patel, Nikunj (GE Healthcare) wrote:

HI,

This is one the option we are thinking for i18n testing.

I know JBehave have i18n testing example but we don’t want
to convert entire story file in language we supporting. We
only want to convert labels and messages in different
language and test and keep everything in English. We are
planning to have converted text in multiple languages
available in files (key/values) or database.

Using below example, error message or label “abc” will be
in English, then using language files we convert values to
appropriate language(language set in
application.properties) before do compare with actual
value. Now, we want to include this converted text in the
HTML report.

One other option I was thinking to these message in story
example template and use meta filter but there are so many
and we don’t want to maintain in feature file.

What do you suggest we should do to test this kind of
scenario?

Thanks,

Nikunj

*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Friday, April 03, 2015 6:15 AM
*To:* dev@jbehave.codehaus.org
<mailto:dev@jbehave.codehaus.org>
*Subject:* Re: [jbehave-dev] Override step in Jbehave

It's possible if you define your own custom converter, but
it should be associated to a custom parameter type, e.g.
ErrorCode.

Then you implement the value conversion logic in the
parameter converter.

That said, it does not really seem very logical to do
this. What's your usecase?

On 03/04/2015 03:00, Patel, Nikunj (GE Healthcare) wrote:

Hi,

Is there any way in Jbehave we can override step with
converted parameter values?

Here is what I am trying to do:

For Example:

I have step in feature file- Then error message “a

[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time

2015-04-13 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










Hi Christopher, 
you can set it either in CoreStories or in the pom.xml but be aware that the pom.xml overrides what is set in the embedded Java configuration. 












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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] Override step in Jbehave

2015-04-13 Thread Mauro Talevi

Hi,

Sorry but I had misunderstood the usecase, the report will show the original 
textual value. 

What you might consider is parametrised scenarios, where the values are 
replaced at the each execution.   The table values can be read from a file.

If you can provide a simplified example of your usecase we can add it our core 
examples.

Cheers



> On 12 Apr 2015, at 17:56, Patel, Nikunj (GE Healthcare)  
> wrote:
> 
> Mauro,
>  
> I tried just simple String conversion using @AsParameterConverter (haven’t 
> created ErrorCode type yet) . It is returning converted string fine but I 
> don’t see converted string in HTML report. Report still showing original 
> string from feature file in report. How can I replace converted string in 
> report?
>  
>  
> Thanks,
> Nikunj
>  
> From: Mauro Talevi [mailto:mauro.tal...@aquilonia.org] 
> Sent: Tuesday, April 07, 2015 3:30 AM
> To: dev@jbehave.codehaus.org
> Subject: Re: [jbehave-dev] Override step in Jbehave
>  
> Here's an example of dynamic lookup via a parameter converter method: 
> 
> https://github.com/jbehave/jbehave-core/blob/master/examples/core/src/main/java/org/jbehave/examples/core/steps/TraderSteps.java
> 
> Look for:
> 
> public Trader retrieveTrader(String name);
> 
> On 05/04/2015 16:07, Patel, Nikunj (GE Healthcare) wrote:
> Thanks Mauro.
>  
> Can you please guide to the example (if any)?
>  
> Thanks,
> Nikunj
>  
> From: Mauro Talevi [mailto:mauro.tal...@aquilonia.org] 
> Sent: Saturday, April 04, 2015 11:01 AM
> To: dev@jbehave.codehaus.org
> Subject: Re: [jbehave-dev] Override step in Jbehave
>  
> Hi, 
> 
> thanks for explaining your scenario.  In this case, a custom ErrorMessage 
> type and a custom converter that looks up the translation in a file or 
> database would seem your best option. 
> 
> Let use know if you encounter problems in its implementation. 
> 
> Cheers
> 
> On 03/04/2015 14:38, Patel, Nikunj (GE Healthcare) wrote:
> HI,
>  
> This is one the option we are thinking for i18n testing.
> I know JBehave have i18n testing example but we don’t want to convert entire 
> story file in language we supporting. We only want to convert labels and 
> messages in different language and test and keep everything in English. We 
> are planning to have converted text in multiple languages available in files 
> (key/values) or database.
> Using below example, error message or label “abc” will be in English, then 
> using language files we convert values to appropriate language(language set 
> in application.properties) before do compare with actual value. Now, we want 
> to include this converted text in the HTML report.
>  
> One other option I was thinking to these message in story example template 
> and use meta filter but there are so many and we don’t want to maintain in 
> feature file.
>  
> What do you suggest we should do to test this kind of scenario?
>  
> Thanks,
> Nikunj
>  
>  
> From: Mauro Talevi [mailto:mauro.tal...@aquilonia.org] 
> Sent: Friday, April 03, 2015 6:15 AM
> To: dev@jbehave.codehaus.org
> Subject: Re: [jbehave-dev] Override step in Jbehave
>  
> It's possible if you define your own custom converter, but it should be 
> associated to a custom parameter type, e.g. ErrorCode.
> 
> Then you implement the value conversion logic in the parameter converter. 
> 
> That said, it does not really seem very logical to do this.   What's your 
> usecase? 
> 
> On 03/04/2015 03:00, Patel, Nikunj (GE Healthcare) wrote:
> Hi,
>  
> Is there any way in Jbehave we can override step with converted parameter 
> values?
>  
> Here is what I am trying to do:
> For Example:
> I have step in feature file- Then error message “abc” should be displayed. 
> Let’s see I am converting  string from “abc”  to “xyz”.
> Now, I want to override feature file step with converted value and see HTML 
> report like-  Then error message “xyz” should be displayed.
>  
> Thanks,
> Nikunj
>  
>  
>  
>  
>  
>  
>

[jbehave-dev] [jira] (JBEHAVE-1076) Travis builds failing

2015-04-09 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Travis builds failing 










The jenkins maven repo is only for Jenkins artifacts. The surefire plugin is found in Maven Central. If not found in one repo, it'll look it up in another.
The build works with settings.xml provided unless there are network issues preventing correct download.
Travis has been known to have connection issues. 












   

 Add Comment











 













 JBehave /  JBEHAVE-1076



  Travis builds failing 







 From my findings, it looks like the problem is the settings.xml file.   E.g. this "works" -> https://travis-ci.org/alb-i986/jbehave-core/builds/57723534  this does not -> https://travis-ci.org/alb-i986/jbehave-core/builds/57725840   The latter fails because of these:  {code}  [WARNING] Could not validate integrity of download from http://maven.jenkins-c...















 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-1075) Add FluentEnumConverter, able to convert lower-cased, space-separated values to Enums

2015-04-08 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi resolved an issue as Fixed











 







Pulled with thanks









 JBehave /  JBEHAVE-1075



  Add FluentEnumConverter, able to convert lower-cased, space-separated values to Enums 










Change By:

 Mauro Talevi




Resolution:

 Fixed




Fix Version/s:

 3.10




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-scm] [scm-core/jbehave-4.x][2/2] JBEHAVE-1075: Minor tidy up.

2015-04-08 Thread Mauro Talevi

commit 3d8b2a125746dcf3110634dcf6731e5fe55626b0
Author: Mauro Talevi 
AuthorDate: Wed, 8 Apr 2015 19:30:24 +0100
Commit: Mauro Talevi 
CommitDate: Wed, 8 Apr 2015 19:31:01 +0100

JBEHAVE-1075:  Minor tidy up.

diff --git 
a/jbehave-core/src/main/java/org/jbehave/core/steps/ParameterConverters.java 
b/jbehave-core/src/main/java/org/jbehave/core/steps/ParameterConverters.java
index e1d1122..b69d5c6 100755
--- a/jbehave-core/src/main/java/org/jbehave/core/steps/ParameterConverters.java
+++ b/jbehave-core/src/main/java/org/jbehave/core/steps/ParameterConverters.java
@@ -601,8 +601,7 @@ public class ParameterConverters {
 
 @Override
 public Object convertValue(String value, Type type) {
-String transformedValue = value.replaceAll("\\W", 
"_").toUpperCase();
-return super.convertValue(transformedValue, type);
+return super.convertValue(value.replaceAll("\\W", 
"_").toUpperCase(), type);
 }
 }
 
diff --git 
a/jbehave-core/src/test/java/org/jbehave/core/steps/ParameterConvertersBehaviour.java
 
b/jbehave-core/src/test/java/org/jbehave/core/steps/ParameterConvertersBehaviour.java
index 8ddb0f2..3e16a5a 100755
--- 
a/jbehave-core/src/test/java/org/jbehave/core/steps/ParameterConvertersBehaviour.java
+++ 
b/jbehave-core/src/test/java/org/jbehave/core/steps/ParameterConvertersBehaviour.java
@@ -40,11 +40,9 @@ import org.jbehave.core.steps.SomeSteps.MyParameters;
 import org.junit.Test;
 
 import static org.hamcrest.MatcherAssert.assertThat;
-
 import static org.hamcrest.Matchers.equalTo;
 import static org.hamcrest.Matchers.instanceOf;
 import static org.hamcrest.Matchers.is;
-
 import static org.junit.Assert.fail;
 import static org.mockito.Mockito.mock;
 
@@ -64,7 +62,7 @@ public class ParameterConvertersBehaviour {
 }
 
 private void assertThatDefaultConvertersInclude(ParameterConverter[] 
defaultConverters,
-Class... converterTypes) {
+@SuppressWarnings("unchecked") Class... converterTypes) {
 for (Class type : converterTypes) {
 boolean found = false;
 for (ParameterConverter converter : defaultConverters) {
@@ -461,7 +459,7 @@ public class ParameterConvertersBehaviour {
 }
 
 @Test
-public void flexibleEnumConverter_givenLowercasedSpaceSeparatedValue() {
+public void shouldConvertEnumFluently() {
 ParameterConverter converter = new FluentEnumConverter();
 assertThat(converter.accept(SomeEnum.class), equalTo(true));
 assertThat((SomeEnum) converter.convertValue("multiple words and 1 
number", SomeEnum.class), equalTo(SomeEnum.MULTIPLE_WORDS_AND_1_NUMBER));

[jbehave-scm] [scm-core][2/2] JBEHAVE-1075: Minor tidy up.

2015-04-08 Thread Mauro Talevi

commit d463814e7602de6a856fea3ba15eabb171934c2f
Author: Mauro Talevi 
AuthorDate: Wed, 8 Apr 2015 19:30:24 +0100
Commit: Mauro Talevi 
CommitDate: Wed, 8 Apr 2015 19:30:24 +0100

JBEHAVE-1075:  Minor tidy up.

diff --git 
a/jbehave-core/src/main/java/org/jbehave/core/steps/ParameterConverters.java 
b/jbehave-core/src/main/java/org/jbehave/core/steps/ParameterConverters.java
index e1d1122..b69d5c6 100755
--- a/jbehave-core/src/main/java/org/jbehave/core/steps/ParameterConverters.java
+++ b/jbehave-core/src/main/java/org/jbehave/core/steps/ParameterConverters.java
@@ -601,8 +601,7 @@ public class ParameterConverters {
 
 @Override
 public Object convertValue(String value, Type type) {
-String transformedValue = value.replaceAll("\\W", 
"_").toUpperCase();
-return super.convertValue(transformedValue, type);
+return super.convertValue(value.replaceAll("\\W", 
"_").toUpperCase(), type);
 }
 }
 
diff --git 
a/jbehave-core/src/test/java/org/jbehave/core/steps/ParameterConvertersBehaviour.java
 
b/jbehave-core/src/test/java/org/jbehave/core/steps/ParameterConvertersBehaviour.java
index 8ddb0f2..3e16a5a 100755
--- 
a/jbehave-core/src/test/java/org/jbehave/core/steps/ParameterConvertersBehaviour.java
+++ 
b/jbehave-core/src/test/java/org/jbehave/core/steps/ParameterConvertersBehaviour.java
@@ -40,11 +40,9 @@ import org.jbehave.core.steps.SomeSteps.MyParameters;
 import org.junit.Test;
 
 import static org.hamcrest.MatcherAssert.assertThat;
-
 import static org.hamcrest.Matchers.equalTo;
 import static org.hamcrest.Matchers.instanceOf;
 import static org.hamcrest.Matchers.is;
-
 import static org.junit.Assert.fail;
 import static org.mockito.Mockito.mock;
 
@@ -64,7 +62,7 @@ public class ParameterConvertersBehaviour {
 }
 
 private void assertThatDefaultConvertersInclude(ParameterConverter[] 
defaultConverters,
-Class... converterTypes) {
+@SuppressWarnings("unchecked") Class... converterTypes) {
 for (Class type : converterTypes) {
 boolean found = false;
 for (ParameterConverter converter : defaultConverters) {
@@ -461,7 +459,7 @@ public class ParameterConvertersBehaviour {
 }
 
 @Test
-public void flexibleEnumConverter_givenLowercasedSpaceSeparatedValue() {
+public void shouldConvertEnumFluently() {
 ParameterConverter converter = new FluentEnumConverter();
 assertThat(converter.accept(SomeEnum.class), equalTo(true));
 assertThat((SomeEnum) converter.convertValue("multiple words and 1 
number", SomeEnum.class), equalTo(SomeEnum.MULTIPLE_WORDS_AND_1_NUMBER));

[jbehave-dev] [jira] (JBEHAVE-1075) Add FlexibleEnumConverter, able to convert lower-cased, space-separated values to Enums

2015-04-08 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Add FlexibleEnumConverter, able to convert lower-cased, space-separated values to Enums 










I think FluentEnumConverter would be a more suitable name. 












   

 Add Comment











 













 JBehave /  JBEHAVE-1075



  Add FlexibleEnumConverter, able to convert lower-cased, space-separated values to Enums 







 Copying&pasting from the javadoc:   An EnumConverter allowing stories prose to be more natural. Before performing the actual conversion, it transforms values to upper-case, with any non-alphanumeric character replaced by an underscore ('_').   Example: assuming we have defined the step "Given I am on the $page" which is mapped to the method iAmOnPage(Pa...















 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-1066) Upgrade dependencies to support JDK 8

2015-04-07 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi resolved an issue as Fixed











 






 JBehave /  JBEHAVE-1066



  Upgrade dependencies to support JDK 8 










Change By:

 Mauro Talevi




Resolution:

 Fixed




Status:

 In Progress 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-833) Provide a configurable timeout value for each story running time

2015-04-07 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










I think it'd be much easier to modifiy the examples' CoreStories configuration to reproduce the behaviour in the doc.
Can you provide such pull request please? I'd be interested in understanding what works and what does not for you. 
Thanks












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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] Additional info in HTML report

2015-04-07 Thread Mauro Talevi

No, that's currently not supported. Please raise a JIRA issue for this.

On 06/04/2015 19:35, Patel, Nikunj (GE Healthcare) wrote:

Thanks Mauro. I was able to implement custom html output.

One more question- I want to print some items (i.e- browser name,
build ) from our .properties files in to this HTML report. Is it
possible to define variables from .properties file or java class to
ftl template?

*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Tuesday, March 31, 2015 3:10 AM
*To:* dev@jbehave.codehaus.org
*Subject:* Re: [jbehave-dev] Additional info in HTML report

That's because the html output is configured in the CustomHtmlOutput
class.

Follow the example, it shows you how to configure the custom html
output template.

On 30/03/2015 21:57, Patel, Nikunj (GE Healthcare) wrote:

Thanks Mauro.

I am following below link for custom template but having issue
with location.

https://github.com/jbehave/jbehave-core/blob/master/examples/core/src/main/java/org/jbehave/examples/core/CustomCoreStories.java

Currently, I have custome files under src/main/java/ftl and
using below to call it but doesn’t seem to be working? Getting
file not found.

viewResources.put("reports", " ftl/custom-html-output.ftl");

where should I put this custom report file?

Thanks,

Nikunj

*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Monday, March 30, 2015 12:37 PM
*To:* dev@jbehave.codehaus.org <mailto:dev@jbehave.codehaus.org>
*Subject:* Re: [jbehave-dev] Additional info in HTML report

The successful/failed information is implicit in the colour-coding
- green for success and red for failure.

If you want you can adapt your the html report template to
prepend/append the words.Look for macro called renderStep.

Cheers

On 30/03/2015 19:23, Patel, Nikunj (GE Healthcare) wrote:

Hi,

I would like know if there is a way to add additional logging
in HTML report specially for successful steps. We are required
to provide objective evidence in test results and as part of
it we are thinking to add “PASSED” or “SUCCESS” before/after
each successful step.

What do you suggest to achieve above goal?

Approaches I took so far:

1. I tried it below class which is writing info in log4j.txt
file but I really want add info in HTML report.

cid:image001.png@01D06ADF.46CEBEB0

2.I am thinking about creating custom freemarker template
using jbehave-html-output.ftl but not sure it will work.

Thanks,

Nikunj

Re: [jbehave-dev] Override step in Jbehave

2015-04-07 Thread Mauro Talevi

Here's an example of dynamic lookup via a parameter converter method:

https://github.com/jbehave/jbehave-core/blob/master/examples/core/src/main/java/org/jbehave/examples/core/steps/TraderSteps.java

Look for:

publicTraderretrieveTrader(Stringname);

On 05/04/2015 16:07, Patel, Nikunj (GE Healthcare) wrote:

Thanks Mauro.

Can you please guide to the example (if any)?

Thanks,

Nikunj

*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Saturday, April 04, 2015 11:01 AM
*To:* dev@jbehave.codehaus.org
*Subject:* Re: [jbehave-dev] Override step in Jbehave

Hi,

thanks for explaining your scenario. In this case, a custom
ErrorMessage type and a custom converter that looks up the translation
in a file or database would seem your best option.

Let use know if you encounter problems in its implementation.

Cheers

On 03/04/2015 14:38, Patel, Nikunj (GE Healthcare) wrote:

HI,

This is one the option we are thinking for i18n testing.

I know JBehave have i18n testing example but we don’t want to
convert entire story file in language we supporting. We only want
to convert labels and messages in different language and test and
keep everything in English. We are planning to have converted text
in multiple languages available in files (key/values) or database.

Using below example, error message or label “abc” will be in
English, then using language files we convert values to
appropriate language(language set in application.properties)
before do compare with actual value. Now, we want to include this
converted text in the HTML report.

One other option I was thinking to these message in story example
template and use meta filter but there are so many and we don’t
want to maintain in feature file.

What do you suggest we should do to test this kind of scenario?

Thanks,

Nikunj

*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Friday, April 03, 2015 6:15 AM
*To:* dev@jbehave.codehaus.org <mailto:dev@jbehave.codehaus.org>
*Subject:* Re: [jbehave-dev] Override step in Jbehave

It's possible if you define your own custom converter, but it
should be associated to a custom parameter type, e.g. ErrorCode.

Then you implement the value conversion logic in the parameter
converter.

That said, it does not really seem very logical to do this.
What's your usecase?

On 03/04/2015 03:00, Patel, Nikunj (GE Healthcare) wrote:

Hi,

Is there any way in Jbehave we can override step with
converted parameter values?

Here is what I am trying to do:

For Example:

I have step in feature file- Then error message “abc” should
be displayed.

Let’s see I am converting string from “abc” to “xyz”.

Now, I want to override feature file step with converted value
and see HTML report like- Then error message “xyz” should be
displayed.

Thanks,

Nikunj

Re: [jbehave-dev] Override step in Jbehave

2015-04-04 Thread Mauro Talevi


Hi,

thanks for explaining your scenario.  In this case, a custom 
ErrorMessage type and a custom converter that looks up the translation 
in a file or database would seem your best option.


Let use know if you encounter problems in its implementation.

Cheers

On 03/04/2015 14:38, Patel, Nikunj (GE Healthcare) wrote:


HI,

This is one the option we are thinking for i18n testing.

I know JBehave have i18n testing example but we don’t want to convert 
entire story file in language we supporting. We only want to convert 
labels and messages in different language and test and keep everything 
in English. We are planning to have converted text in multiple 
languages available in files (key/values) or database.


Using below example, error message or label “abc” will be in English, 
then using language files we convert values to appropriate 
language(language set in application.properties) before do compare 
with actual value. Now, we want to include this converted text in the 
HTML report.


One other option I was thinking to these message in story example 
template and use meta filter but there are so many and we don’t want 
to maintain in feature file.


What do you suggest we should do to test this kind of scenario?

Thanks,

Nikunj

*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Friday, April 03, 2015 6:15 AM
*To:* dev@jbehave.codehaus.org
*Subject:* Re: [jbehave-dev] Override step in Jbehave

It's possible if you define your own custom converter, but it should 
be associated to a custom parameter type, e.g. ErrorCode.


Then you implement the value conversion logic in the parameter converter.

That said, it does not really seem very logical to do this.   What's 
your usecase?


On 03/04/2015 03:00, Patel, Nikunj (GE Healthcare) wrote:

Hi,

Is there any way in Jbehave we can override step with converted
parameter values?

Here is what I am trying to do:

For Example:

I have step in feature file- Then error message “abc” should be
displayed.

Let’s see I am converting  string from “abc”  to “xyz”.

Now, I want to override feature file step with converted value and
see HTML report like-  Then error message “xyz” should be displayed.

Thanks,

Nikunj

Re: [jbehave-dev] Override step in Jbehave

2015-04-03 Thread Mauro Talevi

It's possible if you define your own custom converter, but it should be 
associated to a custom parameter type, e.g. ErrorCode.


Then you implement the value conversion logic in the parameter converter.

That said, it does not really seem very logical to do this. What's your 
usecase?


On 03/04/2015 03:00, Patel, Nikunj (GE Healthcare) wrote:


Hi,

Is there any way in Jbehave we can override step with converted 
parameter values?


Here is what I am trying to do:

For Example:

I have step in feature file- Then error message “abc” should be 
displayed.


Let’s see I am converting  string from “abc”  to “xyz”.

Now, I want to override feature file step with converted value and see 
HTML report like-  Then error message “xyz” should be displayed.


Thanks,

Nikunj

[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time

Title: Message Title










 

 Mauro Talevi edited a comment on an issue











 






  Re: Provide a configurable timeout value for each story running time 









 Hi Christopher,happy to hear that it works well for you.   Not sure I understand your comment, though.The current path format allows use of  "  asterisks [ * " ] , which will be converted to regex characters  "  [ .* " ] Can you clarify what you mean?Cheers












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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-833) Provide a configurable timeout value for each story running time

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










Hi Christopher,
happy to hear that it works well for you. Not sure I understand your comment, though.
The current path format allows use of '', which will be converted to regex characters '.'. 
Can you clarify what you mean?
Cheers












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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-833) Provide a configurable timeout value for each story running time

Title: Message Title










 

 Mauro Talevi edited a comment on an issue











 






  Re: Provide a configurable timeout value for each story running time 









 Hi Christopher,happy to hear that it works well for you.   Not sure I understand your comment, though.The current path format allows use of  '  " * ' " , which will be converted to regex characters  '  " .* '. "  Can you clarify what you mean?Cheers












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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-1073) Story duration time in multi-threading execution mode is higher than normal

Title: Message Title










 

 Mauro Talevi resolved an issue as Fixed











 






 JBehave /  JBEHAVE-1073



  Story duration time in multi-threading execution mode is higher than normal 










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-1073) Story duration time in multi-threading execution mode is higher than normal

Title: Message Title










 

 Mauro Talevi updated an issue











 






 JBehave /  JBEHAVE-1073



  Story duration time in multi-threading execution mode is higher than normal 










Change By:

 Mauro Talevi




Issue Type:

 Bug Improvement









 When running in multi-threading mode,  the total is calculated as simply be the sum of each duration.   If you have a single thread then it will coincide with the build duration (more or less), but  if  you use multiple threads it'll be off by a factor which should correspond to the number of threads.   The additional information of the average duration per thread, the total sum of the story durations divided by the number of threads, should also be available if you are in multi-threading mode.












   

 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/jbehave-4.x][1/1] JBEHAVE-1073: Added thread average story duration when running in multi-threading mode.

2015-04-02 Thread Mauro Talevi

commit 4c384067b7a4ef21c1d973d344409b653b7fad2f
Author: Mauro Talevi 
AuthorDate: Thu, 2 Apr 2015 13:25:14 +0200
Commit: Mauro Talevi 
CommitDate: Thu, 2 Apr 2015 13:25:29 +0200

JBEHAVE-1073:  Added thread average story duration when running in 
multi-threading mode.

diff --git a/examples/core/pom.xml b/examples/core/pom.xml
index 342f699..73815ca 100755
--- a/examples/core/pom.xml
+++ b/examples/core/pom.xml
@@ -12,6 +12,7 @@
   
 **/CoreStories.java
 
+2
 true
 true
   
@@ -35,7 +36,7 @@
   true
   
${ignore.failure.in.stories}
   
${ignore.failure.in.view}
-  2
+  ${threads}
   
 ${meta.filter}
   
diff --git 
a/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java 
b/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java
index 2b0ede9..73c2f3b 100644
--- a/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java
+++ b/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java
@@ -220,7 +220,11 @@ public class StoryManager {
 future.cancel(true);
 }
}
+   int threads = embedderControls.threads();
+   long threadAverage = total / threads;
storyDurations.setProperty("total", Long.toString(total));
+   storyDurations.setProperty("threads", Long.toString(threads));
+   storyDurations.setProperty("threadAverage", 
Long.toString(threadAverage));
write(storyDurations, "storyDurations.props");
}
 
diff --git 
a/jbehave-core/src/main/resources/ftl/jbehave-reports-with-totals.ftl 
b/jbehave-core/src/main/resources/ftl/jbehave-reports-with-totals.ftl
index 52cd4ee..c24c68f 100755
--- a/jbehave-core/src/main/resources/ftl/jbehave-reports-with-totals.ftl
+++ b/jbehave-core/src/main/resources/ftl/jbehave-reports-with-totals.ftl
@@ -197,6 +197,20 @@
 Totals
 
 
+
+<#assign threads = storyDurations.get('threads')!1>
+<#if (threads != 1) >
+
+
+
+<@renderTime storyDurations.get('threadAverage')!0/>
+
+
+${threads}-Thread Average
+
+
+
+

[jbehave-scm] [scm-core][1/1] JBEHAVE-1073: Added thread average story duration when running in multi-threading mode.

2015-04-02 Thread Mauro Talevi

commit 8ea8f9e58e7cb879c23bb4f4fff00d15592c3600
Author: Mauro Talevi 
AuthorDate: Thu, 2 Apr 2015 13:25:14 +0200
Commit: Mauro Talevi 
CommitDate: Thu, 2 Apr 2015 13:25:14 +0200

JBEHAVE-1073:  Added thread average story duration when running in 
multi-threading mode.

diff --git a/examples/core/pom.xml b/examples/core/pom.xml
index 0e0f7eb..686c73d 100755
--- a/examples/core/pom.xml
+++ b/examples/core/pom.xml
@@ -12,6 +12,7 @@
   
 **/CoreStories.java
 
+2
 true
 true
   
@@ -35,7 +36,7 @@
   true
   
${ignore.failure.in.stories}
   
${ignore.failure.in.view}
-  2
+  ${threads}
   
 ${meta.filter}
   
diff --git 
a/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java 
b/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java
index 123084a..dec454b 100644
--- a/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java
+++ b/jbehave-core/src/main/java/org/jbehave/core/embedder/StoryManager.java
@@ -200,7 +200,11 @@ public class StoryManager {
 future.cancel(true);
 }
}
+   int threads = embedderControls.threads();
+   long threadAverage = total / threads;
storyDurations.setProperty("total", Long.toString(total));
+   storyDurations.setProperty("threads", Long.toString(threads));
+   storyDurations.setProperty("threadAverage", 
Long.toString(threadAverage));
write(storyDurations, "storyDurations.props");
}
 
diff --git 
a/jbehave-core/src/main/resources/ftl/jbehave-reports-with-totals.ftl 
b/jbehave-core/src/main/resources/ftl/jbehave-reports-with-totals.ftl
index 52cd4ee..c24c68f 100755
--- a/jbehave-core/src/main/resources/ftl/jbehave-reports-with-totals.ftl
+++ b/jbehave-core/src/main/resources/ftl/jbehave-reports-with-totals.ftl
@@ -197,6 +197,20 @@
 Totals
 
 
+
+<#assign threads = storyDurations.get('threads')!1>
+<#if (threads != 1) >
+
+
+
+<@renderTime storyDurations.get('threadAverage')!0/>
+
+
+${threads}-Thread Average
+
+
+
+

[jbehave-dev] [jira] (JBEHAVE-1073) Story duration time in multi-threading execution mode is higher than normal

Title: Message Title










 

 Mauro Talevi updated an issue











 






 JBehave /  JBEHAVE-1073



  Story duration time in multi-threading execution mode is higher than normal 










Change By:

 Mauro Talevi




Fix Version/s:

 3.9.6




Assignee:

 Mauro Talevi









 From: Mauro Talevi [mailto:mauro.tal...@aquilonia.org] Sent: Wednesday, April 01, 2015 4:03 PMTo: u...@jbehave.codehaus.orgSubject: Re: [jbehave-user] Story duration are not calculated correctly in multi-thread executionSure, easy enough to do! Can you please raise a JIRA issue for this usecase?CheersOn 1 Apr 2015, at 23:56, tran, phong  wrote:Hi Mauro, Yes weâre When  running in multi-threading mode  with 10 threads for concurrent story execution. EmbedderControls[batch=false , skip=false,generateViewAfterStories=true,ignoreFailureInStories=true,ignoreFailureInView=false,verboseFailures=true,verboseFiltering=false,storyTimeoutInSecs=108000,failOnStoryTimeout=false,threads=10] Weâre trying to speed up  the  test execution (Selenium-based tests) with multiple threads (threads=10) targeting a Selenium Grid with 10 nodes.   I noticed that the reported duration for each story is also high and that is why the sum of all story durations added up to a high  total  number. Does this mean the duration at the story level has been affected with multi-threading execution mode? Do we need to de-normalize (divided by 10 in this case) the duration for each story to get its accurate execution time?  It would be great if the de-normalization for story duration can be at addressed at the JBehave framework 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 AMTo: u...@jbehave.codehaus.orgSubject: Re: [jbehave-user] Story duration are not calculated correctly in multi-thread execution Hi Phong,I would imagine you're running in multi-threading mode.  The total  is calculated as simply be the sum of each duration.   If you have a single thread then it will coincide with the build duration (more or less), but you use multiple threads it'll be off by a factor which should correspond to the number of threads.   Arguably we could use the information of the threads to renormalise the total by the number of threads.   This formula would still work in the case of a single thread. Can you confirm that you're using multiple threads? CheersOn 25/03/2015 08:22, tran, phong wrote:Hi Mauro,  Thanks a lot for updating the core example template!  We can access and integrate the durations from storyDurations.props into our custom HTML report now. However, we just notice another issue. The total duration reported in storyDurations.props for all stories is much higher (8 times) that what we usually see in our test run. Basically we have a c

[jbehave-dev] [jira] (JBEHAVE-1073) Story duration time in multi-threading execution mode is higher than normal

Title: Message Title










 

 Mauro Talevi updated an issue











 






 JBehave /  JBEHAVE-1073



  Story duration time in multi-threading execution mode is higher than normal 










Change By:

 Mauro Talevi




Summary:

 Story duration time in multi-threading execution mode is  high  higher  than normal












   

 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

Re: [jbehave-dev] Additional info in HTML report

2015-03-31 Thread Mauro Talevi

That's because the html output is configured in the CustomHtmlOutput class.

Follow the example, it shows you how to configure the custom html output
template.

On 30/03/2015 21:57, Patel, Nikunj (GE Healthcare) wrote:

Thanks Mauro.

I am following below link for custom template but having issue with
location.

https://github.com/jbehave/jbehave-core/blob/master/examples/core/src/main/java/org/jbehave/examples/core/CustomCoreStories.java

Currently, I have custome files under src/main/java/ftl and using
below to call it but doesn’t seem to be working? Getting file not found.

viewResources.put("reports", " ftl/custom-html-output.ftl");

where should I put this custom report file?

Thanks,

Nikunj

*From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org]
*Sent:* Monday, March 30, 2015 12:37 PM
*To:* dev@jbehave.codehaus.org
*Subject:* Re: [jbehave-dev] Additional info in HTML report

The successful/failed information is implicit in the colour-coding -
green for success and red for failure.

If you want you can adapt your the html report template to
prepend/append the words.Look for macro called renderStep.

Cheers

On 30/03/2015 19:23, Patel, Nikunj (GE Healthcare) wrote:

Hi,

I would like know if there is a way to add additional logging in
HTML report specially for successful steps. We are required to
provide objective evidence in test results and as part of it we
are thinking to add “PASSED” or “SUCCESS” before/after each
successful step.

What do you suggest to achieve above goal?

Approaches I took so far:

1. I tried it below class which is writing info in log4j.txt file
but I really want add info in HTML report.

cid:image001.png@01D06ADF.46CEBEB0

2.I am thinking about creating custom freemarker template using
jbehave-html-output.ftl but not sure it will work.

Thanks,

Nikunj

Re: [jbehave-dev] Additional info in HTML report

2015-03-30 Thread Mauro Talevi

The successful/failed information is implicit in the colour-coding - 
green for success and red for failure.


If you want you can adapt your the html report template to 
prepend/append the words.Look for macro called renderStep.


Cheers

On 30/03/2015 19:23, Patel, Nikunj (GE Healthcare) wrote:


Hi,

I would like know if there is a way to add additional logging in HTML 
report specially for successful steps. We are required to provide 
objective evidence in test results and as part of it we are thinking 
to add “PASSED” or “SUCCESS” before/after each successful step.


What do you suggest to achieve above goal?

Approaches I took so far:

1. I tried it below class which is writing info in log4j.txt file but 
I really want add info in HTML report.


cid:image001.png@01D06ADF.46CEBEB0

2.I am thinking about creating custom freemarker template using 
jbehave-html-output.ftl but not sure it will work.


Thanks,

Nikunj

[jbehave-dev] [jira] (JBEHAVE-1072) Upgrade to Selenium 2.44.0

2015-03-29 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi created an issue











 






 JBehave /  JBEHAVE-1072



  Upgrade to Selenium 2.44.0 










Issue Type:

  Task




Assignee:

 Mauro Talevi




Components:


 Web Selenium




Created:


 29/Mar/15 10:09 AM




Fix Versions:


 web-3.6




Priority:

  Major




Reporter:

 Mauro Talevi












   

 Add Comment











 










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

[jbehave-scm] [scm-web/4.x][2/2] JBEHAVE-1072: Upgraded to selenium 2.44.0

commit 41c27e813c3606a1bb6ec00fea0ac137bad8df2b
Author: Mauro Talevi 
AuthorDate: Sun, 29 Mar 2015 17:09:54 +0200
Commit: Mauro Talevi 
CommitDate: Sun, 29 Mar 2015 17:10:32 +0200

JBEHAVE-1072:  Upgraded to selenium 2.44.0

diff --git a/web-selenium/pom.xml b/web-selenium/pom.xml
index 9fbb4c4..31caf45 100644
--- a/web-selenium/pom.xml
+++ b/web-selenium/pom.xml
@@ -11,7 +11,7 @@
   Selenium and WebDriver API bindings for JBehave
 
   
-2.42.1
+2.44.0
 2.1.8

[jbehave-scm] [scm-web/4.x][1/2] JBEHAVE-1071: Use oss.sonatype.org.

commit 18101810346da2d4fa5d7a7458d39c638e6813aa
Author: Mauro Talevi 
AuthorDate: Sun, 29 Mar 2015 16:29:42 +0200
Commit: Mauro Talevi 
CommitDate: Sun, 29 Mar 2015 17:10:29 +0200

JBEHAVE-1071:  Use oss.sonatype.org.

diff --git a/pom.xml b/pom.xml
index 59b21ac..19acf5a 100644
--- a/pom.xml
+++ b/pom.xml
@@ -2,9 +2,9 @@
 http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
   4.0.0
   
-org.codehaus
-codehaus-parent
-1
+org.sonatype.oss
+oss-parent
+9
   
   org.jbehave.web
   jbehave-web
@@ -235,7 +235,7 @@
 
   org.apache.maven.plugins
   maven-site-plugin
-  3.0
+  3.4
 
 
   org.codehaus.mojo

[jbehave-scm] [scm-web][1/1] JBEHAVE-1072: Upgraded to selenium 2.44.0

commit 53f49d5ad77840d08d3bde852793382177d793eb
Author: Mauro Talevi 
AuthorDate: Sun, 29 Mar 2015 17:09:54 +0200
Commit: Mauro Talevi 
CommitDate: Sun, 29 Mar 2015 17:09:54 +0200

JBEHAVE-1072:  Upgraded to selenium 2.44.0

diff --git a/web-selenium/pom.xml b/web-selenium/pom.xml
index 3368c4c..f7a3022 100644
--- a/web-selenium/pom.xml
+++ b/web-selenium/pom.xml
@@ -11,7 +11,7 @@
   Selenium and WebDriver API bindings for JBehave
 
   
-2.42.1
+2.44.0
 2.1.8

[jbehave-scm] [scm-eclipse][1/1] JBEHAVE-1071: Use oss.sonatype.org.

commit 2168a6dc1e501d753f62a7152e2c6c239edc863e
Author: Mauro Talevi 
AuthorDate: Sun, 29 Mar 2015 16:35:48 +0200
Commit: Mauro Talevi 
CommitDate: Sun, 29 Mar 2015 16:35:48 +0200

JBEHAVE-1071:  Use oss.sonatype.org.

diff --git a/pom.xml b/pom.xml
index 99b59b5..a372c2f 100644
--- a/pom.xml
+++ b/pom.xml
@@ -4,9 +4,9 @@
   4.0.0
 
   
-org.codehaus
-codehaus-parent
-1
+org.sonatype.oss
+oss-parent
+9
   
 
   org.jbehave.eclipse

[jbehave-scm] [scm-site][1/1] JBEHAVE-1071: Use oss.sonatype.org.

commit 42f3bb545de4f091769907521dbc109dd17073de
Author: Mauro Talevi 
AuthorDate: Sun, 29 Mar 2015 16:32:50 +0200
Commit: Mauro Talevi 
CommitDate: Sun, 29 Mar 2015 16:32:50 +0200

JBEHAVE-1071:  Use oss.sonatype.org.

diff --git a/pom.xml b/pom.xml
index d067a49..ea59eed 100644
--- a/pom.xml
+++ b/pom.xml
@@ -1,9 +1,9 @@
 http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
   4.0.0
   
-org.codehaus
-codehaus-parent
-1
+org.sonatype.oss
+oss-parent
+9
   
   org.jbehave.site
   jbehave-site

[jbehave-scm] [scm-web][1/1] JBEHAVE-1071: Use oss.sonatype.org.

commit cd9e53e4c854c705aedd31920ccc131e01e60938
Author: Mauro Talevi 
AuthorDate: Sun, 29 Mar 2015 16:29:42 +0200
Commit: Mauro Talevi 
CommitDate: Sun, 29 Mar 2015 16:29:42 +0200

JBEHAVE-1071:  Use oss.sonatype.org.

diff --git a/pom.xml b/pom.xml
index 1c50f32..0d6832d 100644
--- a/pom.xml
+++ b/pom.xml
@@ -2,9 +2,9 @@
 http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
   4.0.0
   
-org.codehaus
-codehaus-parent
-1
+org.sonatype.oss
+oss-parent
+9
   
   org.jbehave.web
   jbehave-web
@@ -235,7 +235,7 @@
 
   org.apache.maven.plugins
   maven-site-plugin
-  3.0
+  3.4
 
 
   org.codehaus.mojo

[jbehave-scm] [scm-core/jbehave-4.x][1/1] JBEHAVE-1071: Use oss.sonatype.org.

2015-03-24 Thread Mauro Talevi

commit 35e6b94e19e86a9bec84c61ec071fa367e90ce77
Author: Mauro Talevi 
AuthorDate: Tue, 24 Mar 2015 11:44:48 +
Commit: Mauro Talevi 
CommitDate: Tue, 24 Mar 2015 11:45:48 +

JBEHAVE-1071:  Use oss.sonatype.org.

diff --git a/pom.xml b/pom.xml
index 206bf76..e8fd08b 100755
--- a/pom.xml
+++ b/pom.xml
@@ -1,9 +1,10 @@
-http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
+http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
   4.0.0
   
-org.codehaus
-codehaus-parent
-1
+org.sonatype.oss
+oss-parent
+9
   
   org.jbehave
   jbehave
diff --git a/settings.xml b/settings.xml
index f99454e..17b002e 100755
--- a/settings.xml
+++ b/settings.xml
@@ -6,15 +6,15 @@
   
 
   
-  codehaus
+  sonatype
   
 false
   
   
 
-  codehaus-public-repository-group
-  Codehaus Public Repository Group
-  https://nexus.codehaus.org/content/groups/public/
+  sonatype-public-repository-group
+  Sonatype Public Repository Group
+  https://oss.sonatype.org/content/groups/public/
   default
   
 true
@@ -28,9 +28,9 @@
   
   
 
-  codehaus-public-repository-group
-  Codehaus Public Repository Group
-  https://nexus.codehaus.org/content/groups/public/
+  sonatype-public-repository-group
+  Sonatype Public Repository Group
+  https://oss.sonatype.org/content/groups/public/
   
 true

[jbehave-scm] [scm-core][1/1] JBEHAVE-1071: Use oss.sonatype.org.

2015-03-24 Thread Mauro Talevi

commit 1c6e5379f6ee200b446f5b33ff19f791288693d9
Author: Mauro Talevi 
AuthorDate: Tue, 24 Mar 2015 11:44:48 +
Commit: Mauro Talevi 
CommitDate: Tue, 24 Mar 2015 11:44:48 +

JBEHAVE-1071:  Use oss.sonatype.org.

diff --git a/pom.xml b/pom.xml
index 6b5d5cc..7ca893f 100755
--- a/pom.xml
+++ b/pom.xml
@@ -1,9 +1,10 @@
-http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
+http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
   4.0.0
   
-org.codehaus
-codehaus-parent
-1
+org.sonatype.oss
+oss-parent
+9
   
   org.jbehave
   jbehave
diff --git a/settings.xml b/settings.xml
index f99454e..17b002e 100755
--- a/settings.xml
+++ b/settings.xml
@@ -6,15 +6,15 @@
   
 
   
-  codehaus
+  sonatype
   
 false
   
   
 
-  codehaus-public-repository-group
-  Codehaus Public Repository Group
-  https://nexus.codehaus.org/content/groups/public/
+  sonatype-public-repository-group
+  Sonatype Public Repository Group
+  https://oss.sonatype.org/content/groups/public/
   default
   
 true
@@ -28,9 +28,9 @@
   
   
 
-  codehaus-public-repository-group
-  Codehaus Public Repository Group
-  https://nexus.codehaus.org/content/groups/public/
+  sonatype-public-repository-group
+  Sonatype Public Repository Group
+  https://oss.sonatype.org/content/groups/public/
   
 true

[jbehave-dev] [jira] (JBEHAVE-1071) Migrate from Codehaus Nexus to Sonatype Nexus

2015-03-21 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi created an issue











 






 JBehave /  JBEHAVE-1071



  Migrate from Codehaus Nexus to Sonatype Nexus 










Issue Type:

  Task




Assignee:

 Mauro Talevi




Components:


 Build




Created:


 21/Mar/15 9:10 AM




Fix Versions:


 3.9.6, 4.0




Priority:

  Critical




Reporter:

 Mauro Talevi










As Codehaus is closing down, use Sonatype OSS Nexus at 
https://oss.sonatype.org
for releases and snapshots.












   

 Add Comment

[jbehave-scm] [scm-core/jbehave-4.x][1/1] Updated core exmaple custom-reports template. Updated Eclipse lifecycle mapping.

2015-03-21 Thread Mauro Talevi

commit b7f0435c8473ce97eaf8c70a43ca615827c1b4e4
Author: Mauro Talevi 
AuthorDate: Sat, 21 Mar 2015 13:56:04 +
Commit: Mauro Talevi 
CommitDate: Sat, 21 Mar 2015 13:56:31 +

Updated core exmaple custom-reports template.  Updated Eclipse lifecycle 
mapping.

diff --git a/examples/core/src/main/java/ftl/custom-reports.ftl 
b/examples/core/src/main/java/ftl/custom-reports.ftl
index 4459b36..fae5584 100755
--- a/examples/core/src/main/java/ftl/custom-reports.ftl
+++ b/examples/core/src/main/java/ftl/custom-reports.ftl
@@ -1,16 +1,13 @@
 <#ftl strip_whitespace=true>
 <#macro renderStat stats name class=""><#assign value = stats.get(name)!0><#if 
(value != 0)>${value}<#else>${value}
-<#macro renderMillis stats name class=""><#assign millis = 
stats.get(name)!0><#assign time = 
timeFormatter.formatMillis(millis)>${time}
+<#macro renderTime millis class=""><#assign time = 
timeFormatter.formatMillis(millis)>${time}
 
 http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
 
 
-Custom Reports
-
-
-@import url( "./style/jbehave-core.css" );
-
+JBehave Reports
+
 
 
 
@@ -22,7 +19,7 @@
 
 Story Reports
 
-
+
 
 
 
@@ -129,7 +126,8 @@
 <@renderStat stats "stepsIgnorable" "ignorable"/>
 
 
-<@renderMillis stats "duration"/>
+<#assign path = report.getPath()>
+<@renderTime storyDurations.get(path)!0/>
 
 
 <#assign filesByFormat = report.filesByFormat>
@@ -193,7 +191,7 @@
 <@renderStat stats "stepsIgnorable" "ignorable"/>
 
 
-<@renderMillis stats "duration"/>
+<@renderTime storyDurations.get('total')!0/>
 
 
 Totals
@@ -206,10 +204,24 @@ Totals
 
 
 Generated on ${date?string("dd/MM/ HH:mm:ss")}
-JBehave © 2003-2011
+JBehave © 2003-2014
 
 
 
+  
+  
+
+var mainTable_Props = {
+filters_row_index: 2,
+btn_reset: true
+};
+var tableFilter = setFilterGrid("mainTable", mainTable_Props, 2);
+
+
+
+@import url( "./style/jbehave-core.css" );
+
+

[jbehave-scm] [scm-core][1/1] Updated core exmaple custom-reports template. Updated Eclipse lifecycle mapping.

2015-03-21 Thread Mauro Talevi

commit ab2da932e01fd3929817c67f73f8b637e1225f0a
Author: Mauro Talevi 
AuthorDate: Sat, 21 Mar 2015 13:56:04 +
Commit: Mauro Talevi 
CommitDate: Sat, 21 Mar 2015 13:56:04 +

Updated core exmaple custom-reports template.  Updated Eclipse lifecycle 
mapping.

diff --git a/examples/core/src/main/java/ftl/custom-reports.ftl 
b/examples/core/src/main/java/ftl/custom-reports.ftl
index 4459b36..fae5584 100755
--- a/examples/core/src/main/java/ftl/custom-reports.ftl
+++ b/examples/core/src/main/java/ftl/custom-reports.ftl
@@ -1,16 +1,13 @@
 <#ftl strip_whitespace=true>
 <#macro renderStat stats name class=""><#assign value = stats.get(name)!0><#if 
(value != 0)>${value}<#else>${value}
-<#macro renderMillis stats name class=""><#assign millis = 
stats.get(name)!0><#assign time = 
timeFormatter.formatMillis(millis)>${time}
+<#macro renderTime millis class=""><#assign time = 
timeFormatter.formatMillis(millis)>${time}
 
 http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
 
 
-Custom Reports
-
-
-@import url( "./style/jbehave-core.css" );
-
+JBehave Reports
+
 
 
 
@@ -22,7 +19,7 @@
 
 Story Reports
 
-
+
 
 
 
@@ -129,7 +126,8 @@
 <@renderStat stats "stepsIgnorable" "ignorable"/>
 
 
-<@renderMillis stats "duration"/>
+<#assign path = report.getPath()>
+<@renderTime storyDurations.get(path)!0/>
 
 
 <#assign filesByFormat = report.filesByFormat>
@@ -193,7 +191,7 @@
 <@renderStat stats "stepsIgnorable" "ignorable"/>
 
 
-<@renderMillis stats "duration"/>
+<@renderTime storyDurations.get('total')!0/>
 
 
 Totals
@@ -206,10 +204,24 @@ Totals
 
 
 Generated on ${date?string("dd/MM/ HH:mm:ss")}
-JBehave © 2003-2011
+JBehave © 2003-2014
 
 
 
+  
+  
+
+var mainTable_Props = {
+filters_row_index: 2,
+btn_reset: true
+};
+var tableFilter = setFilterGrid("mainTable", mainTable_Props, 2);
+
+
+
+@import url( "./style/jbehave-core.css" );
+
+
 
 
 
diff --git a/ides/eclipse/lifecycle-mapping-metadata.xml 
b/ides/eclipse/lifecycle-mapping-metadata.xml
index 9cb75be..9a4d18b 100644
--- a/ides/eclipse/lifecycle-mapping-metadata.xml
+++ b/ides/eclipse/lifecycle-mapping-metadata.xml
@@ -1,6 +1,5 @@
 
 
-  
   
 
   
@@ -47,11 +46,9 @@
 maven-hpi-plugin
 [3.0,)
 
-  insert-test
+  resolve-test-dependencies
   test-hpl
-  
-resolve-test-dependencies
-  
+  insert-test
 
   
   
@@ -64,9 +61,9 @@
 maven-scala-plugin
 [2.9.1,)
 
-  add-source
-  compile
   testCompile
+  compile
+  add-source
 
   
   
@@ -86,6 +83,18 @@
 
   
 
+
+  
+org.apache.maven.plugins
+maven-plugin-plugin
+3.2
+
+  descriptor
+
+  
+  
+
+  
+
   
 
-

[jbehave-dev] [jira] (JBEHAVE-362) Convert story name in report to human readable form

2015-03-20 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Convert story name in report to human readable form 










Please use mailing lists for these kind of questions (http://jbehave.org/mailing-lists.html). 
Do not comment on old resolved issues.












   

 Add Comment











 













 JBehave /  JBEHAVE-362



  Convert story name in report to human readable form 







 Another good suggestion from feedback. Convert:   - trader_sells_stocks.story -> Trader Sells Stocks  















 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-833) Provide a configurable timeout value for each story running time

2015-03-13 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










Hi Chris,
I've pushed a refactored version. It passes all the tests that you had written (well done, by the way, for the excellent testing coverage of your patch!). 
The new version simply checks the story path matches the regex pattern provided (well, almost ... replacing ** -> .*).
Also gone is the timeValuesUsed map which was a rather ugly hack, only there for testing purposes. Again, the monitor pattern has been used to verify behaviour in an IOC-friendly way.
Could you please pull latest and test it works for you? 
Cheers












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1

[jbehave-dev] [jira] (JBEHAVE-1070) Loose step matching, not based on StepType

2015-03-12 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Loose step matching, not based on StepType 










While it's true that this constraint is strictly speaking not needed, it is nonetheless useful as it forces scenario writers not to be lazy and think about the syntax and how to word the steps. It is rather unlikely that steps of different types have exactly the same syntax. One could argue that it's a smell. 
That said, there are situations where that may happen. In this case it may be worth introducing an ANY value in the StepType enum (rather than dropping the step type). 
Having an annotation @Step(type=ANY) could be a good suggestion. We could then also have @Step(type=GIVEN) as an alias to @Given, etc ... 












   

 Add Comment











 













 JBehave /  JBEHAVE-1070



  Loose step matching, not based on StepType 







 Hi,   I've recently started working with jbehave, and I am noticing duplication when a step method can be more than one StepType, e.g.:   {code}  @Given("the cart is empty")  @When("the cart is empty")  public void cartIsEmpty() {}  {code}   An easy (?) workaround could be to support the following syntax   {code}  @Given("the cart is empty")  @When  p...















 This message was sen

[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time

2015-03-12 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










You're mixing two very different concerns here, configuration and monitoring. 
What matters is whether the path of the story we're running matches the regex patterns provided in the CSV of story timeouts. 
I'm looking into simplify your solution. 












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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-833) Provide a configurable timeout value for each story running time

2015-03-08 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi edited a comment on an issue











 






  Re: Provide a configurable timeout value for each story running time 









 Hi Christopher,finally got around to the patch.   Can you please explain why you need to introduce the method{code}public String getSearchDirectory() {code}in the EmbedderMonitor? If you need to configure anything, it should not be in the monitor class.  












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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-833) Provide a configurable timeout value for each story running time

2015-03-08 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










Hi Christopher,
finally got around to the patch. Can you please explain why you need to introduce the method



public String getSearchDirectory() 



in the EmbedderMonitor?












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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-1066 Upgraded xstream and scala dependencies.

2015-03-08 Thread Mauro Talevi

commit 33128c984ee1ec7916ee6e332d23c952d8e19190
Author: Mauro Talevi 
AuthorDate: Fri, 13 Feb 2015 10:09:28 +0100
Commit: Mauro Talevi 
CommitDate: Fri, 13 Feb 2015 10:10:36 +0100

JBEHAVE-1066 Upgraded xstream and scala dependencies.

diff --git a/jbehave-core/pom.xml b/jbehave-core/pom.xml
index bd6588c..54c8983 100755
--- a/jbehave-core/pom.xml
+++ b/jbehave-core/pom.xml
@@ -76,7 +76,7 @@
 
   com.thoughtworks.xstream
   xstream
-  1.4.5
+  1.4.7
 
 
   javax.inject
diff --git a/jbehave-scala/pom.xml b/jbehave-scala/pom.xml
index bf7df6d..bf8f2d5 100755
--- a/jbehave-scala/pom.xml
+++ b/jbehave-scala/pom.xml
@@ -19,7 +19,7 @@
 
   org.scala-lang
   scala-library
-  2.9.1
+  2.11.5
 
   
 
@@ -28,7 +28,7 @@
   
 org.scala-tools
 maven-scala-plugin
-2.9.1
+2.15.2
 
   
 scala-test-compile

[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time

2015-02-25 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










Hi Christopher, 
yes, I've seen it thanks. I'll get to it by the end of this week. 
Cheers












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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-1067) it is not possible to comment a scenario with !--

2015-02-20 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: it is not possible to comment a scenario with !-- 










No, it's not possible to comment a scenario with !--
If you want to skip the execution of a scenario, you should annotated it with a meta property, e.g.:
Scenario:  Meta: @skip
And use a filter "-skip" to avoid running the scenarios annotated with this property.












   

 Add Comment











 













 JBehave /  JBEHAVE-1067



  it is not possible to comment a scenario with !-- 







 If you write a scenario with parameter see example, and comment the next scenario with !--. Then the previous when doesn't work.   Example: This will not work   Scenario: example  When using profiles  |profile|  |WEBSOCKET 1 |   !-- Scenario: xxx   The scenario example will not work, because he think that !-- Scenario: xxx is a parameter.   But i...















 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-1066) Upgrade dependencies to support JDK 8

2015-02-13 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi started work on an issue











 







Change By:

 Mauro Talevi




Status:

 Open In Progress












   

 Add Comment











 













 JBehave /  JBEHAVE-1066



  Upgrade dependencies to support JDK 8 







 Upgrade any dependencies to support JDK 8.















 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-1066) Upgrade dependencies to support JDK 8

2015-02-13 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi created an issue











 






 JBehave /  JBEHAVE-1066



  Upgrade dependencies to support JDK 8 










Issue Type:

  Improvement




Assignee:

 Mauro Talevi




Components:


 Core, Scala Support




Created:


 13/Feb/15 3:08 AM




Fix Versions:


 3.9.6, 4.0




Priority:

  Major




Reporter:

 Mauro Talevi










Upgrade any dependencies to support JDK 8.












   

 Add Comment

[jbehave-scm] [scm-core][1/1] JBEHAVE-1066 Upgraded xstream and scala dependencies.

2015-02-13 Thread Mauro Talevi

commit 0eaf1266dd749a1e8cc2b14bc3c96aed8916e352
Author: Mauro Talevi 
AuthorDate: Fri, 13 Feb 2015 10:09:28 +0100
Commit: Mauro Talevi 
CommitDate: Fri, 13 Feb 2015 10:09:28 +0100

JBEHAVE-1066 Upgraded xstream and scala dependencies.

diff --git a/jbehave-core/pom.xml b/jbehave-core/pom.xml
index 03783c2..993426e 100755
--- a/jbehave-core/pom.xml
+++ b/jbehave-core/pom.xml
@@ -76,7 +76,7 @@
 
   com.thoughtworks.xstream
   xstream
-  1.4.5
+  1.4.7
 
 
   javax.inject
diff --git a/jbehave-scala/pom.xml b/jbehave-scala/pom.xml
index 1088551..eeb4ea4 100755
--- a/jbehave-scala/pom.xml
+++ b/jbehave-scala/pom.xml
@@ -19,7 +19,7 @@
 
   org.scala-lang
   scala-library
-  2.9.1
+  2.11.5
 
   
 
@@ -28,7 +28,7 @@
   
 org.scala-tools
 maven-scala-plugin
-2.9.1
+2.15.2
 
   
 scala-test-compile

[jbehave-dev] [jira] (JBEHAVE-1053) Allow entire story to be restarted

2015-02-12 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Allow entire story to be restarted 










Hi Brett,
apologies for the delay in pulling this request. I meant to do the corresponding changes to the 4.x branch but did not get time for it. Could you perhaps have a first stab at it? Essentially changing the PerformableTree in a similar way you've modified the StoryRunner? 
Cheers












   

 Add Comment











 













 JBehave /  JBEHAVE-1053



  Allow entire story to be restarted 







 For selenium tests that keep the same browser / context throughout the story, there are countless things that can go wrong such as network latency, slow application, etc. Since a false positive can cause people to quickly lose trust in the tests, others advised that the story should restart "x" amount of times before failing the test.   There is a way to...















 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] Problem Creating XRef files from Eclipse

2015-02-08 Thread Mauro Talevi


Hi Chris,

feel free to upgrade the version of xstream as part of the patch.

Cheers

On 07/02/2015 02:12, Chris Aguirre wrote:
Figure out what the problem was - I was using JDK 1.8 and the version 
of XStream we are using: 1.4.5 has some issues with JDK 1.8.


After downgrading locally to JDK 1.7 these XRef and Json files were 
being created fine and tests passed.


We will need to upgrade xstream to at least version 1.4.6 if we want 
to claim JBehave works with JDK 1.8.


XStream Issue: https://jira.codehaus.org/browse/XSTR-746

XStream Release Notes Which mention this issue was resolved: 
http://xstream.codehaus.org/changes.html


Regards,
Christopher Aguirre

On Fri, Jan 30, 2015 at 12:42 PM, Chris Aguirre 
mailto:chris.aguirr...@gmail.com>> wrote:


Haven't tried that yet - will try and get back to you when I get
the chance to get back to work on this.

Thanks for the fast response.

Regards,
Christopher Aguirre

On Fri, Jan 30, 2015 at 12:09 PM, Mauro Talevi
mailto:mauro.tal...@aquilonia.org>>
wrote:

Chris,

What counts is the command line build. Does it work?

If not can you stash your changes and verify that you can
build the latest master?

Cheers



On 30 Jan 2015, at 16:36, Chris Aguirre
mailto:chris.aguirr...@gmail.com>>
wrote:


JBehave Devs,

I am having issues creating CrossReferences in Eclipse.
Specifically, I am getting an ArrayIndexOutOfBoundsException
(-1) in:

/ 
com.thoughtworks.xstream.core.util.OrderRetainingMap.entrySet(OrderRetainingMap.java:77)/

when running the following Unit Tests:

/ ConcurrencyBehaviour.shouldCompleteXmlReportWhenStoryIsCancelled()/
/ ConcurrencyBehaviour.shouldAllowStoriesToBeTimed()/

/(Stack Trace is attached)/

Has anyone encountered similar issues when running from Eclipse?

I am actually close to submitting code for a new Ant/Maven
property: /storyTimeoutInSecsByPath /and want to ensure
XRef's are created after a failure.

Appreciate the guidance/help.

Regards,
Christopher Aguirre


-
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-1065) error with tab character in comments

2015-02-04 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: error with tab character in comments 










Could you please provide some concrete examples? 
As a side note, why not simply configure your editor to replace tabs with spaces? 












   

 Add Comment











 













 JBehave /  JBEHAVE-1065



  error with tab character in comments 







 When we write scenarios, we use tab character to aline columns of tabulars.  The problem appears when such step is commented (entirely or partially) by prefixing each step line by "!-- ".   The problem comes from the tab characters used in step tabular.  The result is that next uncommented step is recognized pending, and thus scenario fails.   If tab ch...















 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] Problem Creating XRef files from Eclipse

2015-01-30 Thread Mauro Talevi

Chris,

What counts is the command line build.   Does it work?

If not can you stash your changes and verify that you can build the latest 
master?

Cheers 



> On 30 Jan 2015, at 16:36, Chris Aguirre  wrote:
> 
> JBehave Devs, 
> 
> I am having issues creating CrossReferences in Eclipse. Specifically, I am 
> getting an ArrayIndexOutOfBoundsException (-1) in:
> 
>  
> com.thoughtworks.xstream.core.util.OrderRetainingMap.entrySet(OrderRetainingMap.java:77)
> 
> when running the following Unit Tests: 
> 
>  ConcurrencyBehaviour.shouldCompleteXmlReportWhenStoryIsCancelled()
>  ConcurrencyBehaviour.shouldAllowStoriesToBeTimed()
> 
> (Stack Trace is attached)
> 
> Has anyone encountered similar issues when running from Eclipse? 
> 
> I am actually close to submitting code for a new Ant/Maven property: 
> storyTimeoutInSecsByPath and want to ensure XRef's are created after a 
> failure. 
> 
> Appreciate the guidance/help.
> 
> Regards, 
> Christopher Aguirre
> 
> 
> -
> To unsubscribe from this list, please visit:
> 
>http://xircles.codehaus.org/manage_email

Re: [jbehave-dev] Loggin in jbehave

2015-01-29 Thread Mauro Talevi

The reporters do not by default include any logger output, except for 
logger configured to wrote to sysout and then only for the Console 
output.   If you want to do some quick debugging this is the easiest way.


Else, you can define your own custom logging-based reporter that 
includes any log statements you want.   Bear in mind that JBehave was 
designed to be log-agnostic.


Cheers

On 29/01/2015 08:56, Omer Shem-Tov wrote:

Hi,
I'm trying to add logging to jbehave, and I'm not sure what is the 
best practice.
beside this discussion 
http://www.mail-archive.com/dev%40jbehave.codehaus.org/msg08872.html I 
didn't find any documentation.


I'm trying to add log4j properties from a file, so when I log messages 
using logger.debug(message) and above it will go to text file, and 
messages like
logger.info (message) and above will go to the 
console log.


if I want also these messages to be shown in the html report?


How can I do that?
Why do I need to explicitly specify log4j as dependency in the pom?

Thanks,
  Omer

[jbehave-dev] [jira] (JBEHAVE-1053) Allow entire story to be restarted

2015-01-13 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Allow entire story to be restarted 










Hi Brett, the changes are a bit tricky to track because they're spread over multiple commits.
Could you please provide in a single commit the proposed changes since the pull of Nov 10? 
Thanks












   

 Add Comment











 













 JBehave /  JBEHAVE-1053



  Allow entire story to be restarted 







 For selenium tests that keep the same browser / context throughout the story, there are countless things that can go wrong such as network latency, slow application, etc. Since a false positive can cause people to quickly lose trust in the tests, others advised that the story should restart "x" amount of times before failing the test.   There is a way to...















 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-1063) ConcurrentModificationException in CrossReference.outputFile()

2015-01-08 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: ConcurrentModificationException in CrossReference.outputFile() 










Which version are you using? Can you provide a sample project that reproduces this behaviour?












   

 Add Comment











 













 JBehave /  JBEHAVE-1063



  ConcurrentModificationException in CrossReference.outputFile() 







 When Tests are executed massivley multithreaded, from time to time a ConcurrentModificationException is thrown when JBehave tries to write a report-file.   Trace:  {code}  java.util.ConcurrentModificationException  at java.util.HashMap$HashIterator.nextEntry(HashMap.java:926)  at java.util.HashMap$KeyIterator.next(HashMap.java:960)  at com.thoughtwork...















 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-1061) @BeforeScenario runs for every steps file that are instanciated

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: @BeforeScenario runs for every steps file that are instanciated 










All the methods annotated with @BeforeScenario will run before each scenario, regardless of which steps file the are contained in. 
Can you provide a sample project reproducing your behaviour? 












   

 Add Comment











 













 JBehave /  JBEHAVE-1061



  @BeforeScenario runs for every steps file that are instanciated 







 When i run my scenario that are using multiple steps files, the method that are annotated with @BeforeScenario runs for each steps file.   Im excpecting it to only run per scenario not per steps file















 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-979) Improve default report

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Improve default report 










Hi, thanks for the contribution. It's been pulled and applied to both master and jbehave-4.x branches.
A couple of minor further suggestions: 


do we need all the tablefilter*.js files or tablefilter_all_min.js?


can we use lower capitalisation consistently?


can we use white as the background color of the table header?














   

 Add Comment











 













 JBehave /  JBEHAVE-979



  Improve default report 







 The current report suffers from lack of information.  i'm working on a bit project and most of the people prefer the junit report provided on jenkins ci.   i think that the default report should have more information regrading:  * step failure - add full stacktrace and as much information as possible  * step duration  * filtering for the report table (ex...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sh

[jbehave-dev] [jira] (JBEHAVE-1062) Named parameter values containing backslash and dollar characters cause side effects

Title: Message Title










 

 Mauro Talevi updated an issue











 






 JBehave /  JBEHAVE-1062



  Named parameter values containing backslash and dollar characters cause side effects 










Change By:

 Mauro Talevi




Affects Version/s:

 3.9.6




Affects Version/s:

 3.x












   

 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-1062) Named parameter values containing backslash and dollar characters cause side effects

Title: Message Title










 

 Mauro Talevi resolved an issue as Fixed











 







Pulled with thanks!









 JBehave /  JBEHAVE-1062



  Named parameter values containing backslash and dollar characters cause side effects 










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

Re: [jbehave-dev] JBEHAVE-979 - Improve Default Report

2014-12-16 Thread Mauro Talevi

Yes, you can add it to src/main/resources.

Please add js resources to
/js/tablefilter
and any style resources (if any) would go in the die
/style/tablefilter

Cheers

> On 15 Dec 2014, at 19:00, Chris Aguirre  wrote:
> 
> Mauro, 
> 
> To make this change, I need to update jbehave-reports-with-totals.ftl and 
> include the TableFilter directory/code in jbehave-core/src/main-resources. 
> 
> TableFilter is available on GitHub, but there is no mention of a maven 
> repository. Is there a way to retrieve from GitHub, or should I simply add 
> the new directory manually? 
> 
> https://github.com/koalyptus/HTML-Table-Filter-Generator
> 
> 
> 
> Regards, 
> Christopher Aguirre
> 
>> On Thu, Dec 11, 2014 at 9:07 AM, Chris Aguirre  
>> wrote:
>> Mauro, 
>> 
>> I just did prototype for now - I will complete over next few days and send 
>> the pull request when done. 
>> 
>> Regards, 
>> Chris Aguirre
>> 
>>> On Thu, Dec 11, 2014 at 8:05 AM, Mauro Talevi  
>>> wrote:
>>> Hi Chris,
>>> 
>>> this looks like an interesting and useful improvement.   
>>> 
>>> Can you please provide a pull request with your implementation? 
>>> 
>>> Cheers
>>> 
>>> 
>>>> On 10/12/2014 21:13, Chris Aguirre wrote:
>>>> JBehave Devs, 
>>>> 
>>>> I've done a prototype of using TableFilter (http://tablefilter.free.fr/), 
>>>> a javascript library which can be used to add filters to the JBehave 
>>>> reports.html. 
>>>> 
>>>> I've attached 2 screen shots to give a visual - and you can see the filter 
>>>> in action on their website. 
>>>> 
>>>> Thoughts on this implementation?
>>>> 
>>>> 
>>>> Regards, 
>>>> Christopher Aguirre
>>>> 
>>>> 
>>>> -
>>>> To unsubscribe from this list, please visit:
>>>> 
>>>> http://xircles.codehaus.org/manage_email

Re: [jbehave-dev] JBEHAVE-979 - Improve Default Report

2014-12-11 Thread Mauro Talevi


Hi Chris,

this looks like an interesting and useful improvement.

Can you please provide a pull request with your implementation?

Cheers

On 10/12/2014 21:13, Chris Aguirre wrote:

JBehave Devs,

I've done a prototype of using TableFilter 
(http://tablefilter.free.fr/), a javascript library which can be used 
to add filters to the JBehave reports.html.


I've attached 2 screen shots to give a visual - and you can see the 
filter in action on their website.


Thoughts on this implementation?


Regards,
Christopher Aguirre


-
To unsubscribe from this list, please visit:

 http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time

2014-12-09 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










To subscribe to the mailing lists you need to create a Codehaus account and then subscribe via the project site: 
http://xircles.codehaus.org/projects/jbehave












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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-833) Provide a configurable timeout value for each story running time

2014-12-09 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










This features requires two main elements:


configuration: add a configuration element similar to storyTimeoutInSecs, which we may call storyTimeoutInSecsByPath, which will override the default value in storyTimeoutInSecs, and can be expressed as a CSV of regex expressions matching story paths. E.g. "*/long/.story:5000,*/short/.story:200". Note that there are several places where the storyTimeoutInSecs is configured and an equivalent element needs to be added for storyTimeoutInSecsByPath (using the type String in place of long).


implementation of logic: in StoryManager the story timeouts by paths need to be parsed and matched according to the story path being executed














   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 This message was sent by Atlassian JIRA (v6.1.6#6162-sh

[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time

2014-12-08 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










No, there is currently only one configured timeout value.












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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-933) timeout should be applied to stories only

2014-12-08 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: timeout should be applied to stories only 










Yes












   

 Add Comment











 













 JBehave /  JBEHAVE-933



  timeout should be applied to stories only 







 Hi,   as I read the specification of a timeout, it is setting the controls to let a story time out, when a specified amount of time has passed. By the name this is a setting per story. So, when I have a timeout of 300s per story, I should be able to have 100 stories, which take 250 seconds each.   The way it is implemented is different, though. The Sto...















 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][2/3] JBEHAVE-1058: Removed entries corresponding to single letters.

2014-12-06 Thread Mauro Talevi

commit 248b4cf3db3a14d847cf0c6706325e4394bf6331
Author: Mauro Talevi 
AuthorDate: Sat, 6 Dec 2014 17:12:11 +0100
Commit: Mauro Talevi 
CommitDate: Sat, 6 Dec 2014 17:16:29 +0100

JBEHAVE-1058:  Removed entries corresponding to single letters.

diff --git a/jbehave-core/src/main/resources/i18n/keywords_hu.properties 
b/jbehave-core/src/main/resources/i18n/keywords_hu.properties
index c9ddc66..92e4731 100644
--- a/jbehave-core/src/main/resources/i18n/keywords_hu.properties
+++ b/jbehave-core/src/main/resources/i18n/keywords_hu.properties
@@ -1,14 +1,3 @@
-é = \u00e9
-É = \u00c9
-á = \u00e1
-Ö = \u00d6
-Ő = \u0150
-ö = \u00f6
-ő = \u0151
-Ü = \u00dc
-Á = \u00c1
-í = \u00ed
-ó = \u00f3
 Meta=Meta:
 MetaProperty=@
 Narrative=\u00d6sszefoglal\u00e1s:

[jbehave-dev] [jira] (JBEHAVE-1060) Polish language support

2014-12-06 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi resolved an issue as Fixed











 







Pulled with thanks









 JBehave /  JBEHAVE-1060



  Polish language support 










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-1058) Hungarian language support

2014-12-06 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi resolved an issue as Fixed











 







Pulled https://github.com/jbehave/jbehave-core/pull/70 with thanks









 JBehave /  JBEHAVE-1058



  Hungarian language support 










Change By:

 Mauro Talevi




Resolution:

 Fixed




Assignee:

 Mauro Talevi




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-scm] [scm-core][2/2] JBEHAVE-1058: Removed entries corresponding to single letters.

2014-12-06 Thread Mauro Talevi

commit 870bc8878b35c545fdfddbfd382353fd690f07fe
Author: Mauro Talevi 
AuthorDate: Sat, 6 Dec 2014 17:12:11 +0100
Commit: Mauro Talevi 
CommitDate: Sat, 6 Dec 2014 17:12:11 +0100

JBEHAVE-1058:  Removed entries corresponding to single letters.

diff --git a/jbehave-core/src/main/resources/i18n/keywords_hu.properties 
b/jbehave-core/src/main/resources/i18n/keywords_hu.properties
index c9ddc66..92e4731 100644
--- a/jbehave-core/src/main/resources/i18n/keywords_hu.properties
+++ b/jbehave-core/src/main/resources/i18n/keywords_hu.properties
@@ -1,14 +1,3 @@
-é = \u00e9
-É = \u00c9
-á = \u00e1
-Ö = \u00d6
-Ő = \u0150
-ö = \u00f6
-ő = \u0151
-Ü = \u00dc
-Á = \u00c1
-í = \u00ed
-ó = \u00f3
 Meta=Meta:
 MetaProperty=@
 Narrative=\u00d6sszefoglal\u00e1s:

[jbehave-dev] [jira] (JBEHAVE-1059) NPE during run tests in other languages

2014-12-04 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: NPE during run tests in other languages 










This NPE does not occur in the JBehave code but in the codecentric code. 
You should raise the issue with them.












   

 Add Comment











 













 JBehave /  JBEHAVE-1059



  NPE during run tests in other languages 







 I have a simple project Jbehave + Thucydides from archetype: net.thucydides:thucydides-jbehave-archetype.  And I modified class *de.jbehave.AcceptanceTestSuite* to change the locale of the test for other language e.x. German  {code:lang=java}  package de.jbehave;   import net.thucydides.jbehave.ThucydidesJUnitStories;  import net.thucydides.jbehave.UTF8S...















 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-1060) Polish language support

2014-12-04 Thread Mauro Talevi (JIRA)

Title: Message Title










 

 Mauro Talevi assigned an issue to Mauro Talevi











 






 JBehave /  JBEHAVE-1060



  Polish language support 










Change By:

 Mauro Talevi




Assignee:

 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-1057) Jenkins plugin broken, unmatched dependency

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Jenkins plugin broken, unmatched dependency 










The DTKit dependency comes from the Jenkins xunit plugin.
Could you please try building the jbehave-jenkins-plugin with the latest updated version
$ mvn clean install -Dxunit.plugin.version=1.92 
to see if this fixes the problem? 
The currently used version of the xunit plugin is 1.62.












   

 Add Comment











 













 JBehave /  JBEHAVE-1057



  Jenkins plugin broken, unmatched dependency 







 Current available jenkins plugin has unmatched dependency. When installing it crashes with:   WARNING: Failed to load org.jBehavePluginType$DescriptorImpl   jbehave is then not available in product configuration for processing the output.   I'm not only one with this problem. Here is a workaround which works great, modified jenkins package without the ...















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




 












-
To unsubscribe from this list, p

[jbehave-dev] [jira] (JBEHAVE-1056) ResolveToPackagedName path resolver is broken on Windows

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: ResolveToPackagedName path resolver is broken on Windows 










Could you please provide an example project reproducing this behaviour, in particular the configuration you use.












   

 Add Comment











 













 JBehave /  JBEHAVE-1056



  ResolveToPackagedName path resolver is broken on Windows 







 Current implementation of 'org.jbehave.core.reporters.FilePrintStreamFactory.ResolveToPackagedName' is the following:   {code:java}  public static class ResolveToPackagedName extends AbstractPathResolver {   public String resolveName(StoryLocation storyLocation , String extension) {  String name = storyLocation .getPath().replace...















 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-1056) ResolveToPackagedName path resolver is broken on Windows

Title: Message Title










 

 Mauro Talevi updated an issue











 






 JBehave /  JBEHAVE-1056



  ResolveToPackagedName path resolver is broken on Windows 










Change By:

 Mauro Talevi




Affects Version/s:

 3.x




Affects Version/s:

 3.9.5




Fix Version/s:

 3.9.6












   

 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-1057) Jenkins plugin broken, unmatched dependency

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Jenkins plugin broken, unmatched dependency 










It's not clear from the link which dependency is missing. 
Could you please provide a patch of the jenkins plugin pom.xml with the dependencies that work for you?












   

 Add Comment











 













 JBehave /  JBEHAVE-1057



  Jenkins plugin broken, unmatched dependency 







 Current available jenkins plugin has unmatched dependency. When installing it crashes with:   WARNING: Failed to load org.jBehavePluginType$DescriptorImpl   jbehave is then not available in product configuration for processing the output.   I'm not only one with this problem. Here is a workaround which works great, modified jenkins package without the ...















 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-1058) Hungarian language support

Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Hungarian language support 










Can you please provide a patch with the Hungarian version of keywords:
https://github.com/jbehave/jbehave-core/blob/master/jbehave-core/src/main/resources/i18n/keywords_en.properties












   

 Add Comment











 













 JBehave /  JBEHAVE-1058



  Hungarian language support 














 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-1058) Hungarian language support