[jbehave-dev] [jira] Resolved: (JBEHAVE-360) Improve tabular story report
[ http://jira.codehaus.org/browse/JBEHAVE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-360. -- Resolution: Fixed Improve tabular story report - Key: JBEHAVE-360 URL: http://jira.codehaus.org/browse/JBEHAVE-360 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.0.2 Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1 Feedback from colleagues' first use of tabular story report introduced in 3.0.2 (JBEHAVE-339). - The layout is too dispersive, too much white space and table runs away out of page - Unnecessary (or misleading) repetitions of column headers, such as Successful and Failed - More difficult to spot failures, only numbers are colour-coded Suggestions include: - Have a top-level multi-column row with two headers, Scenarios and Steps. - Use logos (with hovering text) for Successful, Failed, Pending etc ... - Colour-code in red the story name in case of failure -- 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-372) Parametrised GivenStories
[
http://jira.codehaus.org/browse/JBEHAVE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-372.
--
Resolution: Fixed
Parametrised GivenStories
-
Key: JBEHAVE-372
URL: http://jira.codehaus.org/browse/JBEHAVE-372
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Fix For: 3.1
GivenStories could be parametrised, using the same mechanism of the
ExamplesTable and the named parameters.
If a GivenStory path has an anchor with a number, e.g.
GivenStories: /path/to/precondition.story#{0}
then the number is assumed to be the row of the ExamplesTable containing the
required parameters (if present).
--
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-358) Add Story Mapping with Swimlane view
[ http://jira.codehaus.org/browse/JBEHAVE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-358. -- Resolution: Fixed Add Story Mapping with Swimlane view Key: JBEHAVE-358 URL: http://jira.codehaus.org/browse/JBEHAVE-358 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.1 In order to get visibility of themes/epics As a release planner I want to be able to map stories by meta filters Using story maps allows us to group stories of cross-cutting concerns, using filters on meta info (JBEHAVE-220). A swimlane view (with one lane per filter) would allow a clear and concise view. -- 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-365) Add Groovy support
[ http://jira.codehaus.org/browse/JBEHAVE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-365. -- Resolution: Fixed Add Groovy support -- Key: JBEHAVE-365 URL: http://jira.codehaus.org/browse/JBEHAVE-365 Project: JBehave Issue Type: New Feature Components: Groovy Support Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.1 Starting from Adriano Bonat's contribution via GitHub (http://github.com/tanob/jbehave-core), add a jbehave-groovy module with extensions of core for Groovy-specific support, similarly to IOC framework extensions (Guice, Pico, Spring). Initially, it will contain a GroovyStepsFactory to create steps instances from Groovy scripts. It should also provide support for @UsingGroovy annotation, to specify the GroovyClassLoader and the GroovyResourceFinder. -- 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-373) BigDecimal-converted parameters don't preserve number of digits
BigDecimal-converted parameters don't preserve number of digits --- Key: JBEHAVE-373 URL: http://jira.codehaus.org/browse/JBEHAVE-373 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.0 Reporter: Mauro Talevi Assignee: Paul Hammant Priority: Minor Fix For: 3.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] Resolved: (JBEHAVE-373) BigDecimal-converted parameters don't preserve number of digits
[ http://jira.codehaus.org/browse/JBEHAVE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-373. -- Resolution: Fixed BigDecimal-converted parameters don't preserve number of digits --- Key: JBEHAVE-373 URL: http://jira.codehaus.org/browse/JBEHAVE-373 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.0 Reporter: Mauro Talevi Assignee: Paul Hammant Priority: Minor Fix For: 3.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] Resolved: (JBEHAVE-337) Document how to configure jbehave-maven-plugin to be aware of log4j dependency
[ http://jira.codehaus.org/browse/JBEHAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-337. -- Resolution: Fixed Updated maven-goals.html page. Document how to configure jbehave-maven-plugin to be aware of log4j dependency -- Key: JBEHAVE-337 URL: http://jira.codehaus.org/browse/JBEHAVE-337 Project: JBehave Issue Type: Task Components: Maven Plugin Affects Versions: 3.0 Environment: Ubuntu 10.4, sun java 1.6.0_20-b02, maven 2.2.1 Reporter: Jonathan Choate Fix For: 3.1 Attachments: log4j-error.tar.gz If my pom.xml contains a dependency on log4j then when I run the target mvn integration-test I get a stack trace indicating that the jbehave-maven-plugin can't find the log4j classes. I've attached a trivial maven project that reproduces the issue. I do not see this issue when I run the tests in eclipse as junit tests and the tests run fine if I remove log4j. The following is the complete stack trace: java.lang.NoClassDefFoundError: org/apache/log4j/Priority at freemarker.log.Log4JLoggerFactory.getLogger(Log4JLoggerFactory.java:65) at freemarker.log.Logger.getLogger(Logger.java:255) at freemarker.template.utility.SecurityUtilities.clinit(SecurityUtilities.java:67) at freemarker.ext.beans.BeansWrapper.clinit(BeansWrapper.java:147) at freemarker.template.ObjectWrapper.clinit(ObjectWrapper.java:69) at freemarker.core.Configurable.init(Configurable.java:132) at freemarker.template.Configuration.init(Configuration.java:109) at freemarker.template.Configuration.clinit(Configuration.java:96) at org.jbehave.core.reporters.FreemarkerViewGenerator.configure(FreemarkerViewGenerator.java:208) at org.jbehave.core.reporters.FreemarkerViewGenerator.init(FreemarkerViewGenerator.java:60) at org.jbehave.core.configuration.Configuration.init(Configuration.java:159) at org.jbehave.core.configuration.MostUsefulConfiguration.init(MostUsefulConfiguration.java:49) at org.jbehave.core.embedder.Embedder.init(Embedder.java:30) at org.jbehave.core.embedder.Embedder.init(Embedder.java:37) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.jbehave.core.embedder.EmbedderClassLoader.newInstance(EmbedderClassLoader.java:37) at org.jbehave.mojo.AbstractEmbedderMojo.newEmbedder(AbstractEmbedderMojo.java:228) at org.jbehave.mojo.RunStoriesAsEmbeddables.execute(RunStoriesAsEmbeddables.java:15) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Priority at
[jbehave-dev] [jira] Updated: (JBEHAVE-370) IDE_CONSOLE no longer any different to IDE (w.r.t console output)
[ http://jira.codehaus.org/browse/JBEHAVE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-370: - Fix Version/s: (was: 3.1) 3.2 Assignee: Paul Hammant IDE_CONSOLE no longer any different to IDE (w.r.t console output) - Key: JBEHAVE-370 URL: http://jira.codehaus.org/browse/JBEHAVE-370 Project: JBehave Issue Type: Bug Affects Versions: 3.1 Reporter: Paul Hammant Assignee: Paul Hammant Fix For: 3.2 I've noticed recently a problem with IDE_CONSOLE. It (or more particularly the IdeOnlyConsoleOutput class) is being ignored. If you do a Maven run from the command line, for a project that uses a normal on JB3.1/JUnit tool chain you can see it. Put in a strategic throw, or loop/sys-out for the current threads stack trace, you don't have the prerequisite packages in the stack (I've checked), yet it still dump to console :-( Maybe there is a System.out somewhere that is ignore this configuration choice. -- 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-375) Add unpack-resources goal to Maven Plugin
Add unpack-resources goal to Maven Plugin - Key: JBEHAVE-375 URL: http://jira.codehaus.org/browse/JBEHAVE-375 Project: JBehave Issue Type: Improvement Components: Maven Plugin Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1 A goal to unpack the resources to the view directory. The main advantage over the maven dependency plugin is the ability to derived the directory location from the configured StoryReporterBuilder accessible via the Embedder. The resources are configured as normal project artifacts and can be filtered based on the resource dependency type (by defaults all zip artifacts are allowed). Different types are configurable via the resourceTypes property. Resource content can optionally be filtered based on the resourceIncludes/Excludes properties. -- 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] Work started: (JBEHAVE-375) Add unpack-resources goal to Maven Plugin
[ http://jira.codehaus.org/browse/JBEHAVE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-375 started by Mauro Talevi. Add unpack-resources goal to Maven Plugin - Key: JBEHAVE-375 URL: http://jira.codehaus.org/browse/JBEHAVE-375 Project: JBehave Issue Type: Improvement Components: Maven Plugin Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1 A goal to unpack the resources to the view directory. The main advantage over the maven dependency plugin is the ability to derived the directory location from the configured StoryReporterBuilder accessible via the Embedder. The resources are configured as normal project artifacts and can be filtered based on the resource dependency type (by defaults all zip artifacts are allowed). Different types are configurable via the resourceTypes property. Resource content can optionally be filtered based on the resourceIncludes/Excludes properties. -- 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-375) Add unpack-view-resources goal to Maven Plugin
[
http://jira.codehaus.org/browse/JBEHAVE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-375.
--
Resolution: Fixed
Add unpack-view-resources goal to Maven Plugin
--
Key: JBEHAVE-375
URL: http://jira.codehaus.org/browse/JBEHAVE-375
Project: JBehave
Issue Type: Improvement
Components: Maven Plugin
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Priority: Minor
Fix For: 3.1
A goal to unpack the resources to the view directory. The main advantage
over the maven dependency plugin is the ability to derived the view directory
location from the configured StoryReporterBuilder accessible via the Embedder.
The resources are configured as normal project artifacts and can be filtered
based on the resource dependency type and artifactIds, via properties
resourceType and resourceArtifacIds
(which default to zip and {jbehave-core, jbehave-site-resources}).
Resource content can optionally be filtered based on the
resourceIncludes/Excludes properties.
--
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-375) Add unpack-view-resources goal to Maven Plugin
[
http://jira.codehaus.org/browse/JBEHAVE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-375:
-
Description:
A goal to unpack the resources to the view directory. The main advantage over
the maven dependency plugin is the ability to derived the view directory
location from the configured StoryReporterBuilder accessible via the Embedder.
The resources are configured as normal project artifacts and can be filtered
based on the resource dependency type and artifactIds, via properties
resourceType and resourceArtifacIds
(which default to zip and {jbehave-core, jbehave-site-resources}).
Resource content can optionally be filtered based on the
resourceIncludes/Excludes properties.
was:
A goal to unpack the resources to the view directory. The main advantage over
the maven dependency plugin is the ability to derived the directory location
from the configured StoryReporterBuilder accessible via the Embedder.
The resources are configured as normal project artifacts and can be filtered
based on the resource dependency type (by defaults all zip artifacts are
allowed). Different types are configurable via the resourceTypes property.
Resource content can optionally be filtered based on the
resourceIncludes/Excludes properties.
Summary: Add unpack-view-resources goal to Maven Plugin (was: Add
unpack-resources goal to Maven Plugin)
Add unpack-view-resources goal to Maven Plugin
--
Key: JBEHAVE-375
URL: http://jira.codehaus.org/browse/JBEHAVE-375
Project: JBehave
Issue Type: Improvement
Components: Maven Plugin
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Priority: Minor
Fix For: 3.1
A goal to unpack the resources to the view directory. The main advantage
over the maven dependency plugin is the ability to derived the view directory
location from the configured StoryReporterBuilder accessible via the Embedder.
The resources are configured as normal project artifacts and can be filtered
based on the resource dependency type and artifactIds, via properties
resourceType and resourceArtifacIds
(which default to zip and {jbehave-core, jbehave-site-resources}).
Resource content can optionally be filtered based on the
resourceIncludes/Excludes properties.
--
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-374) Characters from the Unicode Supplemental Multilingual Plane included in story definitions get rendered incorrectly in HTML
[ http://jira.codehaus.org/browse/JBEHAVE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-374: - Issue Type: Task (was: Bug) Changed to task as reminder to upgrade to commons-lang 3.0 when released. Characters from the Unicode Supplemental Multilingual Plane included in story definitions get rendered incorrectly in HTML -- Key: JBEHAVE-374 URL: http://jira.codehaus.org/browse/JBEHAVE-374 Project: JBehave Issue Type: Task Affects Versions: 3.0.3 Environment: Windows 7, 64-bit Reporter: Alistair Dutton Priority: Minor 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. - 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-378) Add support for meta filtering in story running
Add support for meta filtering in story running Key: JBEHAVE-378 URL: http://jira.codehaus.org/browse/JBEHAVE-378 Project: JBehave Issue Type: Improvement Components: Web Runner Affects Versions: web-3.0 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.1 Upgrade to 3.1 as default Core dependency. Support specification of meta filters in the Run Story page. If meta filters not set, it should use the 3.0.x compatible StoryRunner method, so users are not forced to upgrade to 3.1, until they need to. That meta filtering is a 3.1 only features should also be notified on the Run Story page. -- 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-345) Add support for WebDriver API
[ http://jira.codehaus.org/browse/JBEHAVE-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-345: - Description: Add support for the WebDriver API, new feature of Selenium 2.0. The support for the WebDriver API will complement the support for the Selenium API, featured in both Selenium 1.0 and 2.0. was:Added support for WebDriver, similarly to support for Selenium. Summary: Add support for WebDriver API (was: Add WebDriver support) Add support for WebDriver API - Key: JBEHAVE-345 URL: http://jira.codehaus.org/browse/JBEHAVE-345 Project: JBehave Issue Type: New Feature Components: Web Selenium Reporter: Mauro Talevi Assignee: Paul Hammant Fix For: web-3.1 Add support for the WebDriver API, new feature of Selenium 2.0. The support for the WebDriver API will complement the support for the Selenium API, featured in both Selenium 1.0 and 2.0. -- 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-345) Add support for WebDriver API
[ http://jira.codehaus.org/browse/JBEHAVE-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-345. -- Resolution: Fixed Add support for WebDriver API - Key: JBEHAVE-345 URL: http://jira.codehaus.org/browse/JBEHAVE-345 Project: JBehave Issue Type: New Feature Components: Web Selenium Reporter: Mauro Talevi Assignee: Paul Hammant Fix For: web-3.1 Add support for the WebDriver API, new feature of Selenium 2.0. The support for the WebDriver API will complement the support for the Selenium API, featured in both Selenium 1.0 and 2.0. -- 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-379) Allow scenarios following a failed scenarios to be skipped in a single story
Allow scenarios following a failed scenarios to be skipped in a single story Key: JBEHAVE-379 URL: http://jira.codehaus.org/browse/JBEHAVE-379 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1 Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1.1 Allow option to skip scenarios following a failed scenario in a single story. -- 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-380) Allow story controls to be configurable via annotations
Allow story controls to be configurable via annotations Key: JBEHAVE-380 URL: http://jira.codehaus.org/browse/JBEHAVE-380 Project: JBehave Issue Type: Improvement Components: Core, Guice Support, Pico Support, Spring Support Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1.1 The StoryControls configuration element should be configurable via annotations, @Configure or @UsingGuice|Pico|Spring. -- 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-380) Allow story controls to be configurable via annotations
[ http://jira.codehaus.org/browse/JBEHAVE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-380. -- Resolution: Fixed Allow story controls to be configurable via annotations Key: JBEHAVE-380 URL: http://jira.codehaus.org/browse/JBEHAVE-380 Project: JBehave Issue Type: Improvement Components: Core, Guice Support, Pico Support, Spring Support Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1.1 The StoryControls configuration element should be configurable via annotations, @Configure or @UsingGuice|Pico|Spring. -- 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-376) JBehave Eclipse plugin
[ http://jira.codehaus.org/browse/JBEHAVE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-376: - Affects Version/s: (was: 3.0) (was: web-3.0) (was: 2.5) Fix Version/s: (was: 3.0) ide-3.0 Summary: JBehave Eclipse plugin (was: JBehave eclipse plugin project) JBehave Eclipse plugin --- Key: JBEHAVE-376 URL: http://jira.codehaus.org/browse/JBEHAVE-376 Project: JBehave Issue Type: New Feature Components: IDE Support Reporter: Bogdan Florea Fix For: ide-3.0 Attachments: org.eclipse.behavior.editor.zip If I will be included in JBehave Contributors team I'll be happy to transfer copyright to the JBehave project. You can find the initial plugin sources in the attached zip. I will answer to any question about plugin development specificatons. -- 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-381) Support HtmlUnit WebDriver in PropertyBasedWebDriverProvider
Support HtmlUnit WebDriver in PropertyBasedWebDriverProvider Key: JBEHAVE-381 URL: http://jira.codehaus.org/browse/JBEHAVE-381 Project: JBehave Issue Type: Improvement Components: Web Selenium Reporter: Mauro Talevi Priority: Minor Fix For: web-3.1.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] Reopened: (JBEHAVE-382) Move Screenshotter from example to web-selenium
[ http://jira.codehaus.org/browse/JBEHAVE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-382: -- Move Screenshotter from example to web-selenium --- Key: JBEHAVE-382 URL: http://jira.codehaus.org/browse/JBEHAVE-382 Project: JBehave Issue Type: Improvement Components: Web Selenium Reporter: Paul Hammant Assignee: Paul Hammant Move Screenshotter from example to web-selenium -- 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-382) Add SaveScreenshotUponFailingScenarioWebDriverSteps
[ http://jira.codehaus.org/browse/JBEHAVE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-382: - Description: A instance of WebDriverSteps that save screenshot upon scenario failure. was:Move Screenshotter from example to web-selenium Affects Version/s: web-3.1 Fix Version/s: web-3.1.1 Summary: Add SaveScreenshotUponFailingScenarioWebDriverSteps (was: Move Screenshotter from example to web-selenium) Add SaveScreenshotUponFailingScenarioWebDriverSteps --- Key: JBEHAVE-382 URL: http://jira.codehaus.org/browse/JBEHAVE-382 Project: JBehave Issue Type: Improvement Components: Web Selenium Affects Versions: web-3.1 Reporter: Paul Hammant Assignee: Paul Hammant Fix For: web-3.1.1 A instance of WebDriverSteps that save screenshot upon scenario failure. -- 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-382) Add Selenium/WebDriverSteps to capture/save screenshot upon failing scenario
[ http://jira.codehaus.org/browse/JBEHAVE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-382: - Priority: Minor (was: Major) Add Selenium/WebDriverSteps to capture/save screenshot upon failing scenario Key: JBEHAVE-382 URL: http://jira.codehaus.org/browse/JBEHAVE-382 Project: JBehave Issue Type: Improvement Components: Web Selenium Affects Versions: web-3.1 Reporter: Paul Hammant Assignee: Paul Hammant Priority: Minor Fix For: web-3.1.1 Add instances of Selenium/WebDriverSteps to capture/save screenshot upon scenario failure. The different names reflects the difference in the Selenium and WebDriver APIs. -- 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-382) Add Selenium/WebDriverSteps to capture/save screenshot upon failing scenario
[ http://jira.codehaus.org/browse/JBEHAVE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-382. -- Resolution: Fixed Add Selenium/WebDriverSteps to capture/save screenshot upon failing scenario Key: JBEHAVE-382 URL: http://jira.codehaus.org/browse/JBEHAVE-382 Project: JBehave Issue Type: Improvement Components: Web Selenium Affects Versions: web-3.1 Reporter: Paul Hammant Assignee: Paul Hammant Priority: Minor Fix For: web-3.1.1 Add instances of Selenium/WebDriverSteps to capture/save screenshot upon scenario failure. The different names reflects the difference in the Selenium and WebDriver APIs. -- 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-385) PropertyWebDriverProvider should allow users to configure each WebDriver instance via a factory method
PropertyWebDriverProvider should allow users to configure each WebDriver instance via a factory method -- Key: JBEHAVE-385 URL: http://jira.codehaus.org/browse/JBEHAVE-385 Project: JBehave Issue Type: Improvement Components: Web Selenium Affects Versions: web-3.1 Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: web-3.1.1 Allow each WebDriver instance to be user-configured by extending a separate method, e.g. createFirefoxDriver(). -- 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-386) Allow different StoryNameResolvers to be used in report generation
[ http://jira.codehaus.org/browse/JBEHAVE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-386. -- Resolution: Fixed Applied patch: https://github.com/dgodfrey/jbehave-core/commit/79029c5d845e3dc77c6e368cc6fd417ca5b608d1 Allow different StoryNameResolvers to be used in report generation -- Key: JBEHAVE-386 URL: http://jira.codehaus.org/browse/JBEHAVE-386 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.1 Reporter: Daniel Godfrey Priority: Minor Fix For: 3.1.2 The current StoryNameResolver trims everything before the last full stop, this isn't always required, as sometimes you have full stops in the file name. Allow a custom StoryNameResolver to be used instead of the built-in UnderscoredToCapitalized to fix this. -- 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-387) Allow ExamplesTable to be loaded from external resources
[ http://jira.codehaus.org/browse/JBEHAVE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243007#action_243007 ] Mauro Talevi commented on JBEHAVE-387: -- Behaviour verified in trader example (examples_table_loaded_from_classpath.story) Allow ExamplesTable to be loaded from external resources Key: JBEHAVE-387 URL: http://jira.codehaus.org/browse/JBEHAVE-387 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.1.2 At times it may be convenient to load the content of an examples table from an external resource, be it from classpath or URL. The default resource loader will be the URL-based one as it does not require any additional configuration, unlike the classpath-based one that requires the class from which to derive the classloader. The ExamplesTableConverter should be able to handle both cases (textual table input or resource path input) via the use of an ExamplesTableFactory. The RegexStoryParser should also allow the use of the ExamplesTableFactory. -- 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-388) Support composition of steps
[
http://jira.codehaus.org/browse/JBEHAVE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-388:
-
Component/s: Core
Description:
In order to be more effective in communication and in scenario development
As a scenario writer
I want to compose steps using existing steps
Example:
{noformat}
Given customer has previously bought a product
{noformat}
Could be a composition of
{noformat}
Given customer is logged in
When they put a product in their cart
And go to checkout
And pay using their registered card
And go to the home page
{noformat}
Need to think about what options are available for the definition of the
composition.
Options include: annotations, step concatenation, etc ...
was:
{noformat}
1. @Given($who has previously bought a $what)
2. public String composedFullPurchase(String who, String what) {
3.return given $who is logged in + NL +
4. when they put a + what + in their cart NL +
5. and go to checkout + to NL +
6. and pay using their registered c-card + NL +
7. and go to the home page;
8. }
[Note: Mauro prefers an annotation based design]
{noformat}
Fix Version/s: 3.2
Summary: Support composition of steps (was: Step composition steps)
Support composition of steps
Key: JBEHAVE-388
URL: http://jira.codehaus.org/browse/JBEHAVE-388
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Paul Hammant
Fix For: 3.2
In order to be more effective in communication and in scenario development
As a scenario writer
I want to compose steps using existing steps
Example:
{noformat}
Given customer has previously bought a product
{noformat}
Could be a composition of
{noformat}
Given customer is logged in
When they put a product in their cart
And go to checkout
And pay using their registered card
And go to the home page
{noformat}
Need to think about what options are available for the definition of the
composition.
Options include: annotations, step concatenation, etc ...
--
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] Assigned: (JBEHAVE-388) Support composition of steps
[
http://jira.codehaus.org/browse/JBEHAVE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi reassigned JBEHAVE-388:
Assignee: Mauro Talevi
Support composition of steps
Key: JBEHAVE-388
URL: http://jira.codehaus.org/browse/JBEHAVE-388
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Paul Hammant
Assignee: Mauro Talevi
Fix For: 3.2
In order to be more effective in communication and in scenario development
As a scenario writer
I want to compose steps using existing steps
Example:
{noformat}
Given customer has previously bought a product
{noformat}
Could be a composition of
{noformat}
Given customer is logged in
When they put a product in their cart
And go to checkout
And pay using their registered card
And go to the home page
{noformat}
Need to think about what options are available for the definition of the
composition.
Options include: annotations, step concatenation, etc ...
--
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] Work started: (JBEHAVE-388) Support composition of steps
[
http://jira.codehaus.org/browse/JBEHAVE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JBEHAVE-388 started by Mauro Talevi.
Support composition of steps
Key: JBEHAVE-388
URL: http://jira.codehaus.org/browse/JBEHAVE-388
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Paul Hammant
Assignee: Mauro Talevi
Fix For: 3.2
In order to be more effective in communication and in scenario development
As a scenario writer
I want to compose steps using existing steps
Example:
{noformat}
Given customer has previously bought a product
{noformat}
Could be a composition of
{noformat}
Given customer is logged in
When they put a product in their cart
And go to checkout
And pay using their registered card
And go to the home page
{noformat}
Need to think about what options are available for the definition of the
composition.
Options include: annotations, step concatenation, etc ...
--
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-389) Spaces in Path breaks LoadFromRelativeFile
[
http://jira.codehaus.org/browse/JBEHAVE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-389:
-
Fix Version/s: 3.2
Spaces in Path breaks LoadFromRelativeFile
--
Key: JBEHAVE-389
URL: http://jira.codehaus.org/browse/JBEHAVE-389
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.0.3
Environment: Redhat Linux 5.5
Reporter: Leif Carlsen
Priority: Minor
Fix For: 3.2
LoadFromRelativeFile function loadStoryAsTextfails to unescape URLs passed
into the constructor that have escaped characters like %20 for a space. As a
result, the story files cannot be found.
Test case snippet follows... add it to StoryLoaderBehaviour.java. Also need
to add folder foldername has spaces to
jbehave-core/src/test/java/org/jbehave/core/io/stories/ and copy
MyPendingStory.txt into it. Also including revised code snippet for
loadStoryAsText function. I didn't immediately see a way to do it without
either checked exceptions or deprecated functions (ex
UrlDecoder.decode(string)). Not sure if InvalidStoryResource was the right
exception to convert to.
{code:title=StoryLoaderBehaviour.java}
@Test
public void shouldLoadStoryFromRelativeFilePathsWithSpace() throws
MalformedURLException, URISyntaxException {
// Given
String storyPath = MyPendingStory.txt;
String storyAsText = Given my step;
java.net.URL url =
CodeLocations.codeLocationFromClass(MyPendingStory.class);
java.io.File folderWithSpacesInName = new
java.io.File(url.toURI().getPath() + /org/jbehave/core/io/stories/foldername
has spaces);
java.net.URL urlThatHasEscapedSpaces =
folderWithSpacesInName.toURI().toURL();
assertThat(folderWithSpacesInName.exists(), is(true));
// When
StoryLoader loader = new
LoadFromRelativeFile(urlThatHasEscapedSpaces);
// Then
assertThat(loader.loadStoryAsText(storyPath), equalTo(storyAsText));
}
{code}
{code:title=LoadFromRelativeFile.java}
public String loadStoryAsText(String storyPath) {
ListString traversalPaths = new ArrayListString();
String locationPath;
try {
locationPath = new
File(URLDecoder.decode(location.getFile(),UTF-8)).getAbsolutePath();
} catch (UnsupportedEncodingException e) {
throw new InvalidStoryResource(storyPath, e);
}
for (StoryFilePath traversal : traversals) {
String filePath = locationPath.replace(traversal.toRemove,
traversal.relativePath) + / + storyPath;
File file = new File(filePath);
if (file.exists()) {
return loadContent(filePath);
} else {
traversalPaths.add(filePath);
}
}
throw new StoryResourceNotFound(storyPath, traversalPaths);
}
{code}
--
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-391) There is no @And annotation
[ http://jira.codehaus.org/browse/JBEHAVE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-391. -- Resolution: Not A Bug The absence of the @And annotation is not an oversight nor a bug. You have the ability to use And steps in the textual scenarios, but the step types are only Given/When/Then. The And simply replicates the type of the previous step. There is no @And annotation Key: JBEHAVE-391 URL: http://jira.codehaus.org/browse/JBEHAVE-391 Project: JBehave Issue Type: Bug Components: Core Environment: Window XP, JDK 1.6 Reporter: Etherel Johnson The grammer definition details the availability of a @And notation. However, no annotation exists. This may seem trivial, but in real terms it is fundamental blocker to writing clear scenarios. -- 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-392) There is no Background notation
[ http://jira.codehaus.org/browse/JBEHAVE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-392: - Affects Version/s: (was: web-3.1.1) Fix Version/s: (was: 3.2) There is no Background notation --- Key: JBEHAVE-392 URL: http://jira.codehaus.org/browse/JBEHAVE-392 Project: JBehave Issue Type: Wish Components: Core Environment: Window XP, JDK 1.6 Reporter: Etherel Johnson It would be extremely useful to have the concept of a Background within stories as described by on Aslak Hellesøy https://github.com/aslakhellesoy/cucumber/wiki/background -- 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-392) There is no Background notation
[ http://jira.codehaus.org/browse/JBEHAVE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-392. -- Resolution: Won't Fix JBehave has @Before/After Scenario/Story/Stories notations. There is no Background notation --- Key: JBEHAVE-392 URL: http://jira.codehaus.org/browse/JBEHAVE-392 Project: JBehave Issue Type: Wish Components: Core Environment: Window XP, JDK 1.6 Reporter: Etherel Johnson It would be extremely useful to have the concept of a Background within stories as described by on Aslak Hellesøy https://github.com/aslakhellesoy/cucumber/wiki/background -- 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-392) There is no Background notation
[ http://jira.codehaus.org/browse/JBEHAVE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243816#action_243816 ] Mauro Talevi commented on JBEHAVE-392: -- And GivenStories keyword. There is no Background notation --- Key: JBEHAVE-392 URL: http://jira.codehaus.org/browse/JBEHAVE-392 Project: JBehave Issue Type: Wish Components: Core Environment: Window XP, JDK 1.6 Reporter: Etherel Johnson It would be extremely useful to have the concept of a Background within stories as described by on Aslak Hellesøy https://github.com/aslakhellesoy/cucumber/wiki/background -- 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] Issue Comment Edited: (JBEHAVE-392) There is no Background notation
[ http://jira.codehaus.org/browse/JBEHAVE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243813#action_243813 ] Mauro Talevi edited comment on JBEHAVE-392 at 11/19/10 2:38 PM: JBehave has @Before/After Scenario/Story/Stories annotations. was (Author: maurotalevi): JBehave has @Before/After Scenario/Story/Stories notations. There is no Background notation --- Key: JBEHAVE-392 URL: http://jira.codehaus.org/browse/JBEHAVE-392 Project: JBehave Issue Type: Wish Components: Core Environment: Window XP, JDK 1.6 Reporter: Etherel Johnson It would be extremely useful to have the concept of a Background within stories as described by on Aslak Hellesøy https://github.com/aslakhellesoy/cucumber/wiki/background -- 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-392) There is no Background notation
[ http://jira.codehaus.org/browse/JBEHAVE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-392: - Comment: was deleted (was: And GivenStories keyword.) There is no Background notation --- Key: JBEHAVE-392 URL: http://jira.codehaus.org/browse/JBEHAVE-392 Project: JBehave Issue Type: Wish Components: Core Environment: Window XP, JDK 1.6 Reporter: Etherel Johnson It would be extremely useful to have the concept of a Background within stories as described by on Aslak Hellesøy https://github.com/aslakhellesoy/cucumber/wiki/background -- 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] Issue Comment Edited: (JBEHAVE-392) There is no Background notation
[ http://jira.codehaus.org/browse/JBEHAVE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=243813#action_243813 ] Mauro Talevi edited comment on JBEHAVE-392 at 11/19/10 2:39 PM: JBehave provides the GivenStories keyword and the @Before/After Scenario/Story/Stories annotations. was (Author: maurotalevi): JBehave has @Before/After Scenario/Story/Stories annotations. There is no Background notation --- Key: JBEHAVE-392 URL: http://jira.codehaus.org/browse/JBEHAVE-392 Project: JBehave Issue Type: Wish Components: Core Environment: Window XP, JDK 1.6 Reporter: Etherel Johnson It would be extremely useful to have the concept of a Background within stories as described by on Aslak Hellesøy https://github.com/aslakhellesoy/cucumber/wiki/background -- 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] Work started: (JBEHAVE-234) Improve JUnit integration
[ http://jira.codehaus.org/browse/JBEHAVE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-234 started by Mauro Talevi. Improve JUnit integration - Key: JBEHAVE-234 URL: http://jira.codehaus.org/browse/JBEHAVE-234 Project: JBehave Issue Type: Improvement Components: Core Reporter: Jonathan Ross Assignee: Mauro Talevi Fix For: 3.2 As a developer using jBehave running in JUnit in Eclipse, I would like to easily determine 1. how many individual scenarios have passed or failed, and 2. which steps failures occur in What springs to mind, is to wire each scenario up as separate JUnit TestCase (rather than the single 'testScenario()' method). Doing so, I would easily be able to drill down to the individually failing scenarios more easily. Regarding finding out which step failed, short of writing a fully-fledged plug-in, this would be a simple matter of retaining the actual failure exception and setting this in JUnit's test result - the failed step should be in the stack trace reported by JUnit. -- 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] Assigned: (JBEHAVE-234) Improve JUnit integration
[ http://jira.codehaus.org/browse/JBEHAVE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-234: Assignee: Mauro Talevi Improve JUnit integration - Key: JBEHAVE-234 URL: http://jira.codehaus.org/browse/JBEHAVE-234 Project: JBehave Issue Type: Improvement Components: Core Reporter: Jonathan Ross Assignee: Mauro Talevi Fix For: 3.2 As a developer using jBehave running in JUnit in Eclipse, I would like to easily determine 1. how many individual scenarios have passed or failed, and 2. which steps failures occur in What springs to mind, is to wire each scenario up as separate JUnit TestCase (rather than the single 'testScenario()' method). Doing so, I would easily be able to drill down to the individually failing scenarios more easily. Regarding finding out which step failed, short of writing a fully-fledged plug-in, this would be a simple matter of retaining the actual failure exception and setting this in JUnit's test result - the failed step should be in the stack trace reported by JUnit. -- 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-396) Throw exception if ParameterConverters cannot convert to the desired type.
[ http://jira.codehaus.org/browse/JBEHAVE-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=244465#action_244465 ] Mauro Talevi commented on JBEHAVE-396: -- Can you please add the url of the git commit? Throw exception if ParameterConverters cannot convert to the desired type. -- Key: JBEHAVE-396 URL: http://jira.codehaus.org/browse/JBEHAVE-396 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Currently if ParameterConverters can't convert to the desired type, it just returns the parameter as a string. This then falls over in some unrelated code later in the process when it can't call the step because of mismatching parameter types. To aid in debugging this, it should throw an Exception detailing the type that it can't convert to, so it can be caught early. -- 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-395) Story reporter in the XML format does not include the story narrative in the story title XML attribute
[ http://jira.codehaus.org/browse/JBEHAVE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=244466#action_244466 ] Mauro Talevi commented on JBEHAVE-395: -- Story title and narrative are independent elements.The title is free-text and contains whatever comes before the first keyword element, e.g. Narrative:. The narrative by contrast has its well-defined structure. It you want to have the title contain narrative-like structure, simply omit the Narrative: keyword and ensure it comes before any other story keyword. Story reporter in the XML format does not include the story narrative in the story title XML attribute -- Key: JBEHAVE-395 URL: http://jira.codehaus.org/browse/JBEHAVE-395 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.1.1 Reporter: Alan Parkinson Priority: Minor Attachments: xml-report.zip XML report builder produces a report with a empty title attribute of the story elment if the executed story contains a narrative e.g. story title= If the executed story does not contain a narrative then a empty title attribute is still produced. I would expect a story narrative to be contained in the title attribute if the story provides one or no title attribute should be provided if the story contains no narrative Attached testcase has only been tested on the 3.1.x versions -- 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-395) Story reporter in the XML format does not include the story narrative in the story title XML attribute
[ http://jira.codehaus.org/browse/JBEHAVE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-395: - Affects Version/s: (was: web-3.1.1) (was: web-3.1) 3.1.1 Story reporter in the XML format does not include the story narrative in the story title XML attribute -- Key: JBEHAVE-395 URL: http://jira.codehaus.org/browse/JBEHAVE-395 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.1.1 Reporter: Alan Parkinson Priority: Minor Attachments: xml-report.zip XML report builder produces a report with a empty title attribute of the story elment if the executed story contains a narrative e.g. story title= If the executed story does not contain a narrative then a empty title attribute is still produced. I would expect a story narrative to be contained in the title attribute if the story provides one or no title attribute should be provided if the story contains no narrative Attached testcase has only been tested on the 3.1.x versions -- 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-396) Throw exception if ParameterConverters cannot convert to the desired type.
[ http://jira.codehaus.org/browse/JBEHAVE-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-396: - Fix Version/s: 3.2 Throw exception if ParameterConverters cannot convert to the desired type. -- Key: JBEHAVE-396 URL: http://jira.codehaus.org/browse/JBEHAVE-396 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Fix For: 3.2 Currently if ParameterConverters can't convert to the desired type, it just returns the parameter as a string. This then falls over in some unrelated code later in the process when it can't call the step because of mismatching parameter types. To aid in debugging this, it should throw an Exception detailing the type that it can't convert to, so it can be caught early. -- 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-398) Provide generic parameter conversion to ListT
[ http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=245810#action_245810 ] Mauro Talevi commented on JBEHAVE-398: -- The reason for having different parameter converters for different raw types is to distinguish the parameter ListString from ListNumber (as you can see in the accept(Type) method. We can add a parameter converter for lists that delegates to the element parameter converter (which would be specified when instantiating the converter), so it can reused for different types of element converters, but I don't see the benefit of some of the elements in the patch. In particular, changing the ParameterConverters from class to interface and changing the converter method signature would break backward compat. Provide generic parameter conversion to ListT --- Key: JBEHAVE-398 URL: http://jira.codehaus.org/browse/JBEHAVE-398 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Currently to convert into a ListSomeType it's necessary to register a custom ParameterConverter. By default it already provides the ability to convert into ListString and Listsubtype of Number, but this should be extended to support all instances of ListT as it will reduce the duplicate code necessary. -- 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-398) Provide generic parameter conversion to ListT
[ http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=245856#action_245856 ] Mauro Talevi commented on JBEHAVE-398: -- The rename would break backward compat, and if primarily motivated by testing reasons, it is not a good idea. Let's focus on the functionality requirement and try to satisfy it with current design. I see no problem in adding other parameter converters but would not want to break backward compat. So what is your primary use case: using Lists of parameters converted via methods annotated with @AsParameterConverter? Provide generic parameter conversion to ListT --- Key: JBEHAVE-398 URL: http://jira.codehaus.org/browse/JBEHAVE-398 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Currently to convert into a ListSomeType it's necessary to register a custom ParameterConverter. By default it already provides the ability to convert into ListString and Listsubtype of Number, but this should be extended to support all instances of ListT as it will reduce the duplicate code necessary. -- 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-397) Failure to execute all scenarios within a story.
[ http://jira.codehaus.org/browse/JBEHAVE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-397: - Component/s: Core Fix Version/s: 3.2 Failure to execute all scenarios within a story. Key: JBEHAVE-397 URL: http://jira.codehaus.org/browse/JBEHAVE-397 Project: JBehave Issue Type: Bug Components: Core Reporter: Daniel Godfrey Fix For: 3.2 Given a story with 2 scenarios, the 2nd of which has GivenStores, if the first scenario fails, the second scenario will not execute fully, execution will finish when it's first GivenStory finishes. -- 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-401) XML Scenario reporter doesn't always include a closing story xml tag
[ http://jira.codehaus.org/browse/JBEHAVE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-401: - Fix Version/s: 3.2 XML Scenario reporter doesn't always include a closing story xml tag Key: JBEHAVE-401 URL: http://jira.codehaus.org/browse/JBEHAVE-401 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.1.2 Environment: Windows 7 and Linux x86 Reporter: Alan Parkinson Fix For: 3.2 Attachments: org.jbehave.examples.trader.stories.failure_followed_by_given_stories.xml When running the trader example, the story org/jbehave/examples/trader/stories/failure_followed_by_given_stories.story generates an invalid XML file by not including a final closing story tag. Attached is the generated invalid XML file. -- 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-397) Failure to execute all scenarios within a story.
[ http://jira.codehaus.org/browse/JBEHAVE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-397. -- Resolution: Fixed Patch applied. Failure to execute all scenarios within a story. Key: JBEHAVE-397 URL: http://jira.codehaus.org/browse/JBEHAVE-397 Project: JBehave Issue Type: Bug Components: Core Reporter: Daniel Godfrey Fix For: 3.2 Given a story with 2 scenarios, the 2nd of which has GivenStores, if the first scenario fails, the second scenario will not execute fully, execution will finish when it's first GivenStory finishes. -- 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-401) XML Scenario reporter doesn't always include a closing story xml tag
[ http://jira.codehaus.org/browse/JBEHAVE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-401. -- Resolution: Duplicate Duplicate of JBEHAVE-397. XML Scenario reporter doesn't always include a closing story xml tag Key: JBEHAVE-401 URL: http://jira.codehaus.org/browse/JBEHAVE-401 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.1.2 Environment: Windows 7 and Linux x86 Reporter: Alan Parkinson Fix For: 3.2 Attachments: org.jbehave.examples.trader.stories.failure_followed_by_given_stories.xml When running the trader example, the story org/jbehave/examples/trader/stories/failure_followed_by_given_stories.story generates an invalid XML file by not including a final closing story tag. Attached is the generated invalid XML file. -- 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-396) Throw exception if ParameterConverters cannot convert to the desired type.
[ http://jira.codehaus.org/browse/JBEHAVE-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-396. -- Resolution: Fixed Pulled patch. Throw exception if ParameterConverters cannot convert to the desired type. -- Key: JBEHAVE-396 URL: http://jira.codehaus.org/browse/JBEHAVE-396 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Fix For: 3.2 Currently if ParameterConverters can't convert to the desired type, it just returns the parameter as a string. This then falls over in some unrelated code later in the process when it can't call the step because of mismatching parameter types. To aid in debugging this, it should throw an Exception detailing the type that it can't convert to, so it can be caught early. -- 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-316) Define commom JAXB interfaces for systems to provide Features and its Stories and Scenarios to a JBehave runner.
[ http://jira.codehaus.org/browse/JBEHAVE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-316: - Fix Version/s: (was: 3.2) 3.x Define commom JAXB interfaces for systems to provide Features and its Stories and Scenarios to a JBehave runner. Key: JBEHAVE-316 URL: http://jira.codehaus.org/browse/JBEHAVE-316 Project: JBehave Issue Type: New Feature Components: Core Affects Versions: 3.0 Reporter: Cristiano Gavião Fix For: 3.x There are many systems where Stories could be writed, stored and mantained. Some example are Confluence (using its excelent versioning handle), Rational RSA, SparxSystems Enterprise Architect (both as scenarios inside UseCases/Features UML elements). One way todo that integration would be Jbehave to provide commom classes annotated with _javax.xml.bind.annotation.Xml*_ where developers could create JAXB *Services* that will get data from whatevers system and serve Features, its Stories and related Scenarios objects for JBehave as XML ou JSON. -- 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-328) Creation of a new parser to support the tracking of line numbers in error reporting.
[ http://jira.codehaus.org/browse/JBEHAVE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-328: - Fix Version/s: (was: 3.2) 3.x Creation of a new parser to support the tracking of line numbers in error reporting. Key: JBEHAVE-328 URL: http://jira.codehaus.org/browse/JBEHAVE-328 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1 Reporter: Mike Neeve Fix For: 3.x Attachments: jbehave-core.patch Attached is a patch for JBehave. The main change is the addition of a new parser. Its based on Eclipse JFace, which means we can track line numbers in error reporting. It can also be re-used for syntax highlighting in an Eclipse editor. JFace requires some Eclipse libraries, so these are new dependencies which still work even though we're not running in an OSGi container. The parser is also very fast compared to the current regex-based parser - the longest running test was 25s for the previous parser, and now its just 0.5s. In ScenarioParserBehaviour we've written some tests for the default configuration of JUnitScenario. They fail with the current parser but pass with the new one which is able to throw a new ParseException for each type of problem. We've added one test to CandidateStepBehaviour.java that currently fails. Doug tried fixing it by changing the ExamplesTable to be backed by a LinkedHashMap which means that the arguments are automatically in the correct order. But this did not work for other examples and couldn't figure out how to make it work, so the test is currently broken. We'd need help to fix this. Further proposed changes would improve the detection of problems such as: - not having enough columns in the examples section to cover all the required variables - having more columns than required in the examples section - checking the order of statements e.g. ensure a When comes after a Given - allowing boolean's for parameters The first two are quite difficult as it involves a good knowledge of the CandidateStep class. -- 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-374) Upgrade to commons-lang 3.0 to correctly escape characters from the Unicode Supplemental Multilingual Plane
[ http://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.2) 3.x Upgrade to commons-lang 3.0 to correctly escape characters from the Unicode Supplemental Multilingual Plane --- Key: JBEHAVE-374 URL: http://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 Priority: Minor Fix For: 3.x 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. - 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-402) The sourceDirectory propertey of the jbehave-maven-plugin is read-only in maven 2.2.1
[ http://jira.codehaus.org/browse/JBEHAVE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=246584#action_246584 ] Mauro Talevi commented on JBEHAVE-402: -- Hi Alan, we can make the sourceDirectory not read-only, but why would you need that? The sourceDirectory propertey of the jbehave-maven-plugin is read-only in maven 2.2.1 - Key: JBEHAVE-402 URL: http://jira.codehaus.org/browse/JBEHAVE-402 Project: JBehave Issue Type: Bug Components: Maven Plugin Affects Versions: 3.1.2 Environment: Maven 2.2.1 Reporter: Alan Parkinson Priority: Minor Fix For: 3.x Modifying the sourceDirectory and testSourceDirectory properties works as expected under Maven 3 but a error occurs under Maven 2.2.1 ERROR: Cannot override read-only parameter: sourceDirectory in goal: jbehave:run-stories-as-paths Upgrading to Maven 3 is currently not a option as this was discovered by a CI build running in Hudson and it does not support Maven 3 as a project type. -- 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-403) NullStoryReporter to facilitate subclassing, and use in conjunction with DelegatingStoryReporter
[ http://jira.codehaus.org/browse/JBEHAVE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-403: - Component/s: Core Fix Version/s: 3.2 NullStoryReporter to facilitate subclassing, and use in conjunction with DelegatingStoryReporter Key: JBEHAVE-403 URL: http://jira.codehaus.org/browse/JBEHAVE-403 Project: JBehave Issue Type: New Feature Components: Core Affects Versions: web-3.1.1 Reporter: Paul Hammant Priority: Trivial Fix For: 3.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-399) Count scenarios in a story separately from those in the GivenStories.
[ http://jira.codehaus.org/browse/JBEHAVE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-399. -- Resolution: Fixed Pull patch from branch. Count scenarios in a story separately from those in the GivenStories. - Key: JBEHAVE-399 URL: http://jira.codehaus.org/browse/JBEHAVE-399 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Fix For: 3.2 PostStoryStatisticsCollector should be counting scenarios in a story considering whether it's a givenStory or not. It should be displaying the number of scenarios executed in the story, not including int the count those executed in the GivenStories. -- 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-399) Count scenarios in a story separately from those in the GivenStories.
[ http://jira.codehaus.org/browse/JBEHAVE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-399: - Component/s: Core Description: PostStoryStatisticsCollector should be counting scenarios in a story considering whether it's a givenStory or not. It should be displaying the number of scenarios executed in the story, not including int the count those executed in the GivenStories. was:This is because PostStoryStatisticsCollector is resetting and writing the data on calls to beforeStory/afterStory irrespective of whether givenStory is set or not. It's also displaying the total number of scenarios executed, including the count from the GivenStories, rather than just the number of scenarios in the story. Fix Version/s: 3.2 Issue Type: Improvement (was: Bug) Summary: Count scenarios in a story separately from those in the GivenStories. (was: Reports contain incorrect data with multiple scenarios in one story when using GivenStories.) Count scenarios in a story separately from those in the GivenStories. - Key: JBEHAVE-399 URL: http://jira.codehaus.org/browse/JBEHAVE-399 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Fix For: 3.2 PostStoryStatisticsCollector should be counting scenarios in a story considering whether it's a givenStory or not. It should be displaying the number of scenarios executed in the story, not including int the count those executed in the GivenStories. -- 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-403) NullStoryReporter to facilitate subclassing, and use in conjunction with DelegatingStoryReporter
[ http://jira.codehaus.org/browse/JBEHAVE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-403. -- Resolution: Fixed NullStoryReporter to facilitate subclassing, and use in conjunction with DelegatingStoryReporter Key: JBEHAVE-403 URL: http://jira.codehaus.org/browse/JBEHAVE-403 Project: JBehave Issue Type: New Feature Components: Core Reporter: Paul Hammant Assignee: Mauro Talevi Priority: Trivial Fix For: 3.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] Commented: (JBEHAVE-399) Count scenarios in a story separately from those in the GivenStories.
[ http://jira.codehaus.org/browse/JBEHAVE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=247330#action_247330 ] Mauro Talevi commented on JBEHAVE-399: -- Added event categories for the GivenStory scenarios, which are now reported separately in the views. Count scenarios in a story separately from those in the GivenStories. - Key: JBEHAVE-399 URL: http://jira.codehaus.org/browse/JBEHAVE-399 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Fix For: 3.2 PostStoryStatisticsCollector should be counting scenarios in a story considering whether it's a givenStory or not. It should be displaying the number of scenarios executed in the story, not including int the count those executed in the GivenStories. -- 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-402) The sourceDirectory property of the jbehave-maven-plugin is read-only in maven 2.2.1
[ http://jira.codehaus.org/browse/JBEHAVE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-402: - Fix Version/s: (was: 3.x) 3.2 Summary: The sourceDirectory property of the jbehave-maven-plugin is read-only in maven 2.2.1 (was: The sourceDirectory propertey of the jbehave-maven-plugin is read-only in maven 2.2.1) The sourceDirectory property of the jbehave-maven-plugin is read-only in maven 2.2.1 Key: JBEHAVE-402 URL: http://jira.codehaus.org/browse/JBEHAVE-402 Project: JBehave Issue Type: Bug Components: Maven Plugin Affects Versions: 3.1.2 Environment: Maven 2.2.1 Reporter: Alan Parkinson Priority: Minor Fix For: 3.2 Modifying the sourceDirectory and testSourceDirectory properties works as expected under Maven 3 but a error occurs under Maven 2.2.1 ERROR: Cannot override read-only parameter: sourceDirectory in goal: jbehave:run-stories-as-paths Upgrading to Maven 3 is currently not a option as this was discovered by a CI build running in Hudson and it does not support Maven 3 as a project type. -- 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-402) The sourceDirectory property of the jbehave-maven-plugin is read-only in maven 2.2.1
[ http://jira.codehaus.org/browse/JBEHAVE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-402. -- Resolution: Fixed Allowed sourceDirectory and testSourceDirectory to be not read-only. The sourceDirectory property of the jbehave-maven-plugin is read-only in maven 2.2.1 Key: JBEHAVE-402 URL: http://jira.codehaus.org/browse/JBEHAVE-402 Project: JBehave Issue Type: Bug Components: Maven Plugin Affects Versions: 3.1.2 Environment: Maven 2.2.1 Reporter: Alan Parkinson Priority: Minor Fix For: 3.2 Modifying the sourceDirectory and testSourceDirectory properties works as expected under Maven 3 but a error occurs under Maven 2.2.1 ERROR: Cannot override read-only parameter: sourceDirectory in goal: jbehave:run-stories-as-paths Upgrading to Maven 3 is currently not a option as this was discovered by a CI build running in Hudson and it does not support Maven 3 as a project type. -- 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-394) Hudson Plugin to import JBehave test reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-394: - Attachment: jbehave-hudson-plugin.zip jbehave-hudson-plugin incorporated in maven core build. Hudson Plugin to import JBehave test reports Key: JBEHAVE-394 URL: http://jira.codehaus.org/browse/JBEHAVE-394 Project: JBehave Issue Type: New Feature Environment: Hudsdon Reporter: Alan Parkinson Priority: Minor Attachments: jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, org.jbehave.examples.trader.stories.claims_with_null_calendar.xml, TEST--778446379.xml As a developer I want to see a Hudson build test result showing failed scenarios so that I can see what broke my build As a developer I want scenarios containing pending steps and no failed steps to appear in build test result not as a fail or pass so that I can see what is missing from a story As a Manager I want to see individual scenarios in the build graph so that I can monitor progress of stories As a Manager I want to see Hudson build trend graph containing failed, pending and successful scenarios so that I can monitor the stability of my build -- 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-399) Count scenarios in a story separately from those in the GivenStories.
[ http://jira.codehaus.org/browse/JBEHAVE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=247755#action_247755 ] Mauro Talevi commented on JBEHAVE-399: -- Dan, your branch seems outdated wrt master. It still shows the StoryReporter methods breaking backward compatibility which have been reverted in master branch. Could you please recreate branch from master and apply the changes again? Count scenarios in a story separately from those in the GivenStories. - Key: JBEHAVE-399 URL: http://jira.codehaus.org/browse/JBEHAVE-399 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Fix For: 3.2 PostStoryStatisticsCollector should be counting scenarios in a story considering whether it's a givenStory or not. It should be displaying the number of scenarios executed in the story, not including int the count those executed in the GivenStories. -- 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] Assigned: (JBEHAVE-394) Hudson Plugin to import JBehave test reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-394: Assignee: Mauro Talevi Hudson Plugin to import JBehave test reports Key: JBEHAVE-394 URL: http://jira.codehaus.org/browse/JBEHAVE-394 Project: JBehave Issue Type: New Feature Components: Hudson Support Environment: Hudsdon Reporter: Alan Parkinson Assignee: Mauro Talevi Fix For: 3.2 Attachments: jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, org.jbehave.examples.trader.stories.claims_with_null_calendar.xml, pom.xml, TEST--778446379.xml As a developer I want to see a Hudson build test result showing failed scenarios so that I can see what broke my build As a developer I want scenarios containing pending steps and no failed steps to appear in build test result not as a fail or pass so that I can see what is missing from a story As a Manager I want to see individual scenarios in the build graph so that I can monitor progress of stories As a Manager I want to see Hudson build trend graph containing failed, pending and successful scenarios so that I can monitor the stability of my build -- 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-394) Hudson Plugin to import JBehave test reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=248649#action_248649 ] Mauro Talevi commented on JBEHAVE-394: -- Thanks Alan, that fixed the problems. I've added to hudson plugin to core build. Hudson Plugin to import JBehave test reports Key: JBEHAVE-394 URL: http://jira.codehaus.org/browse/JBEHAVE-394 Project: JBehave Issue Type: New Feature Components: Hudson Support Environment: Hudsdon Reporter: Alan Parkinson Assignee: Mauro Talevi Fix For: 3.2 Attachments: jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, org.jbehave.examples.trader.stories.claims_with_null_calendar.xml, pom.xml, TEST--778446379.xml As a developer I want to see a Hudson build test result showing failed scenarios so that I can see what broke my build As a developer I want scenarios containing pending steps and no failed steps to appear in build test result not as a fail or pass so that I can see what is missing from a story As a Manager I want to see individual scenarios in the build graph so that I can monitor progress of stories As a Manager I want to see Hudson build trend graph containing failed, pending and successful scenarios so that I can monitor the stability of my build -- 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-398) Provide generic parameter conversion to ListT
[ http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=248660#action_248660 ] Mauro Talevi commented on JBEHAVE-398: -- Hi Dan, I've pull the latest change from branch. I'm really not too convinced about the rename of Row - Record. Also, can you please clarify the usecase for the chaining implementation and the defaults? Provide generic parameter conversion to ListT --- Key: JBEHAVE-398 URL: http://jira.codehaus.org/browse/JBEHAVE-398 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Currently to convert into a ListSomeType it's necessary to register a custom ParameterConverter. By default it already provides the ability to convert into ListString and Listsubtype of Number, but this should be extended to support all instances of ListT as it will reduce the duplicate code necessary. -- 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-398) Provide conversion of table value
[ http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-398: - Priority: Major (was: Minor) Summary: Provide conversion of table value (was: Provide generic parameter conversion to ListT) Provide conversion of table value - Key: JBEHAVE-398 URL: http://jira.codehaus.org/browse/JBEHAVE-398 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Assignee: Mauro Talevi Fix For: 3.2 Currently to convert into a ListSomeType it's necessary to register a custom ParameterConverter. By default it already provides the ability to convert into ListString and Listsubtype of Number, but this should be extended to support all instances of ListT as it will reduce the duplicate code necessary. -- 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-398) Provide conversion of table value
[ http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=248756#action_248756 ] Mauro Talevi commented on JBEHAVE-398: -- Yes, an example story in trader would be most welcome! I'm starting to get the use case, but a concrete example would be useful. Provide conversion of table value - Key: JBEHAVE-398 URL: http://jira.codehaus.org/browse/JBEHAVE-398 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Assignee: Mauro Talevi Fix For: 3.2 Currently to convert into a ListSomeType it's necessary to register a custom ParameterConverter. By default it already provides the ability to convert into ListString and Listsubtype of Number, but this should be extended to support all instances of ListT as it will reduce the duplicate code necessary. -- 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-398) Provide table row values as converted parameters
[ http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-398: - Description: Currently, ExamplesTable provides the row values as MapString,String. In most cases, users will need to convert these values. We should provide the row values converted as specified types using the same ParameterConverters defined for the step conversion. We should also allow for provision of defaults, both accessing single value and as a table structure. was:Currently to convert into a ListSomeType it's necessary to register a custom ParameterConverter. By default it already provides the ability to convert into ListString and Listsubtype of Number, but this should be extended to support all instances of ListT as it will reduce the duplicate code necessary. Issue Type: New Feature (was: Improvement) Summary: Provide table row values as converted parameters (was: Provide conversion of table value) Provide table row values as converted parameters Key: JBEHAVE-398 URL: http://jira.codehaus.org/browse/JBEHAVE-398 Project: JBehave Issue Type: New Feature Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Assignee: Mauro Talevi Fix For: 3.2 Currently, ExamplesTable provides the row values as MapString,String. In most cases, users will need to convert these values. We should provide the row values converted as specified types using the same ParameterConverters defined for the step conversion. We should also allow for provision of defaults, both accessing single value and as a table structure. -- 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] Work started: (JBEHAVE-398) Provide table row values as converted parameters
[ http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-398 started by Mauro Talevi. Provide table row values as converted parameters Key: JBEHAVE-398 URL: http://jira.codehaus.org/browse/JBEHAVE-398 Project: JBehave Issue Type: New Feature Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Assignee: Mauro Talevi Fix For: 3.2 Currently, ExamplesTable provides the row values as MapString,String. In most cases, users will need to convert these values. We should provide the row values converted as specified types using the same ParameterConverters defined for the step conversion. We should also allow for provision of defaults, both accessing single value and as a table structure. -- 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-398) Provide table row values as converted parameters
[
http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=248958#action_248958
]
Mauro Talevi commented on JBEHAVE-398:
--
Dan, I've renamed Record - Parameters (below) as it seems a logic name to
describe a collection of parameters. I've removed the need to subclass to a
specific converting implementation. The map implementation has been removed as
it is a corner case of the converting implementation. The refactoring
maintained the unit test behaviour as specified by you. Do note that I've also
move the Parameters classes to the steps package, as it's where most of the
parameter-related logic is.
{code}
public interface Parameters {
/**
* Determines if the parameter of a given name is found
*
* @param name the name of the parameter
* @return A boolean, codetrue/code if found
*/
boolean hasValue(String name);
/**
* Returns the value for parameter of a given name
*
* @param type the Class of type T to convert to
* @param name the name of the parameter
* @return The value of type T
*/
T T valueAs(String name, ClassT type);
/**
* Returns the value for parameter of a given name and provides a default
* value if the name is not found
*
* @param type Class of type T to convert to
* @param name the name of the parameter
* @param defaultValue the default value if the name doesn't exist.
* @return The value of type T
*/
T T valueAs(String name, ClassT type, T defaultValue);
/**
* Returns the map of all the values as Strings
*
* @return The Map of values
*/
MapString, String values();
}
{code}
Provide table row values as converted parameters
Key: JBEHAVE-398
URL: http://jira.codehaus.org/browse/JBEHAVE-398
Project: JBehave
Issue Type: New Feature
Components: Core
Affects Versions: 3.1.2
Reporter: Daniel Godfrey
Assignee: Mauro Talevi
Fix For: 3.2
Currently, ExamplesTable provides the row values as MapString,String.
In most cases, users will need to convert these values. We should provide
the row values converted as specified types using the same
ParameterConverters defined for the step conversion.
We should also allow for provision of defaults, both accessing single value
and as a table structure.
--
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-398) Provide table row values as converted parameters
[ http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=248969#action_248969 ] Mauro Talevi commented on JBEHAVE-398: -- Updated trader example to use table with parameters defaults. Provide table row values as converted parameters Key: JBEHAVE-398 URL: http://jira.codehaus.org/browse/JBEHAVE-398 Project: JBehave Issue Type: New Feature Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Assignee: Mauro Talevi Fix For: 3.2 Currently, ExamplesTable provides the row values as MapString,String. In most cases, users will need to convert these values. We should provide the row values converted as specified types using the same ParameterConverters defined for the step conversion. We should also allow for provision of defaults, both accessing single value and as a table structure. -- 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-394) Hudson Plugin to import JBehave test reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=249694#action_249694 ] Mauro Talevi commented on JBEHAVE-394: -- Yes, I agree. We should provide a settings.xml with the list of repositories required to build. Then folks can build out of the box, while those using repository managers will need to create proxies appropriately. Hudson Plugin to import JBehave test reports Key: JBEHAVE-394 URL: http://jira.codehaus.org/browse/JBEHAVE-394 Project: JBehave Issue Type: New Feature Components: Hudson Support Environment: Hudsdon Reporter: Alan Parkinson Assignee: Mauro Talevi Fix For: 3.2 Attachments: jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, org.jbehave.examples.trader.stories.claims_with_null_calendar.xml, pom.xml, TEST--778446379.xml As a developer I want to see a Hudson build test result showing failed scenarios so that I can see what broke my build As a developer I want scenarios containing pending steps and no failed steps to appear in build test result not as a fail or pass so that I can see what is missing from a story As a Manager I want to see individual scenarios in the build graph so that I can monitor progress of stories As a Manager I want to see Hudson build trend graph containing failed, pending and successful scenarios so that I can monitor the stability of my build -- 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-394) Hudson Plugin to import JBehave test reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=249872#action_249872 ] Mauro Talevi commented on JBEHAVE-394: -- If that happens we can quickly put out a bugfix release. There is always a balance to be struck when creating separate projects, and having one for such a small codebase is not recommended. Also, the hudson plugin is very tied to the core reporting functionality, so it does make sense to keep them in sync. Hudson Plugin to import JBehave test reports Key: JBEHAVE-394 URL: http://jira.codehaus.org/browse/JBEHAVE-394 Project: JBehave Issue Type: New Feature Components: Hudson Support Environment: Hudsdon Reporter: Alan Parkinson Assignee: Mauro Talevi Fix For: 3.2 Attachments: jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, org.jbehave.examples.trader.stories.claims_with_null_calendar.xml, pom.xml, TEST--778446379.xml As a developer I want to see a Hudson build test result showing failed scenarios so that I can see what broke my build As a developer I want scenarios containing pending steps and no failed steps to appear in build test result not as a fail or pass so that I can see what is missing from a story As a Manager I want to see individual scenarios in the build graph so that I can monitor progress of stories As a Manager I want to see Hudson build trend graph containing failed, pending and successful scenarios so that I can monitor the stability of my build -- 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-407) Failing Scenarios are Reported as Successfull
[ http://jira.codehaus.org/browse/JBEHAVE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24#action_24 ] Mauro Talevi commented on JBEHAVE-407: -- Hi Patrick, it would seem that the failure is reported as it should (hence the output) but the method annotated with outcome FAILURE is not executed. We'll investigate. Do also bear in mind that the trader stories are actually configured to ignore failures in stories (but not in view) so that the execution of all stories can complete and a collective view of all stories can be generated. Failing Scenarios are Reported as Successfull - Key: JBEHAVE-407 URL: http://jira.codehaus.org/browse/JBEHAVE-407 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.2 Environment: Win XP Reporter: Patrick McFadden We noticed that methods annotated with @AfterScenario(uponOutcome=FAILURE) were not being triggered properly after a scenario failed. Upon further inspection, we see that the Failure is reported by the failing step. It is then ignored by the After methods, which report success. The following scenario is run (although it should be skipped). The report at the bottom correctly states that the story failed. Sample Output from one of the Trader Examples: Running story org/jbehave/examples/trader/stories/skip_scenarios_after_failure.story (org/jbehave/examples/trader/stories/skip_scenarios_after_failure.story) Before Story ... Scenario: A scenario with failed step Before Scenario ... Given I do nothing Then I fail (FAILED) (junit.framework.AssertionFailedError: I failed!) After Any Scenario ... After Successful Scenario ... Scenario: A scenario that is not executed because if followed a failed scenario Before Scenario ... Given I do nothing After Any Scenario ... After Successful Scenario ... ... Browser has been put to rest After Story ... Failed to run story org/jbehave/examples/trader/stories/skip_scenarios_after_failure.story junit.framework.AssertionFailedError: I failed! -- 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-409) @Composite step is executing successfully when one of its sub-steps is Pending.
[ http://jira.codehaus.org/browse/JBEHAVE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-409: - Fix Version/s: 3.2 @Composite step is executing successfully when one of its sub-steps is Pending. - Key: JBEHAVE-409 URL: http://jira.codehaus.org/browse/JBEHAVE-409 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.2 Environment: WinXP Reporter: Chris Kozak Fix For: 3.2 Attachments: Patrick_McFadden__Chris_Kozak_-_Pending_steps_in_Composite_steps_now_halt_test_execution.patch We believe that these should behave in the same manner as other pending steps; the pending step should be marked in the output and subsequent steps should not be performed. -- 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-409) @Composite step is executing successfully when one of its sub-steps is Pending.
[ http://jira.codehaus.org/browse/JBEHAVE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-409. -- Resolution: Fixed Well spotted - patch applied with thanks. @Composite step is executing successfully when one of its sub-steps is Pending. - Key: JBEHAVE-409 URL: http://jira.codehaus.org/browse/JBEHAVE-409 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.2 Environment: WinXP Reporter: Chris Kozak Fix For: 3.2 Attachments: Patrick_McFadden__Chris_Kozak_-_Pending_steps_in_Composite_steps_now_halt_test_execution.patch We believe that these should behave in the same manner as other pending steps; the pending step should be marked in the output and subsequent steps should not be performed. -- 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-408) GivenStories should be able to be loaded relative to the story depending on them.
[ http://jira.codehaus.org/browse/JBEHAVE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-408: - Fix Version/s: 3.2 GivenStories should be able to be loaded relative to the story depending on them. - Key: JBEHAVE-408 URL: http://jira.codehaus.org/browse/JBEHAVE-408 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Fix For: 3.2 It should be possible to have given stories included relative to the story including them, as this makes it easier to re-organise the stories without changing the paths. -- 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-408) GivenStories should be able to be loaded relative to the story depending on them.
[ http://jira.codehaus.org/browse/JBEHAVE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=250051#action_250051 ] Mauro Talevi commented on JBEHAVE-408: -- Hi Dan, I've pulled patch. I'd be good if we also had an example of using given stories with relative path calculator. GivenStories should be able to be loaded relative to the story depending on them. - Key: JBEHAVE-408 URL: http://jira.codehaus.org/browse/JBEHAVE-408 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Priority: Minor Fix For: 3.2 It should be possible to have given stories included relative to the story including them, as this makes it easier to re-organise the stories without changing the paths. -- 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-407) Failing Scenarios are Reported as Successfull
[ http://jira.codehaus.org/browse/JBEHAVE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-407. -- Resolution: Fixed Fix Version/s: 3.2 Assignee: Mauro Talevi Fixed - added story to verify behaviour: org/jbehave/examples/trader/stories/after_scenario_outcome.story Failing Scenarios are Reported as Successfull - Key: JBEHAVE-407 URL: http://jira.codehaus.org/browse/JBEHAVE-407 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.2 Environment: Win XP Reporter: Patrick McFadden Assignee: Mauro Talevi Fix For: 3.2 We noticed that methods annotated with @AfterScenario(uponOutcome=FAILURE) were not being triggered properly after a scenario failed. Upon further inspection, we see that the Failure is reported by the failing step. It is then ignored by the After methods, which report success. The following scenario is run (although it should be skipped). The report at the bottom correctly states that the story failed. Sample Output from one of the Trader Examples: Running story org/jbehave/examples/trader/stories/skip_scenarios_after_failure.story (org/jbehave/examples/trader/stories/skip_scenarios_after_failure.story) Before Story ... Scenario: A scenario with failed step Before Scenario ... Given I do nothing Then I fail (FAILED) (junit.framework.AssertionFailedError: I failed!) After Any Scenario ... After Successful Scenario ... Scenario: A scenario that is not executed because if followed a failed scenario Before Scenario ... Given I do nothing After Any Scenario ... After Successful Scenario ... ... Browser has been put to rest After Story ... Failed to run story org/jbehave/examples/trader/stories/skip_scenarios_after_failure.story junit.framework.AssertionFailedError: I failed! -- 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-410) WebDriverProvider should return a boolean to say if the screenshot has been taken
WebDriverProvider should return a boolean to say if the screenshot has been taken - Key: JBEHAVE-410 URL: http://jira.codehaus.org/browse/JBEHAVE-410 Project: JBehave Issue Type: Improvement Components: Web Selenium Reporter: Mauro Talevi Assignee: Paul Hammant Priority: Minor Fix For: 3.2 As not all WebDrivers support taking screenshots (ie instances of TakesScreenshot) it's useful to return a boolean value to inform when it does. -- 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-410) WebDriverProvider#takeScreenshot() should return a boolean to say if the screenshot has been taken
[ http://jira.codehaus.org/browse/JBEHAVE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-410: - Description: As not all WebDrivers support taking screenshots (ie instances of TakesScreenshot) it's useful for the takeScreenshot() method to return a boolean value to inform when the underlying WebDriver supports screenshots. was: As not all WebDrivers support taking screenshots (ie instances of TakesScreenshot) it's useful to return a boolean value to inform when it does. Summary: WebDriverProvider#takeScreenshot() should return a boolean to say if the screenshot has been taken (was: WebDriverProvider should return a boolean to say if the screenshot has been taken) WebDriverProvider#takeScreenshot() should return a boolean to say if the screenshot has been taken -- Key: JBEHAVE-410 URL: http://jira.codehaus.org/browse/JBEHAVE-410 Project: JBehave Issue Type: Improvement Components: Web Selenium Reporter: Mauro Talevi Assignee: Paul Hammant Priority: Minor Fix For: 3.2 As not all WebDrivers support taking screenshots (ie instances of TakesScreenshot) it's useful for the takeScreenshot() method to return a boolean value to inform when the underlying WebDriver supports screenshots. -- 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-414) ClassCastException: org.jbehave.tutorials.etsy.EtsyDotComStories cannot be cast to org.jbehave.core.embedder.Embedder (StepDocs issue)
[ http://jira.codehaus.org/browse/JBEHAVE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=251197#action_251197 ] Mauro Talevi commented on JBEHAVE-414: -- What are you trying to achieve? ClassCastException: org.jbehave.tutorials.etsy.EtsyDotComStories cannot be cast to org.jbehave.core.embedder.Embedder (StepDocs issue) -- Key: JBEHAVE-414 URL: http://jira.codehaus.org/browse/JBEHAVE-414 Project: JBehave Issue Type: Bug Reporter: Paul Hammant 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] Commented: (JBEHAVE-416) Hudson can't issue -Dmeta.filter directives because of the spaces and quotes in the values side of the name/value thing passed to -D
[ http://jira.codehaus.org/browse/JBEHAVE-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=251347#action_251347 ] Mauro Talevi commented on JBEHAVE-416: -- Can you use single quotes? E.g.: -Dmeta.filter='+suite foo' Hudson can't issue -Dmeta.filter directives because of the spaces and quotes in the values side of the name/value thing passed to -D Key: JBEHAVE-416 URL: http://jira.codehaus.org/browse/JBEHAVE-416 Project: JBehave Issue Type: Bug Components: Core Reporter: Paul Hammant Priority: Minor -Dmeta.filter=+suite foo is going to cause Hudson to try to redo the quotes like so -Dmeta.filter=+suite foo The fix will be add underscore as a space replacement for meta-filters. -Dmeta.filter=+suite_foo -- 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-407) Failing Scenarios are Reported as Successfull
[ http://jira.codehaus.org/browse/JBEHAVE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252132#action_252132 ] Mauro Talevi commented on JBEHAVE-407: -- Not yet released, we'll push out a new beta of 3.2 by the end of the week. Failing Scenarios are Reported as Successfull - Key: JBEHAVE-407 URL: http://jira.codehaus.org/browse/JBEHAVE-407 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.2 Environment: Win XP Reporter: Patrick McFadden Assignee: Mauro Talevi Fix For: 3.2 We noticed that methods annotated with @AfterScenario(uponOutcome=FAILURE) were not being triggered properly after a scenario failed. Upon further inspection, we see that the Failure is reported by the failing step. It is then ignored by the After methods, which report success. The following scenario is run (although it should be skipped). The report at the bottom correctly states that the story failed. Sample Output from one of the Trader Examples: Running story org/jbehave/examples/trader/stories/skip_scenarios_after_failure.story (org/jbehave/examples/trader/stories/skip_scenarios_after_failure.story) Before Story ... Scenario: A scenario with failed step Before Scenario ... Given I do nothing Then I fail (FAILED) (junit.framework.AssertionFailedError: I failed!) After Any Scenario ... After Successful Scenario ... Scenario: A scenario that is not executed because if followed a failed scenario Before Scenario ... Given I do nothing After Any Scenario ... After Successful Scenario ... ... Browser has been put to rest After Story ... Failed to run story org/jbehave/examples/trader/stories/skip_scenarios_after_failure.story junit.framework.AssertionFailedError: I failed! -- 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] Assigned: (JBEHAVE-408) GivenStories should be able to be loaded relative to the story depending on them.
[ http://jira.codehaus.org/browse/JBEHAVE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-408: Assignee: Mauro Talevi GivenStories should be able to be loaded relative to the story depending on them. - Key: JBEHAVE-408 URL: http://jira.codehaus.org/browse/JBEHAVE-408 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Assignee: Mauro Talevi Priority: Minor Fix For: 3.2 It should be possible to have given stories included relative to the story including them, as this makes it easier to re-organise the stories without changing the paths. -- 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] Work started: (JBEHAVE-408) GivenStories should be able to be loaded relative to the story depending on them.
[ http://jira.codehaus.org/browse/JBEHAVE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-408 started by Mauro Talevi. GivenStories should be able to be loaded relative to the story depending on them. - Key: JBEHAVE-408 URL: http://jira.codehaus.org/browse/JBEHAVE-408 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Assignee: Mauro Talevi Priority: Minor Fix For: 3.2 It should be possible to have given stories included relative to the story including them, as this makes it easier to re-organise the stories without changing the paths. -- 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] Reopened: (JBEHAVE-418) Stacktraces for failure 'yes' vs 'no' should be settable with the 'enum' like list of output formats.
[ http://jira.codehaus.org/browse/JBEHAVE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-418: -- Issues should not be closed, just resolved. Stacktraces for failure 'yes' vs 'no' should be settable with the 'enum' like list of output formats. - Key: JBEHAVE-418 URL: http://jira.codehaus.org/browse/JBEHAVE-418 Project: JBehave Issue Type: Wish Affects Versions: 3.2 Reporter: Paul Hammant Assignee: Paul Hammant Fix For: 3.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-418) Stacktraces for failure 'yes' vs 'no' should be settable with the 'enum' like list of output formats.
[ http://jira.codehaus.org/browse/JBEHAVE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-418: - Component/s: Core Issue Type: Improvement (was: Wish) Stacktraces for failure 'yes' vs 'no' should be settable with the 'enum' like list of output formats. - Key: JBEHAVE-418 URL: http://jira.codehaus.org/browse/JBEHAVE-418 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.2 Reporter: Paul Hammant Assignee: Paul Hammant Fix For: 3.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] Reopened: (JBEHAVE-419) Generic Parameter Converter for Enum classes.
[ http://jira.codehaus.org/browse/JBEHAVE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-419: -- Assignee: Mauro Talevi (was: Paul Hammant) Issues should not be closed, just resolved. Generic Parameter Converter for Enum classes. - Key: JBEHAVE-419 URL: http://jira.codehaus.org/browse/JBEHAVE-419 Project: JBehave Issue Type: New Feature Components: Core Reporter: Larry Shatzer Assignee: Mauro Talevi Fix For: 3.2 It would be nice if you could generically convert Enum fields automatically without having to create ad-hoc @AsParameterConverters for each. -- 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-419) Generic Parameter Converter for Enum classes.
[ http://jira.codehaus.org/browse/JBEHAVE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-419: - Priority: Minor (was: Major) Fix Version/s: 3.2 Issue Type: Improvement (was: New Feature) Generic Parameter Converter for Enum classes. - Key: JBEHAVE-419 URL: http://jira.codehaus.org/browse/JBEHAVE-419 Project: JBehave Issue Type: Improvement Components: Core Reporter: Larry Shatzer Assignee: Mauro Talevi Priority: Minor Fix For: 3.2 It would be nice if you could generically convert Enum fields automatically without having to create ad-hoc @AsParameterConverters for each. -- 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-419) Generic Parameter Converter for Enum classes.
[ http://jira.codehaus.org/browse/JBEHAVE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-419. -- Resolution: Fixed Thanks for very useful contribution. Generic Parameter Converter for Enum classes. - Key: JBEHAVE-419 URL: http://jira.codehaus.org/browse/JBEHAVE-419 Project: JBehave Issue Type: Improvement Components: Core Reporter: Larry Shatzer Assignee: Mauro Talevi Priority: Minor Fix For: 3.2 It would be nice if you could generically convert Enum fields automatically without having to create ad-hoc @AsParameterConverters for each. -- 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-418) Stacktraces for failure 'yes' vs 'no' should be settable with the 'enum' like list of output formats.
[ http://jira.codehaus.org/browse/JBEHAVE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-418. -- Resolution: Won't Fix Same behaviour already achievable via: new StoryReporterBuilder().withFailureTrace(true) Stacktraces for failure 'yes' vs 'no' should be settable with the 'enum' like list of output formats. - Key: JBEHAVE-418 URL: http://jira.codehaus.org/browse/JBEHAVE-418 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.2 Reporter: Paul Hammant Assignee: Paul Hammant Fix For: 3.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] Reopened: (JBEHAVE-389) Spaces in Path breaks LoadFromRelativeFile
[
http://jira.codehaus.org/browse/JBEHAVE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi reopened JBEHAVE-389:
--
Spaces in Path breaks LoadFromRelativeFile
--
Key: JBEHAVE-389
URL: http://jira.codehaus.org/browse/JBEHAVE-389
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.0.3
Environment: Redhat Linux 5.5
Reporter: Leif Carlsen
Assignee: Paul Hammant
Priority: Minor
Fix For: 3.2
LoadFromRelativeFile function loadStoryAsTextfails to unescape URLs passed
into the constructor that have escaped characters like %20 for a space. As a
result, the story files cannot be found.
Test case snippet follows... add it to StoryLoaderBehaviour.java. Also need
to add folder foldername has spaces to
jbehave-core/src/test/java/org/jbehave/core/io/stories/ and copy
MyPendingStory.txt into it. Also including revised code snippet for
loadStoryAsText function. I didn't immediately see a way to do it without
either checked exceptions or deprecated functions (ex
UrlDecoder.decode(string)). Not sure if InvalidStoryResource was the right
exception to convert to.
{code:title=StoryLoaderBehaviour.java}
@Test
public void shouldLoadStoryFromRelativeFilePathsWithSpace() throws
MalformedURLException, URISyntaxException {
// Given
String storyPath = MyPendingStory.txt;
String storyAsText = Given my step;
java.net.URL url =
CodeLocations.codeLocationFromClass(MyPendingStory.class);
java.io.File folderWithSpacesInName = new
java.io.File(url.toURI().getPath() + /org/jbehave/core/io/stories/foldername
has spaces);
java.net.URL urlThatHasEscapedSpaces =
folderWithSpacesInName.toURI().toURL();
assertThat(folderWithSpacesInName.exists(), is(true));
// When
StoryLoader loader = new
LoadFromRelativeFile(urlThatHasEscapedSpaces);
// Then
assertThat(loader.loadStoryAsText(storyPath), equalTo(storyAsText));
}
{code}
{code:title=LoadFromRelativeFile.java}
public String loadStoryAsText(String storyPath) {
ListString traversalPaths = new ArrayListString();
String locationPath;
try {
locationPath = new
File(URLDecoder.decode(location.getFile(),UTF-8)).getAbsolutePath();
} catch (UnsupportedEncodingException e) {
throw new InvalidStoryResource(storyPath, e);
}
for (StoryFilePath traversal : traversals) {
String filePath = locationPath.replace(traversal.toRemove,
traversal.relativePath) + / + storyPath;
File file = new File(filePath);
if (file.exists()) {
return loadContent(filePath);
} else {
traversalPaths.add(filePath);
}
}
throw new StoryResourceNotFound(storyPath, traversalPaths);
}
{code}
--
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] Reopened: (JBEHAVE-413) Failing steps could be assigned a unique failure-context that could to a) name screenshots, and b) be used in HTML reports
[ http://jira.codehaus.org/browse/JBEHAVE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-413: -- Failing steps could be assigned a unique failure-context that could to a) name screenshots, and b) be used in HTML reports -- Key: JBEHAVE-413 URL: http://jira.codehaus.org/browse/JBEHAVE-413 Project: JBehave Issue Type: Improvement Components: Core Reporter: Paul Hammant Assignee: Paul Hammant Priority: Minor Fix For: 3.2 This affects 'core' and 'web' Say an element is not found in a webpage, and WebDriver throws whatever exception it needs, presuming that fails a step, then JBehave could set a failure-context (lets say that a GUID). Later, when the FailingScreenShotThing picks up the fact that a step failed, it could use the failure-context in the name of the screen-shot jpeg. Later, in the rendering of the reports, the HTML one at least could link to the jpeg. Maybe instead of GUID, this could be the Object Identity of the StepResult or Failed instance. -- 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-413) Failing steps could be assigned a unique failure-context that could to a) name screenshots, and b) be used in HTML reports
[ http://jira.codehaus.org/browse/JBEHAVE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-413. -- Resolution: Fixed Failing steps could be assigned a unique failure-context that could to a) name screenshots, and b) be used in HTML reports -- Key: JBEHAVE-413 URL: http://jira.codehaus.org/browse/JBEHAVE-413 Project: JBehave Issue Type: Improvement Components: Core Reporter: Paul Hammant Assignee: Paul Hammant Priority: Minor Fix For: 3.2 This affects 'core' and 'web' Say an element is not found in a webpage, and WebDriver throws whatever exception it needs, presuming that fails a step, then JBehave could set a failure-context (lets say that a GUID). Later, when the FailingScreenShotThing picks up the fact that a step failed, it could use the failure-context in the name of the screen-shot jpeg. Later, in the rendering of the reports, the HTML one at least could link to the jpeg. Maybe instead of GUID, this could be the Object Identity of the StepResult or Failed instance. -- 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-389) Spaces in Path breaks LoadFromRelativeFile
[
http://jira.codehaus.org/browse/JBEHAVE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-389.
--
Resolution: Fixed
Spaces in Path breaks LoadFromRelativeFile
--
Key: JBEHAVE-389
URL: http://jira.codehaus.org/browse/JBEHAVE-389
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.0.3
Environment: Redhat Linux 5.5
Reporter: Leif Carlsen
Assignee: Paul Hammant
Priority: Minor
Fix For: 3.2
LoadFromRelativeFile function loadStoryAsTextfails to unescape URLs passed
into the constructor that have escaped characters like %20 for a space. As a
result, the story files cannot be found.
Test case snippet follows... add it to StoryLoaderBehaviour.java. Also need
to add folder foldername has spaces to
jbehave-core/src/test/java/org/jbehave/core/io/stories/ and copy
MyPendingStory.txt into it. Also including revised code snippet for
loadStoryAsText function. I didn't immediately see a way to do it without
either checked exceptions or deprecated functions (ex
UrlDecoder.decode(string)). Not sure if InvalidStoryResource was the right
exception to convert to.
{code:title=StoryLoaderBehaviour.java}
@Test
public void shouldLoadStoryFromRelativeFilePathsWithSpace() throws
MalformedURLException, URISyntaxException {
// Given
String storyPath = MyPendingStory.txt;
String storyAsText = Given my step;
java.net.URL url =
CodeLocations.codeLocationFromClass(MyPendingStory.class);
java.io.File folderWithSpacesInName = new
java.io.File(url.toURI().getPath() + /org/jbehave/core/io/stories/foldername
has spaces);
java.net.URL urlThatHasEscapedSpaces =
folderWithSpacesInName.toURI().toURL();
assertThat(folderWithSpacesInName.exists(), is(true));
// When
StoryLoader loader = new
LoadFromRelativeFile(urlThatHasEscapedSpaces);
// Then
assertThat(loader.loadStoryAsText(storyPath), equalTo(storyAsText));
}
{code}
{code:title=LoadFromRelativeFile.java}
public String loadStoryAsText(String storyPath) {
ListString traversalPaths = new ArrayListString();
String locationPath;
try {
locationPath = new
File(URLDecoder.decode(location.getFile(),UTF-8)).getAbsolutePath();
} catch (UnsupportedEncodingException e) {
throw new InvalidStoryResource(storyPath, e);
}
for (StoryFilePath traversal : traversals) {
String filePath = locationPath.replace(traversal.toRemove,
traversal.relativePath) + / + storyPath;
File file = new File(filePath);
if (file.exists()) {
return loadContent(filePath);
} else {
traversalPaths.add(filePath);
}
}
throw new StoryResourceNotFound(storyPath, traversalPaths);
}
{code}
--
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-408) GivenStories should be able to be loaded relative to the story depending on them.
[ http://jira.codehaus.org/browse/JBEHAVE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=253460#action_253460 ] Mauro Talevi commented on JBEHAVE-408: -- Added trader example given_relative_path_story.story to verify behaviour. GivenStories should be able to be loaded relative to the story depending on them. - Key: JBEHAVE-408 URL: http://jira.codehaus.org/browse/JBEHAVE-408 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1.2 Reporter: Daniel Godfrey Assignee: Mauro Talevi Priority: Minor Fix For: 3.2 It should be possible to have given stories included relative to the story including them, as this makes it easier to re-organise the stories without changing the paths. -- 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
