[jbehave-dev] [jira] Resolved: (JBEHAVE-521) Typo in jbehave-spring-archetype causes malformed pom.xml
[ http://jira.codehaus.org/browse/JBEHAVE-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-521. -- Resolution: Fixed Typo in jbehave-spring-archetype causes malformed pom.xml - Key: JBEHAVE-521 URL: http://jira.codehaus.org/browse/JBEHAVE-521 Project: JBehave Issue Type: Bug Components: Archetypes Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.1 /jbehave.sitee.version - /jbehave.site.version -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-522) Add documentation page on tutorials
[ http://jira.codehaus.org/browse/JBEHAVE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-522. -- Resolution: Fixed Add documentation page on tutorials --- Key: JBEHAVE-522 URL: http://jira.codehaus.org/browse/JBEHAVE-522 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-520) NPE in StoryRunner: currentStrategy is not set when running before or after stories steps
[ http://jira.codehaus.org/browse/JBEHAVE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-520: - Fix Version/s: (was: 3.4) 3.4.1 Summary: NPE in StoryRunner: currentStrategy is not set when running before or after stories steps (was: NPE in StoryRunner:76 [currentStrategy.get().handleFailure(storyFailure.get());] - causing org.jbehave.core.embedder.Embedder$RunningStoriesFailed: Failures in running before or after stories steps) NPE in StoryRunner: currentStrategy is not set when running before or after stories steps - Key: JBEHAVE-520 URL: http://jira.codehaus.org/browse/JBEHAVE-520 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.4 Environment: Windowx XP, mvn 3.0.3 and 2.2.1, jbehave 3.4 Reporter: Maciej Madej Priority: Critical Fix For: 3.4.1 Attachments: jbehave-after-before-bug.zip I got following exception when building attached project (mvn clean install): --- Test set: pl.mmadej.jbehave.JBehaveStoriesTest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.562 sec FAILURE! [run_with_no_replacement.story](pl.mmadej.jbehave.JBehaveStoriesTest) Time elapsed: 0.343 sec ERROR! org.jbehave.core.embedder.Embedder$RunningStoriesFailed: Failures in running before or after stories steps at org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:210) at pl.mmadej.jbehave.JBehaveStoriesTest.run(JBehaveStoriesTest.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Please investigate. This error happens with jbehave 3.4. When I'm using 3.3.2 everything looks ok. Internally there is NPE in StoryRunner:76 -- currentStrategy.get().handleFailure(storyFailure.get()); currentStrategy.get() returns null. Please investigate. Thanks in advance for your help -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-520) NPE in StoryRunner: currentStrategy is not set when running before or after stories steps
[ http://jira.codehaus.org/browse/JBEHAVE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-520. -- Resolution: Fixed NPE in StoryRunner: currentStrategy is not set when running before or after stories steps - Key: JBEHAVE-520 URL: http://jira.codehaus.org/browse/JBEHAVE-520 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.4 Environment: Windowx XP, mvn 3.0.3 and 2.2.1, jbehave 3.4 Reporter: Maciej Madej Priority: Critical Fix For: 3.4.1 Attachments: jbehave-after-before-bug.zip I got following exception when building attached project (mvn clean install): --- Test set: pl.mmadej.jbehave.JBehaveStoriesTest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.562 sec FAILURE! [run_with_no_replacement.story](pl.mmadej.jbehave.JBehaveStoriesTest) Time elapsed: 0.343 sec ERROR! org.jbehave.core.embedder.Embedder$RunningStoriesFailed: Failures in running before or after stories steps at org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:210) at pl.mmadej.jbehave.JBehaveStoriesTest.run(JBehaveStoriesTest.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Please investigate. This error happens with jbehave 3.4. When I'm using 3.3.2 everything looks ok. Internally there is NPE in StoryRunner:76 -- currentStrategy.get().handleFailure(storyFailure.get()); currentStrategy.get() returns null. Please investigate. Thanks in advance for your help -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-520) StoryRunner failure strategy is not set when running before or after stories steps in multiple threads
[ http://jira.codehaus.org/browse/JBEHAVE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-520: - Summary: StoryRunner failure strategy is not set when running before or after stories steps in multiple threads (was: NPE in StoryRunner: currentStrategy is not set when running before or after stories steps) StoryRunner failure strategy is not set when running before or after stories steps in multiple threads -- Key: JBEHAVE-520 URL: http://jira.codehaus.org/browse/JBEHAVE-520 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.4 Environment: Windowx XP, mvn 3.0.3 and 2.2.1, jbehave 3.4 Reporter: Maciej Madej Priority: Critical Fix For: 3.4.1 Attachments: jbehave-after-before-bug.zip I got following exception when building attached project (mvn clean install): --- Test set: pl.mmadej.jbehave.JBehaveStoriesTest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.562 sec FAILURE! [run_with_no_replacement.story](pl.mmadej.jbehave.JBehaveStoriesTest) Time elapsed: 0.343 sec ERROR! org.jbehave.core.embedder.Embedder$RunningStoriesFailed: Failures in running before or after stories steps at org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:210) at pl.mmadej.jbehave.JBehaveStoriesTest.run(JBehaveStoriesTest.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Please investigate. This error happens with jbehave 3.4. When I'm using 3.3.2 everything looks ok. Internally there is NPE in StoryRunner:76 -- currentStrategy.get().handleFailure(storyFailure.get()); currentStrategy.get() returns null. Please investigate. Thanks in advance for your help -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-523) Allow specification of Configuration implementation class via @Configure annotation
Allow specification of Configuration implementation class via @Configure annotation --- Key: JBEHAVE-523 URL: http://jira.codehaus.org/browse/JBEHAVE-523 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.1 Currently starts from MostUsefulConfiguration as implementation on which other annotated properties are applied. In some cases, e.g. SeleniumConfiguration, user needs to specify a different starting implementation e.g. SeleniumConfiguration. Also, the specification of the implementation would allow users to use a custom implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-525) Add documentation page on tutorials
Add documentation page on tutorials --- Key: JBEHAVE-525 URL: http://jira.codehaus.org/browse/JBEHAVE-525 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi Priority: Minor Fix For: web-3.4, web-3.3.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-525) Add documentation page on tutorials
[ http://jira.codehaus.org/browse/JBEHAVE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-525. -- Resolution: Fixed Add documentation page on tutorials --- Key: JBEHAVE-525 URL: http://jira.codehaus.org/browse/JBEHAVE-525 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi Priority: Minor Fix For: web-3.4, web-3.3.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-524) Add page URL to screenshot console message
[ http://jira.codehaus.org/browse/JBEHAVE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-524: - Fix Version/s: web-3.3.4 Issue Type: Improvement (was: Bug) Summary: Add page URL to screenshot console message (was: Add correlating URL to screen-shots in output) Add page URL to screenshot console message -- Key: JBEHAVE-524 URL: http://jira.codehaus.org/browse/JBEHAVE-524 Project: JBehave Issue Type: Improvement Components: Web Selenium Reporter: Paul Hammant Assignee: Paul Hammant Fix For: web-3.4, web-3.3.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-527) Composed steps not being matched when using non-named parameter matching for the composite step
Composed steps not being matched when using non-named parameter matching for the composite step --- Key: JBEHAVE-527 URL: http://jira.codehaus.org/browse/JBEHAVE-527 Project: JBehave Issue Type: Bug Affects Versions: 3.4.1, 3.4 Environment: After the introduction of the specifications of parameters as meta (JBEHAVE-487) the composed steps are not being matched if meta parameters are specified as they superseed the parameters specified in the composite step. Need to merge the two set of parameters rather than choosing one over the other. Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-528) Examples Table for subset of steps
[
http://jira.codehaus.org/browse/JBEHAVE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-528:
-
Description:
http://jbehave.org/reference/stable/tabular-parameters.html is great, but
pertains to a single step.
{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter foo in the foo field
Then the bar field is auto-completed with bar
Examples:
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}
http://jbehave.org/reference/stable/parametrised-scenarios.html suggests that
all the Given/When/Then steps are repeated.
In the linked-to example, it is the only one given. What this change is about
is the fact that only the When/Then steps need to be repeated. This is
implicit because the Given line does not refer to any of the table params.
If this needs to be explicit, it could be a team's choice to set this for the
entire set of stories:
bq. configuration.setPartialExamplesTablesExpansionPerScenario(true);
Or it could be specified in the story itself:
{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter foo in the foo field
Then the bar field is auto-completed with bar
Examples(1-2):
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}
was:
http://jbehave.org/reference/stable/tabular-parameters.html is great, but
pertains to a single step.
{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter foo in the foo field
Then the bar field is auto-completed with bar
Examples:
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}
http://jbehave.org/reference/legacy/table-examples.html (note no /stable/
version of this page) gives the general theme, but suggests that all the
Given/When/Then steps are repeated.
In the linked-to example, it is the only one given. What this change is about
is the fact that only the When/Then steps need to be repeated. This is
implicit because the Given line does not refer to any of the table params.
If this needs to be explicit, it could be a team's choice to set this for the
entire set of stories:
bq. configuration.setPartialExamplesTablesExpansionPerScenario(true);
Or it could be specified in the story itself:
{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter foo in the foo field
Then the bar field is auto-completed with bar
Examples(1-2):
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}
Examples Table for subset of steps
--
Key: JBEHAVE-528
URL: http://jira.codehaus.org/browse/JBEHAVE-528
Project: JBehave
Issue Type: New Feature
Affects Versions: 3.4
Reporter: Paul Hammant
Priority: Minor
Fix For: 3.5
http://jbehave.org/reference/stable/tabular-parameters.html is great, but
pertains to a single step.
{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter foo in the foo field
Then the bar field is auto-completed with bar
Examples:
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}
http://jbehave.org/reference/stable/parametrised-scenarios.html suggests that
all the Given/When/Then steps are repeated.
In the linked-to example, it is the only one given. What this change is
about is the fact that only the When/Then steps need to be repeated. This is
implicit because the Given line does not refer to any of the table params.
If this needs to be explicit, it could be a team's choice to set this for the
entire set of stories:
bq. configuration.setPartialExamplesTablesExpansionPerScenario(true);
Or it could be specified in the story itself:
{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter foo in the foo field
Then the bar field is auto-completed with bar
Examples(1-2):
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-528) Examples Table for subset of steps
[
http://jira.codehaus.org/browse/JBEHAVE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=269442#action_269442
]
Mauro Talevi commented on JBEHAVE-528:
--
Composite steps (http://jbehave.org/reference/stable/composite-steps.html) is
one option that allows to group a subset of scenario steps.
Another approach is to have the part that is not repeated contained in a
GivenStory precondition, leaving the repeated steps in the parametrised
scenario.
Supporting the tabular parameters for arbitrary subset of steps is likely to be
non trivial, and possibly confusing unless we can come up with a clear way to
spell out which steps are executed in which order.
Examples Table for subset of steps
--
Key: JBEHAVE-528
URL: http://jira.codehaus.org/browse/JBEHAVE-528
Project: JBehave
Issue Type: New Feature
Affects Versions: 3.4
Reporter: Paul Hammant
Priority: Minor
Fix For: 3.5
http://jbehave.org/reference/stable/tabular-parameters.html is great, but
pertains to a single step.
{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter foo in the foo field
Then the bar field is auto-completed with bar
Examples:
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}
http://jbehave.org/reference/stable/parametrised-scenarios.html suggests that
all the Given/When/Then steps are repeated.
In the linked-to example, it is the only one given. What this change is
about is the fact that only the When/Then steps need to be repeated. This is
implicit because the Given line does not refer to any of the table params.
If this needs to be explicit, it could be a team's choice to set this for the
entire set of stories:
bq. configuration.setPartialExamplesTablesExpansionPerScenario(true);
Or it could be specified in the story itself:
{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter foo in the foo field
Then the bar field is auto-completed with bar
Examples(1-2):
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-527) Composed steps not being matched when using non-named parameter matching for the composite step
[ http://jira.codehaus.org/browse/JBEHAVE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-527. -- Resolution: Fixed Composed steps not being matched when using non-named parameter matching for the composite step --- Key: JBEHAVE-527 URL: http://jira.codehaus.org/browse/JBEHAVE-527 Project: JBehave Issue Type: Bug Affects Versions: 3.4, 3.4.1 Environment: After the introduction of the specifications of parameters as meta (JBEHAVE-487) the composed steps are not being matched if meta parameters are specified as they superseed the parameters specified in the composite step. Need to merge the two set of parameters rather than choosing one over the other. Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-529) Simplify trader-ant example to not depend on the Maven pom.xml
Simplify trader-ant example to not depend on the Maven pom.xml -- Key: JBEHAVE-529 URL: http://jira.codehaus.org/browse/JBEHAVE-529 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-529) Simplify trader-ant example to not depend on the Maven pom.xml
[ http://jira.codehaus.org/browse/JBEHAVE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-529. -- Resolution: Fixed Simplify trader-ant example to not depend on the Maven pom.xml -- Key: JBEHAVE-529 URL: http://jira.codehaus.org/browse/JBEHAVE-529 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-514) jbehave-maven-plugin ignoring execution
[
http://jira.codehaus.org/browse/JBEHAVE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-514:
-
Affects Version/s: (was: web-3.3.2)
3.3.2
Fix Version/s: (was: 3.x)
3.4.3
jbehave-maven-plugin ignoring execution
---
Key: JBEHAVE-514
URL: http://jira.codehaus.org/browse/JBEHAVE-514
Project: JBehave
Issue Type: Bug
Components: Maven Plugin
Affects Versions: 3.3.2
Environment: Ubuntu 10.4
Java 1.6
STS (Eclipse)
Maven 3.0-SNAPSHOT/0.10.0.201202009-0800) (via STS) or
Apache Maven 2.2.1 (rdebian-1)
Java version: 1.6.0_22
Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: linux version: 2.6.32-31-generic arch: amd64 Family: unix
JBehave 3.3.2
jbehave-maven-plugin 3.3.2
Reporter: Gavin Tranter
Priority: Critical
Fix For: 3.4.3
when trying to execute a package on a maven project with jbehave and
jbehave-maven-plugin configured Maven fails to execute the jbehave goal.
This is regardless of weather I execute it with in Eclipse or on the
commandline.
However if I issue the following command on the command line the
jbehave-maven-plugin is executed and runs the acceptance tests:
mvn clean package
org.jbehave:jbehave-maven-plugin:3.3.2:run-stories-as-embeddables
The command I use in Eclipse is:
jbehave:run-stories-as-embeddables
I have configured the jbehave plugin:
{noformat}
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.6/source
target1.6/target
/configuration
/plugin
plugin
groupIdorg.jbehave/groupId
artifactIdjbehave-maven-plugin/artifactId
version3.3.2/version
configuration
scopetest/scope
includes
include**/*.java/include
/includes
metaFilters
metaFilter+author */metaFilter
metaFilter-skip/metaFilter
/metaFilters
systemProperties
property
namejava.awt.headless/name
valuetrue/value
/property
/systemProperties
ignoreFailureInStoriestrue/ignoreFailureInStories
ignoreFailureInViewfalse/ignoreFailureInView
/configuration
executions
execution
idrun-stories-as-embeddables/id
phasetest/phase
goals
goalrun-stories-as-embeddables/goal
/goals
/execution
/executions
/plugin
/plugins
{noformat}
Thanks
Gavin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-514) jbehave-maven-plugin ignoring execution
[
http://jira.codehaus.org/browse/JBEHAVE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-514.
--
Resolution: Not A Bug
Meta filters are documented here:
http://jbehave.org/reference/stable/meta-filtering.html
jbehave-maven-plugin ignoring execution
---
Key: JBEHAVE-514
URL: http://jira.codehaus.org/browse/JBEHAVE-514
Project: JBehave
Issue Type: Bug
Components: Maven Plugin
Affects Versions: 3.3.2
Environment: Ubuntu 10.4
Java 1.6
STS (Eclipse)
Maven 3.0-SNAPSHOT/0.10.0.201202009-0800) (via STS) or
Apache Maven 2.2.1 (rdebian-1)
Java version: 1.6.0_22
Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: linux version: 2.6.32-31-generic arch: amd64 Family: unix
JBehave 3.3.2
jbehave-maven-plugin 3.3.2
Reporter: Gavin Tranter
Priority: Critical
Fix For: 3.4.3
when trying to execute a package on a maven project with jbehave and
jbehave-maven-plugin configured Maven fails to execute the jbehave goal.
This is regardless of weather I execute it with in Eclipse or on the
commandline.
However if I issue the following command on the command line the
jbehave-maven-plugin is executed and runs the acceptance tests:
mvn clean package
org.jbehave:jbehave-maven-plugin:3.3.2:run-stories-as-embeddables
The command I use in Eclipse is:
jbehave:run-stories-as-embeddables
I have configured the jbehave plugin:
{noformat}
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.6/source
target1.6/target
/configuration
/plugin
plugin
groupIdorg.jbehave/groupId
artifactIdjbehave-maven-plugin/artifactId
version3.3.2/version
configuration
scopetest/scope
includes
include**/*.java/include
/includes
metaFilters
metaFilter+author */metaFilter
metaFilter-skip/metaFilter
/metaFilters
systemProperties
property
namejava.awt.headless/name
valuetrue/value
/property
/systemProperties
ignoreFailureInStoriestrue/ignoreFailureInStories
ignoreFailureInViewfalse/ignoreFailureInView
/configuration
executions
execution
idrun-stories-as-embeddables/id
phasetest/phase
goals
goalrun-stories-as-embeddables/goal
/goals
/execution
/executions
/plugin
/plugins
{noformat}
Thanks
Gavin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-414) Document generating StepDocs from a Embeddable instance
[ http://jira.codehaus.org/browse/JBEHAVE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-414. -- Resolution: Fixed Document generating StepDocs from a Embeddable instance - Key: JBEHAVE-414 URL: http://jira.codehaus.org/browse/JBEHAVE-414 Project: JBehave Issue Type: Task Components: Core Reporter: Paul Hammant Assignee: Mauro Talevi Priority: Minor Fix For: 3.4.3 Step Docs pom xml needs an embedder, but not every project is going to have one. Etsy does not. Embeddable (EtsyDotComStories) makes an Embedder. Could it expose it for the StepDoc thingy to leverage? Alternatively, is it not really the Configuration that is needed by the reportStepdocs() method that the jbehave-plugin calls ? Could this be more flexible so that simpler cases that subclass JUnitStories ONLY can play with stepdocs production ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-414) Document generating StepDocs from a Embeddable instance
[ http://jira.codehaus.org/browse/JBEHAVE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-414: - Fix Version/s: (was: 3.x) 3.4.3 Assignee: Mauro Talevi Document generating StepDocs from a Embeddable instance - Key: JBEHAVE-414 URL: http://jira.codehaus.org/browse/JBEHAVE-414 Project: JBehave Issue Type: Task Components: Core Reporter: Paul Hammant Assignee: Mauro Talevi Priority: Minor Fix For: 3.4.3 Step Docs pom xml needs an embedder, but not every project is going to have one. Etsy does not. Embeddable (EtsyDotComStories) makes an Embedder. Could it expose it for the StepDoc thingy to leverage? Alternatively, is it not really the Configuration that is needed by the reportStepdocs() method that the jbehave-plugin calls ? Could this be more flexible so that simpler cases that subclass JUnitStories ONLY can play with stepdocs production ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-530) Add time duration to story statistics and reports view
Add time duration to story statistics and reports view -- Key: JBEHAVE-530 URL: http://jira.codehaus.org/browse/JBEHAVE-530 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.4 Add story time duration in ms -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-530) Add time duration to story statistics and reports view
[ http://jira.codehaus.org/browse/JBEHAVE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-530. -- Resolution: Fixed Add time duration to story statistics and reports view -- Key: JBEHAVE-530 URL: http://jira.codehaus.org/browse/JBEHAVE-530 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.4 Add story time duration in ms -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-521) Typo in jbehave-spring-archetype causes malformed pom.xml
[ http://jira.codehaus.org/browse/JBEHAVE-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-521: - Fix Version/s: 3.5 Typo in jbehave-spring-archetype causes malformed pom.xml - Key: JBEHAVE-521 URL: http://jira.codehaus.org/browse/JBEHAVE-521 Project: JBehave Issue Type: Bug Components: Archetypes Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.1, 3.5 /jbehave.sitee.version - /jbehave.site.version -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-522) Add documentation page on tutorials
[ http://jira.codehaus.org/browse/JBEHAVE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-522: - Fix Version/s: 3.5 Add documentation page on tutorials --- Key: JBEHAVE-522 URL: http://jira.codehaus.org/browse/JBEHAVE-522 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.4.1, 3.5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-520) StoryRunner failure strategy is not set when running before or after stories steps in multiple threads
[ http://jira.codehaus.org/browse/JBEHAVE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-520: - Fix Version/s: 3.5 StoryRunner failure strategy is not set when running before or after stories steps in multiple threads -- Key: JBEHAVE-520 URL: http://jira.codehaus.org/browse/JBEHAVE-520 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.4 Environment: Windowx XP, mvn 3.0.3 and 2.2.1, jbehave 3.4 Reporter: Maciej Madej Priority: Critical Fix For: 3.4.1, 3.5 Attachments: jbehave-after-before-bug.zip I got following exception when building attached project (mvn clean install): --- Test set: pl.mmadej.jbehave.JBehaveStoriesTest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.562 sec FAILURE! [run_with_no_replacement.story](pl.mmadej.jbehave.JBehaveStoriesTest) Time elapsed: 0.343 sec ERROR! org.jbehave.core.embedder.Embedder$RunningStoriesFailed: Failures in running before or after stories steps at org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:210) at pl.mmadej.jbehave.JBehaveStoriesTest.run(JBehaveStoriesTest.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Please investigate. This error happens with jbehave 3.4. When I'm using 3.3.2 everything looks ok. Internally there is NPE in StoryRunner:76 -- currentStrategy.get().handleFailure(storyFailure.get()); currentStrategy.get() returns null. Please investigate. Thanks in advance for your help -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-523) Allow specification of Configuration implementation class via @Configure annotation
[ http://jira.codehaus.org/browse/JBEHAVE-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-523: - Fix Version/s: 3.5 Allow specification of Configuration implementation class via @Configure annotation --- Key: JBEHAVE-523 URL: http://jira.codehaus.org/browse/JBEHAVE-523 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.1, 3.5 Currently starts from MostUsefulConfiguration as implementation on which other annotated properties are applied. In some cases, e.g. SeleniumConfiguration, user needs to specify a different starting implementation e.g. SeleniumConfiguration. Also, the specification of the implementation would allow users to use a custom implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-531) OutcomesTable not being reported
OutcomesTable not being reported Key: JBEHAVE-531 URL: http://jira.codehaus.org/browse/JBEHAVE-531 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.4, 3.3 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.5, 3.5 Regression due to the introduction of the UUIDExceptionWrapper: the wrapped OutcomesFailed exception is not detected and the OutcomesTable is not reported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-531) OutcomesTable not being reported
[ http://jira.codehaus.org/browse/JBEHAVE-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-531. -- Resolution: Fixed OutcomesTable not being reported Key: JBEHAVE-531 URL: http://jira.codehaus.org/browse/JBEHAVE-531 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.3, 3.4 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.5, 3.5 Regression due to the introduction of the UUIDExceptionWrapper: the wrapped OutcomesFailed exception is not detected and the OutcomesTable is not reported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-532) Upgrade to hamcrest-library 1.2
Upgrade to hamcrest-library 1.2 --- Key: JBEHAVE-532 URL: http://jira.codehaus.org/browse/JBEHAVE-532 Project: JBehave Issue Type: Task Components: Core Affects Versions: 3.4 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 From 1.2 Hamcrest has deprecated hamcrest-all and moved to a modules with transitive dependencies. jbehave-core should depend on org.hamcrest:hamcrest-library. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-532) Split hamcrest-all dependency
[ http://jira.codehaus.org/browse/JBEHAVE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-532: - Description: From 1.2.x Hamcrest has removed hamcrest-all and moved to separate modules hamcrest-library and hamcrest-integration (with transitive dependencies). was: From 1.2 Hamcrest has deprecated hamcrest-all and moved to a modules with transitive dependencies. jbehave-core should depend on org.hamcrest:hamcrest-library. Fix Version/s: 3.4.5 Summary: Split hamcrest-all dependency (was: Upgrade to hamcrest-library 1.2) Split hamcrest-all dependency - Key: JBEHAVE-532 URL: http://jira.codehaus.org/browse/JBEHAVE-532 Project: JBehave Issue Type: Task Components: Core Affects Versions: 3.4 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.5, 3.5 From 1.2.x Hamcrest has removed hamcrest-all and moved to separate modules hamcrest-library and hamcrest-integration (with transitive dependencies). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-532) Split hamcrest-all dependency
[ http://jira.codehaus.org/browse/JBEHAVE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-532. -- Resolution: Fixed Split hamcrest-all dependency - Key: JBEHAVE-532 URL: http://jira.codehaus.org/browse/JBEHAVE-532 Project: JBehave Issue Type: Task Components: Core Affects Versions: 3.4 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.5, 3.5 From 1.2.x Hamcrest has removed hamcrest-all and moved to separate modules hamcrest-library and hamcrest-integration (with transitive dependencies). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-532) Split hamcrest-all dependency
[ http://jira.codehaus.org/browse/JBEHAVE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-532: - Description: From 1.2.x Hamcrest has removed hamcrest-all. As for 1.1 separate modules are available: - hamcrest-core: provides the API, unlikely to change much: used at compile time in jbehave-core for OutcomesTable - hamcrest-library: provides the library of Matchers - hamcrest-integration: provides integration with other tools, e.g. JUnit, JMock etc ... Making jbehave-core depend explicitly on the separate modules allows uses to override individual modules (e.g. hamcrest-library) via the POM dependency management. was: From 1.2.x Hamcrest has removed hamcrest-all and moved to separate modules hamcrest-library and hamcrest-integration (with transitive dependencies). Split hamcrest-all dependency - Key: JBEHAVE-532 URL: http://jira.codehaus.org/browse/JBEHAVE-532 Project: JBehave Issue Type: Task Components: Core Affects Versions: 3.4 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4.5, 3.5 From 1.2.x Hamcrest has removed hamcrest-all. As for 1.1 separate modules are available: - hamcrest-core: provides the API, unlikely to change much: used at compile time in jbehave-core for OutcomesTable - hamcrest-library: provides the library of Matchers - hamcrest-integration: provides integration with other tools, e.g. JUnit, JMock etc ... Making jbehave-core depend explicitly on the separate modules allows uses to override individual modules (e.g. hamcrest-library) via the POM dependency management. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-533) Bad encoding in JBehave Raports with default configuration from jbehave archetype in Windows
[
http://jira.codehaus.org/browse/JBEHAVE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=270075#action_270075
]
Mauro Talevi commented on JBEHAVE-533:
--
Hi, so you seem to be using PL chars in the textual story but not in the Java
steps class.
Can you try running the trader-i18n example stories and see if they work for
you?
Bad encoding in JBehave Raports with default configuration from jbehave
archetype in Windows
Key: JBEHAVE-533
URL: http://jira.codehaus.org/browse/JBEHAVE-533
Project: JBehave
Issue Type: Bug
Environment: Windows
Reporter: Mariusz Smykula
Attachments: wrong-encoding-sample-prj.tar.gz,
wrong-encoding-sample-prj.zip
I have created project from archetype with command:
{{mvn archetype:generate -DarchetypeGroupId=org.jbehave
-DarchetypeArtifactId=jbehave-spring-archetype}}
and edited my.story file (added some international chars)
After this
There is:
??A scenario with some pending steps
#313;‚#258;#322;#313;›#313;#317;#313;‚#313;›#258;#322;a#313;›Ä™#313;‚??
Should be:
??Scenario: A scenario with some pending steps
#322;ó#347;#380;#322;#347;óa#347;#281;#322;?? - here is proper
encoded letters
I have edited pom.xml and added:
{{project.build.sourceEncodingUTF-8/project.build.sourceEncoding}}
{{project.reporting.outputEncodingUTF-8/project.reporting.outputEncoding}}
in properties section.
The HTML and XML raport should be properly encoded after this. I think option
-Dfile.encoding=UTF-8 should be not required for this. Maven project should
have identical results on all platforms if properly configured.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-534) Lazy instantiation of steps classes, only if candidate steps are matched
Lazy instantiation of steps classes, only if candidate steps are matched Key: JBEHAVE-534 URL: http://jira.codehaus.org/browse/JBEHAVE-534 Project: JBehave Issue Type: New Feature Components: Core, Groovy Support, Guice Support, Pico Support, Spring Support, Weld Support Affects Versions: 3.4 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 As suggested by Paul, the eager instantiation of steps classes is unnecessary. Candidate steps can be matched using the steps type and the steps instances should be instantiated only if the candidate steps are matched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-534) Lazy instantiation of steps classes, only if candidate steps are matched
[ http://jira.codehaus.org/browse/JBEHAVE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-534 started by Mauro Talevi. Lazy instantiation of steps classes, only if candidate steps are matched Key: JBEHAVE-534 URL: http://jira.codehaus.org/browse/JBEHAVE-534 Project: JBehave Issue Type: New Feature Components: Core, Groovy Support, Guice Support, Pico Support, Spring Support, Weld Support Affects Versions: 3.4 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 As suggested by Paul, the eager instantiation of steps classes is unnecessary. Candidate steps can be matched using the steps type and the steps instances should be instantiated only if the candidate steps are matched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-536) Allow stories that don't match filters not to be reported
Allow stories that don't match filters not to be reported - Key: JBEHAVE-536 URL: http://jira.codehaus.org/browse/JBEHAVE-536 Project: JBehave Issue Type: Improvement Affects Versions: 3.4 Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.5 Currently, stories that are not matched by filters are reported but not run. Allow option to silently ignore them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-537) Pluggable template processor for view generator
Pluggable template processor for view generator Key: JBEHAVE-537 URL: http://jira.codehaus.org/browse/JBEHAVE-537 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-535) Template-based reporters
[ http://jira.codehaus.org/browse/JBEHAVE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-535 started by Mauro Talevi. Template-based reporters Key: JBEHAVE-535 URL: http://jira.codehaus.org/browse/JBEHAVE-535 Project: JBehave Issue Type: New Feature Components: Core Affects Versions: 3.4 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 Currently, most reporters are PrintStream-based and configurable via a set of properties. Provide template-based implementations that: - build up the report context during the execution - generate the report using the context at the end of the execution using a configurable template -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-537) Pluggable template processor for view generator
[ http://jira.codehaus.org/browse/JBEHAVE-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-537: - Fix Version/s: 3.5 Pluggable template processor for view generator Key: JBEHAVE-537 URL: http://jira.codehaus.org/browse/JBEHAVE-537 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-537) Pluggable template processor for view generator
[ http://jira.codehaus.org/browse/JBEHAVE-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-537 started by Mauro Talevi. Pluggable template processor for view generator Key: JBEHAVE-537 URL: http://jira.codehaus.org/browse/JBEHAVE-537 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-539) ConcurrentModificationException in xref when run multithreaded.
[ http://jira.codehaus.org/browse/JBEHAVE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-539: - Fix Version/s: 3.5 Assignee: Paul Hammant ConcurrentModificationException in xref when run multithreaded. --- Key: JBEHAVE-539 URL: http://jira.codehaus.org/browse/JBEHAVE-539 Project: JBehave Issue Type: Bug Affects Versions: 3.4.5 Reporter: Paul Hammant Assignee: Paul Hammant Fix For: 3.5 This causes Jenkins to choke when in does not find a /story for the story in question (the xunit plugin stage): [WARNING] Failed to run story loyalty/RapidRewards_extend_awards.story java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) at java.util.AbstractList$Itr.next(AbstractList.java:343) at org.jbehave.core.reporters.CrossReference$XRefRoot.processStories(CrossReference.java:273) at org.jbehave.core.reporters.CrossReference.createXRefRoot(CrossReference.java:115) at org.jbehave.core.reporters.CrossReference.outputToFiles(CrossReference.java:96) at org.jbehave.core.reporters.CrossReference$1.afterStory(CrossReference.java:206) at org.jbehave.core.reporters.ConcurrentStoryReporter.afterStory(ConcurrentStoryReporter.java:114) at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:263) at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:163) at org.jbehave.core.embedder.Embedder$EnqueuedStory.call(Embedder.java:686) at org.jbehave.core.embedder.Embedder$EnqueuedStory.call(Embedder.java:650) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-538) Wrong encoding in reports running from JUnit (maven failsafe or surefire plugin, not dedicated jebhave maven plugin) on Windows
[
http://jira.codehaus.org/browse/JBEHAVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=270888#comment-270888
]
Mauro Talevi commented on JBEHAVE-538:
--
Why do you say that encoding issues only occur when not running via the maven
plugin?
Seems to me that problem is independent of the way they are run.
Wrong encoding in reports running from JUnit (maven failsafe or surefire
plugin, not dedicated jebhave maven plugin) on Windows
---
Key: JBEHAVE-538
URL: http://jira.codehaus.org/browse/JBEHAVE-538
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.4.2, 3.4.3, 3.4.4, 3.4.5
Environment: Windows, for example with cp1250 encoding (Poland/PL)
Reporter: Mariusz Smykula
Labels: encoding, i18n, junit, maven
Attachments: wrong-encoding-sample-prj (2).zip
With -Dfile.encoding=UTF-8 FreeMaker still is using and rendering html report
with cp1250 encoding, output log from maven install command:
...
(stories/sample.story)
Scenario: Przyk#322;adowy scenariusz numer 1 #347;#380;ó#322;
Given Given co#347;tam#378;#322;ó#347; (PENDING)
When By#322;ó#347;#380;#378;#324;#346;#260; (PENDING)
Then G#380;eg#380;ó#322;k#261; (PENDING)
@Given(Given
co\u0139\u203Atam\u0139\u015F\u0139\u201A\u0102\u0142\u0139\u203A)
...
Generating reports view to
'e:\Jenkins\jobs\jbehave-encoding-test\workspace\target\jbehave' using
formats '[console, txt, html, stats]' and view properties '
Unknown macro: {defaultFormats=stats, decorateNonHtml=true,
viewDirectory=view, decorated=ftl/jbehave-report-decorated.ftl,
reports=ftl/jbehave-reports-with-totals.ftl, maps=ftl/jbehave-maps.ftl,
navigator=ftl/jbehave-navigator.ftl, views=ftl/jbehave-views.ftl,
nonDecorated=ftl/jbehave-report-non-decorated.ftl}
'
[encoding-test] DEBUG Could not find template in cache, creating new one;
id=[ftl/jbehave-report-decorated.ftl[pl_PL,Cp1250,parsed] ]
[encoding-test] DEBUG Compiling FreeMarker template
ftl/jbehave-report-decorated.ftl[pl_PL,Cp1250,parsed] from
jar:file:/C:/.m2/repository/org/jbehave/jbehave-core/3.4.4/jbehave-core-3.4.4.jar!/ftl/jbehave-report-decorated.ftl
[encoding-test] DEBUG Could not find template in cache, creating new one;
id=[ftl/sh.ftl[pl_PL,Cp1250,parsed] ]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-540) Color-coded console output
Color-coded console output -- Key: JBEHAVE-540 URL: https://jira.codehaus.org/browse/JBEHAVE-540 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Fix For: 3.5 As contributed by Adriano Bonat: https://github.com/tanob/jbehave-core/commit/1de6908065a085621c4b9576b589d7e005aee606 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-540) ANSI-coded console output
[ https://jira.codehaus.org/browse/JBEHAVE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-540: - Description: As contributed by Adriano Bonat: https://github.com/tanob/jbehave-core/commit/1de6908065a085621c4b9576b589d7e005aee606 was: As contributed by Adriano Bonat: https://github.com/tanob/jbehave-core/commit/1de6908065a085621c4b9576b589d7e005aee606 Summary: ANSI-coded console output (was: Color-coded console output) ANSI-coded console output - Key: JBEHAVE-540 URL: https://jira.codehaus.org/browse/JBEHAVE-540 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Fix For: 3.5 As contributed by Adriano Bonat: https://github.com/tanob/jbehave-core/commit/1de6908065a085621c4b9576b589d7e005aee606 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-541) Meta tags (and other things) injectable into components
[ https://jira.codehaus.org/browse/JBEHAVE-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=271134#comment-271134 ] Mauro Talevi commented on JBEHAVE-541: -- What are the usecases you are trying to address? What one may do is to define an interface MetaEnabled that steps classes can optionally implement and the current Meta can be passed on to the instance (ah the good ol' Avalon days are coming back). You can't have any parsed data (including Meta) injected into the constructors of the steps classes without doing very complicated back flipping and throwing IoC out the window. Meta tags (and other things) injectable into components --- Key: JBEHAVE-541 URL: https://jira.codehaus.org/browse/JBEHAVE-541 Project: JBehave Issue Type: New Feature Components: Guice Support, Pico Support, Spring Support Reporter: Paul Hammant Meta tags can be injected into step methods. They can't be injected into step-pojo constructors, nor in any capacity to components that are themselves injectable into step-pojo constructors. Workaround people have to do: accept the meta-tag into the step-pojo's step method and hand it to wherever needs. In our particular case, Page objects are being made by a DI container, and it would be better separation of concerns to have meta tags injected where they are needed, and not in the steps class (which only passes them on). The senior developer in question wishes, in lieu of something better, that StoryRunner.RunContext.Meta was statically available (on a thread local) and that page objects could pull it when they need it. That's a breach of IoC of course, but you get why he wishes for it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-544) JBehave !-- Comments amongst meta tags causes corrupt XML output
[ https://jira.codehaus.org/browse/JBEHAVE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=271136#comment-271136 ] Mauro Talevi commented on JBEHAVE-544: -- The syntax of meta do not recognise !-- at the moment, only the separator @. Hence, !-- is as valid as any other char set. Meta is not parsed like the rest of the story, it is parsed in isolation. We can support comments but we need to know how to define the syntax. JBehave !-- Comments amongst meta tags causes corrupt XML output Key: JBEHAVE-544 URL: https://jira.codehaus.org/browse/JBEHAVE-544 Project: JBehave Issue Type: Bug Reporter: Paul Hammant Jenkins subsequently barfs because of an XSLT transform (xUnit plugin). Can we cater for comments amongst meta-tags? Either parse and handle them, or fail to parse explicitly :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-544) JBehave !-- Comments amongst meta tags causes corrupt XML output
[ https://jira.codehaus.org/browse/JBEHAVE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=271136#comment-271136 ] Mauro Talevi edited comment on JBEHAVE-544 at 6/22/11 1:47 PM: --- The syntax of meta do not recognise !-- at the moment, only the separator @. Hence, !-- is as valid as any other char set. Meta is not parsed like the rest of the story, it is parsed in isolation. We can support comments but we need to know how to define the syntax. was (Author: maurotalevi): The syntax of meta do not recognise !-- at the moment, only the separator @. Hence, !-- is as valid as any other char set. Meta is not parsed like the rest of the story, it is parsed in isolation. We can support comments but we need to know how to define the syntax. JBehave !-- Comments amongst meta tags causes corrupt XML output Key: JBEHAVE-544 URL: https://jira.codehaus.org/browse/JBEHAVE-544 Project: JBehave Issue Type: Bug Reporter: Paul Hammant Jenkins subsequently barfs because of an XSLT transform (xUnit plugin). Can we cater for comments amongst meta-tags? Either parse and handle them, or fail to parse explicitly :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-544) JBehave !-- Comments amongst meta tags causes corrupt XML output
[ https://jira.codehaus.org/browse/JBEHAVE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=271138#comment-271138 ] Mauro Talevi commented on JBEHAVE-544: -- Can you provide an example of an invalid XML and how you would encode it? JBehave !-- Comments amongst meta tags causes corrupt XML output Key: JBEHAVE-544 URL: https://jira.codehaus.org/browse/JBEHAVE-544 Project: JBehave Issue Type: Bug Reporter: Paul Hammant Jenkins subsequently barfs because of an XSLT transform (xUnit plugin). Can we cater for comments amongst meta-tags? Either parse and handle them, or fail to parse explicitly :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-544) Ignore !-- comments in story meta
[ https://jira.codehaus.org/browse/JBEHAVE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-544: - Description: Jenkins barfs when finding !-- during the XSLT transform (xUnit plugin). Can we cater for comments amongst meta-tags? Either parse and handle them, or fail to parse explicitly :) was: Jenkins subsequently barfs because of an XSLT transform (xUnit plugin). Can we cater for comments amongst meta-tags? Either parse and handle them, or fail to parse explicitly :) Priority: Minor (was: Major) Fix Version/s: 3.5 Issue Type: Improvement (was: Bug) Summary: Ignore !-- comments in story meta (was: JBehave !-- Comments amongst meta tags causes corrupt XML output) Ignore !-- comments in story meta - Key: JBEHAVE-544 URL: https://jira.codehaus.org/browse/JBEHAVE-544 Project: JBehave Issue Type: Improvement Reporter: Paul Hammant Priority: Minor Fix For: 3.5 Jenkins barfs when finding !-- during the XSLT transform (xUnit plugin). Can we cater for comments amongst meta-tags? Either parse and handle them, or fail to parse explicitly :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-544) Ignore !-- comments in story meta
[ https://jira.codehaus.org/browse/JBEHAVE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-544. -- Resolution: Fixed Anything after ignorable keyword (!-- by default) is ignored in meta properties. Ignore !-- comments in story meta - Key: JBEHAVE-544 URL: https://jira.codehaus.org/browse/JBEHAVE-544 Project: JBehave Issue Type: Improvement Reporter: Paul Hammant Priority: Minor Fix For: 3.5 Jenkins barfs when finding !-- during the XSLT transform (xUnit plugin). Can we cater for comments amongst meta-tags? Either parse and handle them, or fail to parse explicitly :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-546) Reports are not showing properly, all are showing as Zero
[ https://jira.codehaus.org/browse/JBEHAVE-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-546. -- Resolution: Not A Bug Fix Version/s: 3.5 You're missing the stats, which are used in the report generation. You can either invoke withDefaultFormats() on the StoryReporterBuilder, or add Format.STATS directly to withFormats(). You may also use archetypes to get started on a project: http://jbehave.org/reference/stable/archetypes.html Reports are not showing properly, all are showing as Zero - Key: JBEHAVE-546 URL: https://jira.codehaus.org/browse/JBEHAVE-546 Project: JBehave Issue Type: Bug Components: Core, IDE Support, Maven Plugin Affects Versions: 3.1.1, 3.4.5 Environment: Windows XP2, used maven-dependency-plugin for jbehave-site-resources 3.1.1, jbehave-maven-plugin 3.4.5, junit 4.8.2, jbehave core 3.4.5. Reporter: Chandra Sekhar K Labels: eclipse, junit, maven, plugin Fix For: 3.5 Attachments: cc_JBehaveSample.zip Original Estimate: 2 days Remaining Estimate: 2 days i used an example to create JBehave Scenarios, i fallowed as given in the Jbehave documentation but facing a problem getting report generated. i didn't find the solution to get count the scenarios and Steps or testcases. is their any configuration i am missing? i am attaching all the files used. Thank you in Advance. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-547) StoryRunner.runParametrisedScenariosByExamples does not execute the examples after the first failure
[
https://jira.codehaus.org/browse/JBEHAVE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-547:
-
Fix Version/s: 3.5
StoryRunner.runParametrisedScenariosByExamples does not execute the examples
after the first failure
Key: JBEHAVE-547
URL: https://jira.codehaus.org/browse/JBEHAVE-547
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.4.5
Environment: Windows XP, Eclipse Helios
Reporter: Plamen Gurov
Fix For: 3.5
Currently, the method StoryRunner.runParametrisedScenariosByExamples does not
check the configuration and whenever a step fails all subsequent examples are
reported as not performed.
A simple fix would be to do this before calling the runScenarioSteps method:
if(context.configuration().storyControls().resetStateBeforeScenario()) {
context.resetState();
}
Thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-547) StoryRunner.runParametrisedScenariosByExamples does not execute the examples after the first failure
[
https://jira.codehaus.org/browse/JBEHAVE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-547.
--
Resolution: Fixed
StoryRunner.runParametrisedScenariosByExamples does not execute the examples
after the first failure
Key: JBEHAVE-547
URL: https://jira.codehaus.org/browse/JBEHAVE-547
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.4.5
Environment: Windows XP, Eclipse Helios
Reporter: Plamen Gurov
Fix For: 3.5
Currently, the method StoryRunner.runParametrisedScenariosByExamples does not
check the configuration and whenever a step fails all subsequent examples are
reported as not performed.
A simple fix would be to do this before calling the runScenarioSteps method:
if(context.configuration().storyControls().resetStateBeforeScenario()) {
context.resetState();
}
Thanks
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-550) StoryReporterBuilder does not have an easy way to provide custom StoryReporter(s)
[ https://jira.codehaus.org/browse/JBEHAVE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272004#comment-272004 ] Mauro Talevi commented on JBEHAVE-550: -- The StoryReporterBuilder provides the method withFormats(Formats...) for this purpose. The Format implementation allows you to create your instance of StoryReporter. StoryReporterBuilder does not have an easy way to provide custom StoryReporter(s) - Key: JBEHAVE-550 URL: https://jira.codehaus.org/browse/JBEHAVE-550 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.4.5 Reporter: Lance Priority: Minor I recently wanted to add my own StoryReporter to every story and found it quite difficult. It would be great if StoryReporterBuilder could have one of the following methods added withStoryReporters(StoryReporter... storyReporters) addStoryReporter(StoryReporter storyReporter) The only way I could find was to override StoryReporterBuilder.build(String storyPath) and use a DelegatingStoryReporter to include my custom storyReporter(s). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment
[
https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272240#comment-272240
]
Mauro Talevi commented on JBEHAVE-543:
--
Thanks Adriano, looks like some nice very work at first sight. I'll dig in a
bit deeper tomorrow.
Just one thing, can you avoid removing unnecessary comments :-)
https://github.com/tanob/jbehave-core/commit/d28f43d843d425dafe0087eba23c62e1c742a1ed
Before/After Story/Scenario methods could accept parameters that have meaning
at that moment
Key: JBEHAVE-543
URL: https://jira.codehaus.org/browse/JBEHAVE-543
Project: JBehave
Issue Type: New Feature
Reporter: Paul Hammant
For example -
bq. public void myBeforeStory(@Named(someMetaTag) String someMetaTag) { .. }
This would be a poor-mans version of JBEHAVE-541
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment
[
https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-543:
-
Fix Version/s: 3.5
Assignee: Mauro Talevi
Before/After Story/Scenario methods could accept parameters that have meaning
at that moment
Key: JBEHAVE-543
URL: https://jira.codehaus.org/browse/JBEHAVE-543
Project: JBehave
Issue Type: New Feature
Reporter: Paul Hammant
Assignee: Mauro Talevi
Fix For: 3.5
For example -
bq. public void myBeforeStory(@Named(someMetaTag) String someMetaTag) { .. }
This would be a poor-mans version of JBEHAVE-541
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment
[
https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272629#comment-272629
]
Mauro Talevi commented on JBEHAVE-543:
--
Adriano, I pulled your commits (except the one above) but there is a
regression. The trader-weld example fails.
Have you tried running mvn clean install -Pexamples on
git://github.com/tanob/jbehave-core.git?
Looks like a NPE somewhere in the class names. But Weld is not exactly
generous with debug help :-(
Before/After Story/Scenario methods could accept parameters that have meaning
at that moment
Key: JBEHAVE-543
URL: https://jira.codehaus.org/browse/JBEHAVE-543
Project: JBehave
Issue Type: New Feature
Reporter: Paul Hammant
Assignee: Mauro Talevi
Fix For: 3.5
For example -
bq. public void myBeforeStory(@Named(someMetaTag) String someMetaTag) { .. }
This would be a poor-mans version of JBEHAVE-541
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment
[
https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JBEHAVE-543 started by Mauro Talevi.
Before/After Story/Scenario methods could accept parameters that have meaning
at that moment
Key: JBEHAVE-543
URL: https://jira.codehaus.org/browse/JBEHAVE-543
Project: JBehave
Issue Type: New Feature
Reporter: Paul Hammant
Assignee: Mauro Talevi
Fix For: 3.5
For example -
bq. public void myBeforeStory(@Named(someMetaTag) String someMetaTag) { .. }
This would be a poor-mans version of JBEHAVE-541
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-540) ANSI-coded console output
[ https://jira.codehaus.org/browse/JBEHAVE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-540 started by Mauro Talevi. ANSI-coded console output - Key: JBEHAVE-540 URL: https://jira.codehaus.org/browse/JBEHAVE-540 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 As contributed by Adriano Bonat: https://github.com/tanob/jbehave-core/commit/1de6908065a085621c4b9576b589d7e005aee606 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment
[
https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-543:
-
Component/s: Core
Before/After Story/Scenario methods could accept parameters that have meaning
at that moment
Key: JBEHAVE-543
URL: https://jira.codehaus.org/browse/JBEHAVE-543
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Paul Hammant
Assignee: Mauro Talevi
Fix For: 3.5
For example -
bq. public void myBeforeStory(@Named(someMetaTag) String someMetaTag) { .. }
This would be a poor-mans version of JBEHAVE-541
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Assigned: (JBEHAVE-540) ANSI-coded console output
[ https://jira.codehaus.org/browse/JBEHAVE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-540: Assignee: Mauro Talevi ANSI-coded console output - Key: JBEHAVE-540 URL: https://jira.codehaus.org/browse/JBEHAVE-540 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 As contributed by Adriano Bonat: https://github.com/tanob/jbehave-core/commit/1de6908065a085621c4b9576b589d7e005aee606 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-551) Better integration with JUnit (Separate results for each story/scenario/example)
[ https://jira.codehaus.org/browse/JBEHAVE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-551: - Fix Version/s: 3.5 Assignee: Mauro Talevi Better integration with JUnit (Separate results for each story/scenario/example) Key: JBEHAVE-551 URL: https://jira.codehaus.org/browse/JBEHAVE-551 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.4.5 Reporter: Lance Assignee: Mauro Talevi Fix For: 3.5 Attachments: eclipse-screenshot.jpg, jbehave-improved-junit-runner.zip, jbehave-parent-runner-src.zip I would like each example in each scenario in each story to show up as distinct result in the JUnit test results within my IDE and the JUnit reports. This has the advantage that assertion failures are linked to example failures and can be clicked on in the IDE to jump to source code of the offending failure. Currently I get a single failure in my IDE and have to look through log files or look at the JBehave report. The current AnnotatedPathRunner implementation extends org.junit.runners.BlockJUnit4ClassRunner and therefore uses the methods with a @Test annotation to drive the JUnit results. In most jbehave tests, there is only one such method which means that there is only a single result in the JUnit reports (IDE and HTML). I have started to implement a new org.junit.runner.Runner implementation which extends org.junit.runners.ParentRunner and can use the stories as the basis for generating the JUnit test results rather than the Test case itself. I have attached a screenshot and source code for running a single test (jbehave.ListTest) in Eclipse. The test case runs a single story (list.story). You can see from the results that there is a hierarchy in the JUnit results for story, scenario and example. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-528) Examples Table for subset of steps
[
https://jira.codehaus.org/browse/JBEHAVE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-528:
-
Fix Version/s: (was: 3.5)
3.x
Examples Table for subset of steps
--
Key: JBEHAVE-528
URL: https://jira.codehaus.org/browse/JBEHAVE-528
Project: JBehave
Issue Type: New Feature
Affects Versions: 3.4
Reporter: Paul Hammant
Priority: Minor
Fix For: 3.x
http://jbehave.org/reference/stable/tabular-parameters.html is great, but
pertains to a single step.
{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter foo in the foo field
Then the bar field is auto-completed with bar
Examples:
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}
http://jbehave.org/reference/stable/parametrised-scenarios.html suggests that
all the Given/When/Then steps are repeated.
In the linked-to example, it is the only one given. What this change is
about is the fact that only the When/Then steps need to be repeated. This is
implicit because the Given line does not refer to any of the table params.
If this needs to be explicit, it could be a team's choice to set this for the
entire set of stories:
bq. configuration.setPartialExamplesTablesExpansionPerScenario(true);
Or it could be specified in the story itself:
{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter foo in the foo field
Then the bar field is auto-completed with bar
Examples(1-2):
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-553) Upgrade to Weld 1.1.1
Upgrade to Weld 1.1.1 - Key: JBEHAVE-553 URL: https://jira.codehaus.org/browse/JBEHAVE-553 Project: JBehave Issue Type: Improvement Components: Weld Support Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Critical Fix For: 3.5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment
[
https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272741#comment-272741
]
Mauro Talevi commented on JBEHAVE-543:
--
Upgraded to Weld 1.1.1 in JBEHAVE-553.
Before/After Story/Scenario methods could accept parameters that have meaning
at that moment
Key: JBEHAVE-543
URL: https://jira.codehaus.org/browse/JBEHAVE-543
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Paul Hammant
Assignee: Mauro Talevi
Fix For: 3.5
For example -
bq. public void myBeforeStory(@Named(someMetaTag) String someMetaTag) { .. }
This would be a poor-mans version of JBEHAVE-541
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment
[
https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272746#comment-272746
]
Mauro Talevi commented on JBEHAVE-543:
--
Pulled commits into master up to
https://github.com/tanob/jbehave-core/commit/32b6770d8661ce942ac76c88549071d9998b332e
Can you please merge with master?
Yes, we should get the example in CI. I'm actually planning to move away from
Codehaus Bamboo, as I find some features annoying (like the non possibility of
deleting build configs).
Any suggestion on where we should set up JBehave CI?
Before/After Story/Scenario methods could accept parameters that have meaning
at that moment
Key: JBEHAVE-543
URL: https://jira.codehaus.org/browse/JBEHAVE-543
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Paul Hammant
Assignee: Mauro Talevi
Fix For: 3.5
For example -
bq. public void myBeforeStory(@Named(someMetaTag) String someMetaTag) { .. }
This would be a poor-mans version of JBEHAVE-541
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-554) Upgrade to Selenium 2.0.0 final
Upgrade to Selenium 2.0.0 final --- Key: JBEHAVE-554 URL: https://jira.codehaus.org/browse/JBEHAVE-554 Project: JBehave Issue Type: Task Components: Web Selenium Reporter: Mauro Talevi Fix For: web-3.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-548) @BeforeExample und @AfterExample
[ https://jira.codehaus.org/browse/JBEHAVE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-548: - Fix Version/s: 3.5 @BeforeExample und @AfterExample Key: JBEHAVE-548 URL: https://jira.codehaus.org/browse/JBEHAVE-548 Project: JBehave Issue Type: New Feature Components: Core Affects Versions: 3.4.5 Reporter: Andreas Ebbert-Karroum Fix For: 3.5 It would be nice to have annotations (or any other way) to run some methods before and after each example. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment
[
https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273226#comment-273226
]
Mauro Talevi commented on JBEHAVE-543:
--
Hi Adriano, I've pulled your commits. Did not see any issues with them.
What do you mean by refactoring StepCreator to only have MethodInvoker?
Examples of the new feature would be most welcome.
Thanks for your great work!
Before/After Story/Scenario methods could accept parameters that have meaning
at that moment
Key: JBEHAVE-543
URL: https://jira.codehaus.org/browse/JBEHAVE-543
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Paul Hammant
Assignee: Mauro Talevi
Fix For: 3.5
For example -
bq. public void myBeforeStory(@Named(someMetaTag) String someMetaTag) { .. }
This would be a poor-mans version of JBEHAVE-541
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-374) Upgrade to commons-lang 3.0 to correctly escape characters from the Unicode Supplemental Multilingual Plane
[ https://jira.codehaus.org/browse/JBEHAVE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-374: - Fix Version/s: (was: 3.x) 3.5 Assignee: Mauro Talevi Upgrade to commons-lang 3.0 to correctly escape characters from the Unicode Supplemental Multilingual Plane --- Key: JBEHAVE-374 URL: https://jira.codehaus.org/browse/JBEHAVE-374 Project: JBehave Issue Type: Task Components: Core Affects Versions: 3.0.3 Environment: Windows 7, 64-bit Reporter: Alistair Dutton Assignee: Mauro Talevi Priority: Minor Fix For: 3.5 If one includes characters from the Unicode Supplemental Multilingual Plane (code points U+1 upwards) in a story file, if one then asks for an HTML report from the test run the characters will not be HTML-escaped correctly. For example, given a story file with the following scenario: Scenario: Some scenario Given some situation When I do something Then the result is #66566; (The dagger-type character is actually code point U+10406 - see http://en.wikibooks.org/wiki/Unicode/Character_reference/1-10FFF) The resulting HTML report will have the dagger character escaped as #55297;#56326; - which represent surrogate-pair code points (used in UTF-16 only) and so is rendered as gibberish in HTML. The escape should be #x10406; NOTE: This is NOT a bug in JBehave per se - the bug is in the StringEscapeUtils class of commons-lang. A related bug has already been raised (and fixed) in commons-lang: https://issues.apache.org/jira/browse/LANG-617. Although the commons-lang bug report relates to XML escaping rather than HTML escaping, it seems likely that the fix will cover both. Unfortunately, the fix is in commons-lang 3.0... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-558) Maven build should be updated to play well with Eclipse m2e 1.0
Maven build should be updated to play well with Eclipse m2e 1.0 --- Key: JBEHAVE-558 URL: https://jira.codehaus.org/browse/JBEHAVE-558 Project: JBehave Issue Type: Task Components: Build Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 As of m2e 1.0 (part of Eclipse Indigo 3.7 release), explicit instructions are required on how to handle the Maven plugins bound to interesting phases: http://wiki.eclipse.org/M2E_plugin_execution_not_covered This does not affect the command-line build, only the Maven integration with Eclipse. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-558) Maven build should be updated to play well with Eclipse m2e 1.0
[ https://jira.codehaus.org/browse/JBEHAVE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-558 started by Mauro Talevi. Maven build should be updated to play well with Eclipse m2e 1.0 --- Key: JBEHAVE-558 URL: https://jira.codehaus.org/browse/JBEHAVE-558 Project: JBehave Issue Type: Task Components: Build Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 As of m2e 1.0 (part of Eclipse Indigo 3.7 release), explicit instructions are required on how to handle the Maven plugins bound to interesting phases: http://wiki.eclipse.org/M2E_plugin_execution_not_covered This does not affect the command-line build, only the Maven integration with Eclipse. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-564) Update Ant and Maven configuration documentation
Update Ant and Maven configuration documentation - Key: JBEHAVE-564 URL: https://jira.codehaus.org/browse/JBEHAVE-564 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.5 Review and update the configuration of the properties, for both Ant tasks and Maven goals. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-565) Make public StoryRunner.State interface
Make public StoryRunner.State interface Key: JBEHAVE-565 URL: https://jira.codehaus.org/browse/JBEHAVE-565 Project: JBehave Issue Type: Task Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.5 Mockito on linux complains about State interface not being visible. Does little harm to upgrade interface visibility to public, while implementations are kepts private. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-565) Make public StoryRunner.State interface
[ https://jira.codehaus.org/browse/JBEHAVE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-565. -- Resolution: Fixed Make public StoryRunner.State interface Key: JBEHAVE-565 URL: https://jira.codehaus.org/browse/JBEHAVE-565 Project: JBehave Issue Type: Task Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.5 Mockito on linux complains about State interface not being visible. Does little harm to upgrade interface visibility to public, while implementations are kepts private. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-567) Excluded (filtered-out) scenarios are reported as pending as well
[
https://jira.codehaus.org/browse/JBEHAVE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-567:
-
Fix Version/s: 3.5
Assignee: Mauro Talevi
Excluded (filtered-out) scenarios are reported as pending as well
-
Key: JBEHAVE-567
URL: https://jira.codehaus.org/browse/JBEHAVE-567
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.4.5
Reporter: Jaroslav Sedlacek
Assignee: Mauro Talevi
Fix For: 3.5
Excluded (filtered-out) scenarios are reported as pending as well.
Set metadata on scenario and set metafilter so the scenario is ignored. It
will be reported as pending too.
this bug has been probably introduced by JBEHAVE-471. The problem is caused
by
{{org.jbehave.core.reporters.PostStoryStatisticsCollector.afterScenario()}}
as the method does not differ if no steps has ben executed because scenario
is not implemented/pending or because scenario was excluded.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-570) Excluded scenarios should not be included into ScenarioSuccessful count
[ https://jira.codehaus.org/browse/JBEHAVE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-570. -- Resolution: Fixed Fix Version/s: 3.5 Applied patch with thanks. Excluded scenarios should not be included into ScenarioSuccessful count --- Key: JBEHAVE-570 URL: https://jira.codehaus.org/browse/JBEHAVE-570 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.4.5 Reporter: Jaroslav Sedlacek Fix For: 3.5 Attachments: JBEHAVE-570%3A+Excluded+scenarios+should+not+be+included+into+ScenarioSuccessful.patch Excluded scenarios should not be included into ScenarioSuccessful count. Let's say we have story with 5 scenarios and metafilter will exclude 3 of them. This story will be reported then with 5 Total Scenarios, 5 Successful Scenarios and 3 Excluded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-571) Shorten method and annotation signature in BeforeOrAfterFalled message
Shorten method and annotation signature in BeforeOrAfterFalled message -- Key: JBEHAVE-571 URL: https://jira.codehaus.org/browse/JBEHAVE-571 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.5 As Paul noted, the message in the BeforeOrAfterFailed message can be too verbose and confusing when reading logs. Should be shorted to include method short name, annotations short names and class, e.g.: Method aFailingBeforeScenarioMethod (annotated with @BeforeScenario in class org.jbehave.core.steps.SomeSteps) failed: java.lang.RuntimeException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-571) Compatify method and annotation information in BeforeOrAfterFalled message
[ https://jira.codehaus.org/browse/JBEHAVE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-571 started by Mauro Talevi. Compatify method and annotation information in BeforeOrAfterFalled message -- Key: JBEHAVE-571 URL: https://jira.codehaus.org/browse/JBEHAVE-571 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.5 As Paul noted, the message in the BeforeOrAfterFailed message can be too verbose and confusing when reading logs. Should be shorted to include method short name, annotations short names and class, e.g.: Method aFailingBeforeScenarioMethod (annotated with @BeforeScenario in class org.jbehave.core.steps.SomeSteps) failed: java.lang.RuntimeException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-571) Compatify method and annotation information in BeforeOrAfterFalled message
[ https://jira.codehaus.org/browse/JBEHAVE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-571: - Summary: Compatify method and annotation information in BeforeOrAfterFalled message (was: Shorten method and annotation signature in BeforeOrAfterFalled message) Compatify method and annotation information in BeforeOrAfterFalled message -- Key: JBEHAVE-571 URL: https://jira.codehaus.org/browse/JBEHAVE-571 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.5 As Paul noted, the message in the BeforeOrAfterFailed message can be too verbose and confusing when reading logs. Should be shorted to include method short name, annotations short names and class, e.g.: Method aFailingBeforeScenarioMethod (annotated with @BeforeScenario in class org.jbehave.core.steps.SomeSteps) failed: java.lang.RuntimeException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-571) Compactify method and annotation information in BeforeOrAfterFalled message
[ https://jira.codehaus.org/browse/JBEHAVE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-571: - Summary: Compactify method and annotation information in BeforeOrAfterFalled message (was: Compatify method and annotation information in BeforeOrAfterFalled message) Compactify method and annotation information in BeforeOrAfterFalled message --- Key: JBEHAVE-571 URL: https://jira.codehaus.org/browse/JBEHAVE-571 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.5 As Paul noted, the message in the BeforeOrAfterFailed message can be too verbose and confusing when reading logs. Should be shorted to include method short name, annotations short names and class, e.g.: Method aFailingBeforeScenarioMethod (annotated with @BeforeScenario in class org.jbehave.core.steps.SomeSteps) failed: java.lang.RuntimeException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-557) When story has multiple failed scenarios, only one screenshot is created
[ https://jira.codehaus.org/browse/JBEHAVE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-557. -- Resolution: Fixed Pulled commit: https://github.com/karacz/jbehave-core/commit/0c81e1f5e49bf8ee70615b15ae0546991c40b6bc When story has multiple failed scenarios, only one screenshot is created Key: JBEHAVE-557 URL: https://jira.codehaus.org/browse/JBEHAVE-557 Project: JBehave Issue Type: Bug Components: Web Selenium Affects Versions: web-3.3.4 Reporter: Jaroslav Sedlacek Fix For: 3.5 When story has multiple failed scenarios, only one screenshot is created. Problem is StoryRunner holds first failure for the rest of the story. WebDriverScreenshotOnFailure then generates all screenshots from the same GUID and writing them them all into the same file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-557) When story has multiple failed scenarios, only one screenshot is created
[ https://jira.codehaus.org/browse/JBEHAVE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-557: - Fix Version/s: 3.5 When story has multiple failed scenarios, only one screenshot is created Key: JBEHAVE-557 URL: https://jira.codehaus.org/browse/JBEHAVE-557 Project: JBehave Issue Type: Bug Components: Web Selenium Affects Versions: web-3.3.4 Reporter: Jaroslav Sedlacek Fix For: 3.5 When story has multiple failed scenarios, only one screenshot is created. Problem is StoryRunner holds first failure for the rest of the story. WebDriverScreenshotOnFailure then generates all screenshots from the same GUID and writing them them all into the same file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-573) Step Marked as PENDING without preceding FAILED step - silent failure???
[ https://jira.codehaus.org/browse/JBEHAVE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=274889#comment-274889 ] Mauro Talevi commented on JBEHAVE-573: -- What's the usecase for the different method signature? Step Marked as PENDING without preceding FAILED step - silent failure??? Key: JBEHAVE-573 URL: https://jira.codehaus.org/browse/JBEHAVE-573 Project: JBehave Issue Type: Bug Components: Core Reporter: David Batchelor In a pull of master today, but using that JBehave-Core with client code, we have a case where the scenario output looks like :- Given foo When bar And I never get to this line (PENDING) Then it does not matter about this line (NOT PERFORMED) We can 100% assert that I never get to this line matches a single well defined step, with no sound-alikes. We can't see a FAILED line, which is our usual experience with JBehave We can see a Selenium screenshot, but we don't know what that pertains to, and it does not show anything that looks like an error. We're not sure why it was produced. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-577) Flash support
Flash support - Key: JBEHAVE-577 URL: https://jira.codehaus.org/browse/JBEHAVE-577 Project: JBehave Issue Type: New Feature Components: Web Selenium Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.4 A WebDriverProvider implementation that supports invocation of SWF object methods via Javascript. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-575) Upgrade Selenium to 2.3.1
[ https://jira.codehaus.org/browse/JBEHAVE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-575: - Fix Version/s: web-3.4 Upgrade Selenium to 2.3.1 - Key: JBEHAVE-575 URL: https://jira.codehaus.org/browse/JBEHAVE-575 Project: JBehave Issue Type: Task Reporter: Paul Hammant Assignee: Paul Hammant Priority: Trivial Fix For: web-3.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-577) Flash support
[ https://jira.codehaus.org/browse/JBEHAVE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-577 started by Mauro Talevi. Flash support - Key: JBEHAVE-577 URL: https://jira.codehaus.org/browse/JBEHAVE-577 Project: JBehave Issue Type: New Feature Components: Web Selenium Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.4 A WebDriverProvider implementation that supports invocation of SWF object methods via Javascript. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-568) Selenium 2.1.0 upgrade
[ https://jira.codehaus.org/browse/JBEHAVE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-568: - Fix Version/s: web-3.4 Issue Type: Task (was: Improvement) Selenium 2.1.0 upgrade -- Key: JBEHAVE-568 URL: https://jira.codehaus.org/browse/JBEHAVE-568 Project: JBehave Issue Type: Task Components: Web Selenium Reporter: Paul Hammant Assignee: Paul Hammant Fix For: web-3.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-554) Upgrade to Selenium 2.0.0 final
[ https://jira.codehaus.org/browse/JBEHAVE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-554. -- Resolution: Fixed Upgrade to Selenium 2.0.0 final --- Key: JBEHAVE-554 URL: https://jira.codehaus.org/browse/JBEHAVE-554 Project: JBehave Issue Type: Task Components: Web Selenium Reporter: Mauro Talevi Fix For: web-3.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-568) Selenium 2.1.0 upgrade
[ https://jira.codehaus.org/browse/JBEHAVE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-568: - Component/s: Web Selenium Selenium 2.1.0 upgrade -- Key: JBEHAVE-568 URL: https://jira.codehaus.org/browse/JBEHAVE-568 Project: JBehave Issue Type: Task Components: Web Selenium Reporter: Paul Hammant Assignee: Paul Hammant Fix For: web-3.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-572) Selenium 2.2 upgrade.
[ https://jira.codehaus.org/browse/JBEHAVE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-572: - Fix Version/s: web-3.4 Selenium 2.2 upgrade. - Key: JBEHAVE-572 URL: https://jira.codehaus.org/browse/JBEHAVE-572 Project: JBehave Issue Type: Task Reporter: Paul Hammant Assignee: Paul Hammant Priority: Minor Fix For: web-3.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-572) Selenium 2.2 upgrade.
[ https://jira.codehaus.org/browse/JBEHAVE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-572: - Component/s: Web Selenium Selenium 2.2 upgrade. - Key: JBEHAVE-572 URL: https://jira.codehaus.org/browse/JBEHAVE-572 Project: JBehave Issue Type: Task Components: Web Selenium Reporter: Paul Hammant Assignee: Paul Hammant Priority: Minor Fix For: web-3.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-576) Allow for setting of environment vars on Firefox binary (for DISPLAY amongst others)
[ https://jira.codehaus.org/browse/JBEHAVE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-576: - Fix Version/s: web-3.4 Allow for setting of environment vars on Firefox binary (for DISPLAY amongst others) Key: JBEHAVE-576 URL: https://jira.codehaus.org/browse/JBEHAVE-576 Project: JBehave Issue Type: Improvement Components: Web Selenium Reporter: Paul Hammant Assignee: Paul Hammant Priority: Minor Fix For: web-3.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-578) Story execution not failing-fast when ignoreFailuresInStories=false
Story execution not failing-fast when ignoreFailuresInStories=false --- Key: JBEHAVE-578 URL: https://jira.codehaus.org/browse/JBEHAVE-578 Project: JBehave Issue Type: Bug Affects Versions: 3.4 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 This is a regression introduced with multi-thread support. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-578) Story execution not failing-fast when ignoreFailuresInStories=false
[ https://jira.codehaus.org/browse/JBEHAVE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-578 started by Mauro Talevi. Story execution not failing-fast when ignoreFailuresInStories=false --- Key: JBEHAVE-578 URL: https://jira.codehaus.org/browse/JBEHAVE-578 Project: JBehave Issue Type: Bug Affects Versions: 3.4 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.5 This is a regression introduced with multi-thread support. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-582) Base WebDriverPage should implement HasCapabilities, JavascriptExecutor and HasInputDevices
[ https://jira.codehaus.org/browse/JBEHAVE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-582: - Affects Version/s: (was: 3.5) Fix Version/s: (was: 3.5) web-3.4 Base WebDriverPage should implement HasCapabilities, JavascriptExecutor and HasInputDevices --- Key: JBEHAVE-582 URL: https://jira.codehaus.org/browse/JBEHAVE-582 Project: JBehave Issue Type: Improvement Components: Web Selenium Reporter: Paul Hammant Assignee: Paul Hammant Priority: Minor Fix For: web-3.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-583) Of multiple exclusion meta filters only one is evaluated
[
https://jira.codehaus.org/browse/JBEHAVE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-583:
-
Fix Version/s: 3.5
Thanks, added test cases.
Of multiple exclusion meta filters only one is evaluated
Key: JBEHAVE-583
URL: https://jira.codehaus.org/browse/JBEHAVE-583
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.4.5
Reporter: Dennis Homann
Fix For: 3.5
Attachments: MetaFilterReproducerTest.java
Assuming meta info
{noformat}
Meta:
@environment all
@skip
{noformat}
the following filter may not exclude the scenario, although it should:
{noformat}
-environment preview -skip
{noformat}
Method {{match}} in {{MetaFilter}} returns immediately when one filter
expression does not match. If environment is tested before skip,
{{match}} will return {{false}}, and scenario will not be excluded. The logic
should be changed such that {{match}} will return {{true}}, iff any exclusion
filter matches.
The actual order of evaluation depends on the order of property names
returned by #getPropertyNames, which appears to be alphabetical.
{noformat}
private boolean match(Properties properties, Meta meta) {
for (Object key : properties.keySet()) {
String property = (String) properties.get(key);
for (String metaName : meta.getPropertyNames()) {
if (key.equals(metaName)) {
String value = meta.getProperty(metaName);
if (StringUtils.isBlank(value)) {
return true;
} else if (property.contains(*)) {
return value.matches(property.replace(*, .*));
}
return properties.get(key).equals(value);
}
}
}
return false;
}
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-584) Support loading stories from Google Docs
[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-584: - Assignee: Mauro Talevi Support loading stories from Google Docs Key: JBEHAVE-584 URL: https://jira.codehaus.org/browse/JBEHAVE-584 Project: JBehave Issue Type: New Feature Components: Core, ODF Support Reporter: Bart De Neuter Assignee: Mauro Talevi Priority: Minor Fix For: 3.5 Attachments: googledocs.patch As a BA I want to be able to write my story in Google Docs. This has the advantage that the stories are in the cloud and multiple stakeholders (BA, developer, ...) work at the same time on the same document. By using the Google docs API, a document can be exported to ODT and be delegated to the ODT support in JBehave. ATTENTION: the given patch contains also a fix for the class OdfUtils in the module jbehave-odf. The class OdfTextExtractor is used to convert ODT correctly to text. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-584) Support loading stories from Google Docs
[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-584 started by Mauro Talevi. Support loading stories from Google Docs Key: JBEHAVE-584 URL: https://jira.codehaus.org/browse/JBEHAVE-584 Project: JBehave Issue Type: New Feature Components: Core, ODF Support Reporter: Bart De Neuter Assignee: Mauro Talevi Priority: Minor Fix For: 3.5 Attachments: googledocs.patch As a BA I want to be able to write my story in Google Docs. This has the advantage that the stories are in the cloud and multiple stakeholders (BA, developer, ...) work at the same time on the same document. By using the Google docs API, a document can be exported to ODT and be delegated to the ODT support in JBehave. ATTENTION: the given patch contains also a fix for the class OdfUtils in the module jbehave-odf. The class OdfTextExtractor is used to convert ODT correctly to text. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-583) Of multiple exclusion meta filters only one is evaluated
[
https://jira.codehaus.org/browse/JBEHAVE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-583.
--
Resolution: Fixed
Assignee: Mauro Talevi
Of multiple exclusion meta filters only one is evaluated
Key: JBEHAVE-583
URL: https://jira.codehaus.org/browse/JBEHAVE-583
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.4.5
Reporter: Dennis Homann
Assignee: Mauro Talevi
Fix For: 3.5
Attachments: MetaFilterReproducerTest.java
Assuming meta info
{noformat}
Meta:
@environment all
@skip
{noformat}
the following filter may not exclude the scenario, although it should:
{noformat}
-environment preview -skip
{noformat}
Method {{match}} in {{MetaFilter}} returns immediately when one filter
expression does not match. If environment is tested before skip,
{{match}} will return {{false}}, and scenario will not be excluded. The logic
should be changed such that {{match}} will return {{true}}, iff any exclusion
filter matches.
The actual order of evaluation depends on the order of property names
returned by #getPropertyNames, which appears to be alphabetical.
{noformat}
private boolean match(Properties properties, Meta meta) {
for (Object key : properties.keySet()) {
String property = (String) properties.get(key);
for (String metaName : meta.getPropertyNames()) {
if (key.equals(metaName)) {
String value = meta.getProperty(metaName);
if (StringUtils.isBlank(value)) {
return true;
} else if (property.contains(*)) {
return value.matches(property.replace(*, .*));
}
return properties.get(key).equals(value);
}
}
}
return false;
}
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-585) BeforeStories.xml can be zero length ( causing xUnit to fail a Jenkins job )
[
https://jira.codehaus.org/browse/JBEHAVE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=276738#comment-276738
]
Mauro Talevi commented on JBEHAVE-585:
--
So what is the proposed fix from JBehave's pov (i.e. not Jenkins')?
BeforeStories.xml can be zero length ( causing xUnit to fail a Jenkins job )
Key: JBEHAVE-585
URL: https://jira.codehaus.org/browse/JBEHAVE-585
Project: JBehave
Issue Type: Bug
Components: Core
Reporter: Paul Hammant
Priority: Minor
Fix For: 3.5
Never fear, the following can fix it so that the Jenkins job can complete:
find $WORKSPACE/project/target/jbehave -maxdepth 1 -type f -size 0 -exec
rm -f {} \;
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
