[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] 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-tabpanel&focusedCommentId=247344#action_247344 ] Mauro Talevi commented on JBEHAVE-394: -- Alan, I've been trying to incorporate the hudson plugin in the core build, but I've been running into issues. These stem from the fact that I'm trying to extend the jbehave parent rather than the hudson one. I'm attaching the version of the your contribution, with only the pom.xml changed. Could perhaps have a look and see if you spot the problem? It needs to be unzipped in the master of the jbehave core build. It's failing on the hpi plugin with error message "Unable to find a plugin class. Did you put @plugin in javadoc?". > 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, > 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] 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-tabpanel&focusedCommentId=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] 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-tabpanel&focusedCommentId=247778#action_247778 ] Mauro Talevi commented on JBEHAVE-399: -- You're right - my remote branch was out of date. Pulled changed. Thanks. > 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-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: - Component/s: Hudson Support Priority: Major (was: Minor) Fix Version/s: 3.2 > 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 > 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] Work started: (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 ] Work on JBEHAVE-394 started by 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] 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-tabpanel&focusedCommentId=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 List
[ http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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 List > --- > > 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 List it's necessary to register a > custom ParameterConverter. By default it already provides the ability to > convert into List and List, but this should be > extended to support all instances of List 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 List) > 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 List it's necessary to register a > custom ParameterConverter. By default it already provides the ability to > convert into List and List, but this should be > extended to support all instances of List 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] Assigned: (JBEHAVE-398) Provide generic parameter conversion to List
[ http://jira.codehaus.org/browse/JBEHAVE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-398: Assignee: Mauro Talevi > Provide generic parameter conversion to List > --- > > 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 >Priority: Minor > Fix For: 3.2 > > > Currently to convert into a List it's necessary to register a > custom ParameterConverter. By default it already provides the ability to > convert into List and List, but this should be > extended to support all instances of List 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: - Fix Version/s: 3.2 > 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 List it's necessary to register a > custom ParameterConverter. By default it already provides the ability to > convert into List and List, but this should be > extended to support all instances of List 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-tabpanel&focusedCommentId=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 List it's necessary to register a > custom ParameterConverter. By default it already provides the ability to > convert into List and List, but this should be > extended to support all instances of List 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 Map. 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 List it's necessary to register a custom ParameterConverter. By default it already provides the ability to convert into List and List, but this should be extended to support all instances of List 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 Map. > 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 Map. > 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-tabpanel&focusedCommentId=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, true if found
*/
boolean hasValue(String name);
/**
* Returns the value for parameter of a given name
*
* @param type the Class of type to convert to
* @param name the name of the parameter
* @return The value of type
*/
T valueAs(String name, Class 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 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 valueAs(String name, Class type, T defaultValue);
/**
* Returns the map of all the values as Strings
*
* @return The Map of values
*/
Map 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 Map.
> 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] Resolved: (JBEHAVE-406) jbehave-site-resources 3.1.2 needs uploading to Maven Central repo
[ http://jira.codehaus.org/browse/JBEHAVE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-406. -- Resolution: Won't Fix There is no such version of site resources, the latest being 3.1.1. Site, core and web releases have independent versioning, and you need to allow for different version variables in your scripts. > jbehave-site-resources 3.1.2 needs uploading to Maven Central repo > -- > > Key: JBEHAVE-406 > URL: http://jira.codehaus.org/browse/JBEHAVE-406 > Project: JBehave > Issue Type: Task >Affects Versions: 3.1.2 >Reporter: Alistair Dutton >Priority: Minor > > All the JBehave 3.1.2 artifacts look to be present and correct in the Maven > Central repository with the exception of jbehave-site-resources which is > missing (see > http://repo2.maven.org/maven2/org/jbehave/site/jbehave-site-resources/). > I tend to have a single "jbehave.version" property in my POMs - I've now > updated it 3.1.2 but my build now breaks because of a reference to the > jbehave-site-resources artifact in my maven-dependency-plugin definition. > It's a minor annoyance which can easily be worked around of course but > uploading it would be neater. > I'd happily have a go myself but I believe I would need to have my public PGP > key assigned the appropriate trusts before I could do so (which seems fair > enough!). -- 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-tabpanel&focusedCommentId=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 Map. > 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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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] Resolved: (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 resolved JBEHAVE-410. -- Resolution: Fixed > 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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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) {
> List traversalPaths = new ArrayList();
> 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) {
> List traversalPaths = new ArrayList();
> 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-tabpanel&focusedCommentId=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
[jbehave-dev] [jira] Resolved: (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 resolved JBEHAVE-408. -- Resolution: Fixed > 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] Resolved: (JBEHAVE-388) Support composition of steps
[
http://jira.codehaus.org/browse/JBEHAVE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-388.
--
Resolution: Fixed
> 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 has previously bought a
> {noformat}
> Could be a composition of
> {noformat}
> Given is logged in
> When they put a 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] Commented: (JBEHAVE-388) Support composition of steps
[
http://jira.codehaus.org/browse/JBEHAVE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253461#action_253461
]
Mauro Talevi commented on JBEHAVE-388:
--
Behaviour verified in trader example step_composition.story.
Documented in composite-steps.html
> 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 has previously bought a
> {noformat}
> Could be a composition of
> {noformat}
> Given is logged in
> When they put a 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-354) @Given, @When and @Then could make the pattern optional
[
http://jira.codehaus.org/browse/JBEHAVE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-354:
-
Fix Version/s: (was: 3.2)
3.x
> @Given, @When and @Then could make the pattern optional
> ---
>
> Key: JBEHAVE-354
> URL: http://jira.codehaus.org/browse/JBEHAVE-354
> Project: JBehave
> Issue Type: Improvement
> Components: Core
>Reporter: Paul Hammant
> Fix For: 3.x
>
>
> ... in that case the Java method that it pertains to could provide the
> matching expression:
> {code}
> @Given
> public void aUserWithALargeBankBalance { .. }
> {code}
> would be equiv to
> {code}
> @Given("a user with a large bank balance")
> public void aUserWithALargeBankBalance { .. }
> {code}
> or maybe we could endorse Ruby naming conventions for extra capitalization
> clarity:
> {code}
> @Given
> public void a_user_with_a_large_bank_balance { .. }
> {code}
> Obviously this is no good for cases where there are parameters. Though that
> could be solved too later, with yet more work.
> Guilherme Silveira's idea :)
--
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-361) Add configurable sorting strategies for stories in reports
[ http://jira.codehaus.org/browse/JBEHAVE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-361: - Fix Version/s: (was: 3.2) 3.x > Add configurable sorting strategies for stories in reports > -- > > Key: JBEHAVE-361 > URL: http://jira.codehaus.org/browse/JBEHAVE-361 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Mauro Talevi >Priority: Minor > Fix For: 3.x > > > Allow stories to be sorted by different configurable strategies: > - alphabetical > - by success/failure criteria > - by number of scenarios or steps -- 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-393) Split trader example different running modes into separate modules
[ http://jira.codehaus.org/browse/JBEHAVE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-393 started by Mauro Talevi. > Split trader example different running modes into separate modules > --- > > Key: JBEHAVE-393 > URL: http://jira.codehaus.org/browse/JBEHAVE-393 > Project: JBehave > Issue Type: Task > Components: Documentation >Reporter: Mauro Talevi >Assignee: Mauro Talevi >Priority: Minor > Fix For: 3.2 > > > Just like the Guice/Pico/Spring examples use the trader example code without > duplicating it (in particular the Steps classes) but have different > configurations and running modes, we could have different modules for the > other non-IoC configuration modes, e.g. AnnotatedEmbedderRunner, > JUnitStories, while still not duplicating the trader example code. > This would allow newcomers to get a better overview of the functionality. It > would also allow to exercise this funcionality without using profiles (as is > currently). -- 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-234) Improve JUnit integration
[ http://jira.codehaus.org/browse/JBEHAVE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-234. -- Resolution: Fixed Provided AnnotatedPathRunner as an extension of AnnotatedEmbedderRunner which creates a JUnit suite containing each story path and resolving the path to a human readable form that plays nicely with any IDE that provides JUnit integration. > 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] Updated: (JBEHAVE-394) Hudson Plugin to import JBehave reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-394: - Summary: Hudson Plugin to import JBehave reports (was: Hudson Plugin to import JBehave test reports) > Hudson Plugin to import JBehave 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: eclipse-jbehave-runner.png, hudson-jbehave-runner.png, > jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, jbehave-runner.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 reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253512#action_253512 ] Mauro Talevi commented on JBEHAVE-394: -- Alan, I've upgraded the dependency on the xUnit plugin to latest 1.13. Are you aware of any counter-indications to using latest version? It's unsavory that one needs to have the plugin already installed and the is no transitive dependency. If the xUnit plugin is not installed, the JBehave plugin fails without a meaningful error message in the UI (there is more detailed message in the log stacktrace). I've updated the description to make more visible and apparent the dependency requirement, but I want to provide better online documentation. Do you know how to configure in a Hudson plugin the clickable URL that appears on the plugins list? Currently defaults to http://jbehave.org/jbehave-hudson-plugin, but I'd like to be able to configure to something like http://jbehave.org/reference/stable/hudson-plugin. > Hudson Plugin to import JBehave 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: eclipse-jbehave-runner.png, hudson-jbehave-runner.png, > jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, jbehave-runner.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 reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253513#action_253513 ] Mauro Talevi commented on JBEHAVE-394: -- Bart, you may choose to run JBehave stories as JUnit test. You have that option, but there are significant use cases for having multiple execution entry points and report integration views with different tools. As always, JBehave likes to support multiple ways of doing the same thing and letting users decide what best suits their needs. > Hudson Plugin to import JBehave 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: eclipse-jbehave-runner.png, hudson-jbehave-runner.png, > jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, jbehave-runner.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 reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253525#action_253525 ] Mauro Talevi commented on JBEHAVE-394: -- Hi Alan, thanks for the pointer on the URL, the installation instructions and dependencies are now in on the doc page. The issue is that if the xUnit dependency is not installed, Hudson does not install the JBehave plugin, without giving any significant reason on the UI. BTW, given that then name will be soon changed to Jenkins, would it be worth to adopt that from the word go in place of Hudson? > Hudson Plugin to import JBehave 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: eclipse-jbehave-runner.png, hudson-jbehave-runner.png, > jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, jbehave-runner.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 reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253557#action_253557 ] Mauro Talevi commented on JBEHAVE-394: -- Yes, not the most user-friendly way to notify of a missing dependency. On the question of the name, I'm in two minds. But perhaps it's best (and easiest) to follow the trend rather than anticipate it. At the moment, we have a CI server call Hudson (of which, the releases will remain for future use) and for this we'll have the Hudson plugins. When the Jenkins fork will be released, we'll follow suite and release accordingly the renamed plugins. Being a simple rename, the two names will coexist for sometime anyway. > Hudson Plugin to import JBehave 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: eclipse-jbehave-runner.png, hudson-jbehave-runner.png, > jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, jbehave-runner.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 reports
[
http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253565#action_253565
]
Mauro Talevi commented on JBEHAVE-394:
--
So, one outstanding thing to verify is how the user accesses the reports. Once
the plugin is configured (e.g. to run the JBehave Core examples), I can see in
the logs:
{log}
[xUnit] [INFO] - Processing JBehave-3.x
[xUnit] [WARNING] - Can't create the path
/Users/mauro/.hudson/jobs/jbehave/workspace/generatedJUnitFiles. Maybe the
directory already exists.
[xUnit] [INFO] - [JBehave-3.x] - 19 test report file(s) were found with the
pattern '**/jbehave/org.jbehave.examples.*.xml' relative to
'/Users/mauro/.hudson/jobs/jbehave/workspace' for the testing framework
'JBehave-3.x'.
[xUnit] [INFO] - Converting
'/Users/mauro/.hudson/jobs/jbehave/workspace/examples/trader/target/jbehave/org.jbehave.examples.trader.stories.after_scenario_outcome.xml'
.
{log}
Other similar lines follow, but I can't see the test reports in the UI Test
Results.
Also, it shows
http://localhost:8080/job/jbehave/3/testReport/junit/org_jbehave_examples_trader_stories_failing_before_scenario/story/We_want_to_show_that_failures_in__BeforeScenario_methods_will_not_prevent_rest_of_scenario_steps_to_run__marked_as_NOT_PERFORMED___Also__the__Before_AfterScenario_failure_messages_should_be_displayed_in_the_output_reports_/
which is blank (showing error 404).
I would just like to clean up these issues.
I agree that publishing it to the Central Plugin repo is a good thing, which
we'll do post release after the dust has settled on the infrastructure.
> Hudson Plugin to import JBehave 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: eclipse-jbehave-runner.png, hudson-jbehave-runner.png,
> jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, jbehave-runner.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 reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253753#action_253753 ] Mauro Talevi commented on JBEHAVE-394: -- Hi Alan, I'm suspecting the problem may lie in the presence of the element which may not agree with the Hudson XSL. I noticed the unit test cases do not contemplate the presence of filters. Could you try to enhance the test (and probably the XSL) to allow filters? Thanks > Hudson Plugin to import JBehave 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: eclipse-jbehave-runner.png, hudson-jbehave-runner.png, > jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, jbehave-runner.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] Assigned: (JBEHAVE-421) StoryReporterBuilder.formatNames() should be locale-aware
[ http://jira.codehaus.org/browse/JBEHAVE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-421: Assignee: Mauro Talevi > StoryReporterBuilder.formatNames() should be locale-aware > - > > Key: JBEHAVE-421 > URL: http://jira.codehaus.org/browse/JBEHAVE-421 > Project: JBehave > Issue Type: Improvement > Components: Core >Affects Versions: 3.1.2 > Environment: Windows with Turkish locale, jbehave-3.1.2 >Reporter: Muammer Yucel >Assignee: Mauro Talevi >Priority: Blocker > Fix For: 3.2 > > > Add StoryReporterBuilder.formatNames(boolean, Locale) which defaults to > formatNames(boolean, Locale.ENGLISH). > Test case on Turkish locale: > StoryReporterBuilderBehaviour.shouldBuildWithReporterOfDifferentFormats > In Turkish, there are two letters in order to symbolize English's I. They are > I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and > lower case of "İ" (I with dot) is "i". Users from different nations may > encounter with this kind of problems. -- 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-421) StoryReporterBuilder.formatNames() should be locale-aware
[ http://jira.codehaus.org/browse/JBEHAVE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-421: - Component/s: Core Description: Add StoryReporterBuilder.formatNames(boolean, Locale) which defaults to formatNames(boolean, Locale.ENGLISH). Test case on Turkish locale: StoryReporterBuilderBehaviour.shouldBuildWithReporterOfDifferentFormats In Turkish, there are two letters in order to symbolize English's I. They are I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and lower case of "İ" (I with dot) is "i". Users from different nations may encounter with this kind of problems. was:org.jbehave.core.reporters.StoryReporterBuilderBehaviour.shouldBuildWithReporterOfDifferentFormats test fails when I try to compile jbehave source with maven on my windows machine with Turkish locale. Consider to use "name = name.toLowerCase(java.util.Locale.ENGLISH);" instead of "name = name.toLowerCase();" at line 150 of org.jbehave.core.reporters.StoryReporterBuilder. In Turkish, there are two letters in order to symbolize English's I. They are I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and lower case of "İ" (I with dot) is "i". Users from different nations may encounteer with this kind of problems. Affects Version/s: 3.1.2 Fix Version/s: 3.2 Issue Type: Improvement (was: Bug) Summary: StoryReporterBuilder.formatNames() should be locale-aware (was: org.jbehave.core.reporters.StoryReporterBuilderBehaviour test fails) > StoryReporterBuilder.formatNames() should be locale-aware > - > > Key: JBEHAVE-421 > URL: http://jira.codehaus.org/browse/JBEHAVE-421 > Project: JBehave > Issue Type: Improvement > Components: Core >Affects Versions: 3.1.2 > Environment: Windows with Turkish locale, jbehave-3.1.2 >Reporter: Muammer Yucel >Priority: Blocker > Fix For: 3.2 > > > Add StoryReporterBuilder.formatNames(boolean, Locale) which defaults to > formatNames(boolean, Locale.ENGLISH). > Test case on Turkish locale: > StoryReporterBuilderBehaviour.shouldBuildWithReporterOfDifferentFormats > In Turkish, there are two letters in order to symbolize English's I. They are > I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and > lower case of "İ" (I with dot) is "i". Users from different nations may > encounter with this kind of problems. -- 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-421) StoryReporterBuilder.formatNames() should be locale-aware
[ http://jira.codehaus.org/browse/JBEHAVE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-421: - Description: StoryReporterBuilder.formatNames(boolean) should use the locale specified in the LocalizedKeywords to retrieve the name lower case. If not specified, it defaults to Locale.getDefault(). Test case on Turkish locale: StoryReporterBuilderBehaviour.shouldBuildWithReporterOfDifferentFormats In Turkish, there are two letters in order to symbolize English's I. They are I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and lower case of "İ" (I with dot) is "i". Users from different nations may encounter with this kind of problems. was: Add StoryReporterBuilder.formatNames(boolean, Locale) which defaults to formatNames(boolean, Locale.ENGLISH). Test case on Turkish locale: StoryReporterBuilderBehaviour.shouldBuildWithReporterOfDifferentFormats In Turkish, there are two letters in order to symbolize English's I. They are I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and lower case of "İ" (I with dot) is "i". Users from different nations may encounter with this kind of problems. > StoryReporterBuilder.formatNames() should be locale-aware > - > > Key: JBEHAVE-421 > URL: http://jira.codehaus.org/browse/JBEHAVE-421 > Project: JBehave > Issue Type: Improvement > Components: Core >Affects Versions: 3.1.2 > Environment: Windows with Turkish locale, jbehave-3.1.2 >Reporter: Muammer Yucel >Assignee: Mauro Talevi >Priority: Blocker > Fix For: 3.2 > > > StoryReporterBuilder.formatNames(boolean) should use the locale specified in > the LocalizedKeywords to retrieve the name lower case. If not specified, it > defaults to Locale.getDefault(). > Test case on Turkish locale: > StoryReporterBuilderBehaviour.shouldBuildWithReporterOfDifferentFormats > In Turkish, there are two letters in order to symbolize English's I. They are > I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and > lower case of "İ" (I with dot) is "i". Users from different nations may > encounter with this kind of problems. -- 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-421) StoryReporterBuilder.formatNames() should be locale-aware
[ http://jira.codehaus.org/browse/JBEHAVE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253834#action_253834 ] Mauro Talevi commented on JBEHAVE-421: -- Pushed a fix for this but could not yet complete the test in the Turkish locale. Could you please provide a version of the keyworks_xx.properties for the Turkish locale? > StoryReporterBuilder.formatNames() should be locale-aware > - > > Key: JBEHAVE-421 > URL: http://jira.codehaus.org/browse/JBEHAVE-421 > Project: JBehave > Issue Type: Improvement > Components: Core >Affects Versions: 3.1.2 > Environment: Windows with Turkish locale, jbehave-3.1.2 >Reporter: Muammer Yucel >Assignee: Mauro Talevi >Priority: Blocker > Fix For: 3.2 > > > StoryReporterBuilder.formatNames(boolean) should use the locale specified in > the LocalizedKeywords to retrieve the name lower case. If not specified, it > defaults to Locale.getDefault(). > Test case on Turkish locale: > StoryReporterBuilderBehaviour.shouldBuildWithReporterOfDifferentFormats > In Turkish, there are two letters in order to symbolize English's I. They are > I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and > lower case of "İ" (I with dot) is "i". Users from different nations may > encounter with this kind of problems. -- 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-421) StoryReporterBuilder.formatNames() should be locale-aware
[ http://jira.codehaus.org/browse/JBEHAVE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-421 started by Mauro Talevi. > StoryReporterBuilder.formatNames() should be locale-aware > - > > Key: JBEHAVE-421 > URL: http://jira.codehaus.org/browse/JBEHAVE-421 > Project: JBehave > Issue Type: Improvement > Components: Core >Affects Versions: 3.1.2 > Environment: Windows with Turkish locale, jbehave-3.1.2 >Reporter: Muammer Yucel >Assignee: Mauro Talevi >Priority: Blocker > Fix For: 3.2 > > > StoryReporterBuilder.formatNames(boolean) should use the locale specified in > the LocalizedKeywords to retrieve the name lower case. If not specified, it > defaults to Locale.getDefault(). > Test case on Turkish locale: > StoryReporterBuilderBehaviour.shouldBuildWithReporterOfDifferentFormats > In Turkish, there are two letters in order to symbolize English's I. They are > I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and > lower case of "İ" (I with dot) is "i". Users from different nations may > encounter with this kind of problems. -- 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-421) StoryReporterBuilder.formatNames() should be locale-aware
[ http://jira.codehaus.org/browse/JBEHAVE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-421: - Priority: Major (was: Blocker) > StoryReporterBuilder.formatNames() should be locale-aware > - > > Key: JBEHAVE-421 > URL: http://jira.codehaus.org/browse/JBEHAVE-421 > Project: JBehave > Issue Type: Improvement > Components: Core >Affects Versions: 3.1.2 > Environment: Windows with Turkish locale, jbehave-3.1.2 >Reporter: Muammer Yucel >Assignee: Mauro Talevi > Fix For: 3.2 > > > StoryReporterBuilder.formatNames(boolean) should use the locale specified in > the LocalizedKeywords to retrieve the name lower case. If not specified, it > defaults to Locale.getDefault(). > Test case on Turkish locale: > StoryReporterBuilderBehaviour.shouldBuildWithReporterOfDifferentFormats > In Turkish, there are two letters in order to symbolize English's I. They are > I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and > lower case of "İ" (I with dot) is "i". Users from different nations may > encounter with this kind of problems. -- 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-422) Maven goal run-stories-with-annotated-embedder-runner doesn't exist
[ http://jira.codehaus.org/browse/JBEHAVE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-422. -- Resolution: Fixed > Maven goal run-stories-with-annotated-embedder-runner doesn't exist > --- > > Key: JBEHAVE-422 > URL: http://jira.codehaus.org/browse/JBEHAVE-422 > Project: JBehave > Issue Type: Bug > Components: Documentation >Affects Versions: 3.1.2 >Reporter: Gardella Juan Pablo >Assignee: Mauro Talevi >Priority: Minor > Fix For: 3.2 > > > In the documentation (http://jbehave.org/reference/latest/maven-goals.html) > reference a goal named: run-stories-with-annotated-embedder-runner that not > exist. Fix with > run-with-annotated-embedder -- 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-422) Maven goal run-stories-with-annotated-embedder-runner doesn't exist
[ http://jira.codehaus.org/browse/JBEHAVE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-422: - Fix Version/s: 3.2 Assignee: Mauro Talevi > Maven goal run-stories-with-annotated-embedder-runner doesn't exist > --- > > Key: JBEHAVE-422 > URL: http://jira.codehaus.org/browse/JBEHAVE-422 > Project: JBehave > Issue Type: Bug > Components: Documentation >Affects Versions: 3.1.2 >Reporter: Gardella Juan Pablo >Assignee: Mauro Talevi >Priority: Minor > Fix For: 3.2 > > > In the documentation (http://jbehave.org/reference/latest/maven-goals.html) > reference a goal named: run-stories-with-annotated-embedder-runner that not > exist. Fix with > run-with-annotated-embedder -- 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-426) BooleanConverter and BooleanListConverter
[ http://jira.codehaus.org/browse/JBEHAVE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-426: - Fix Version/s: 3.2 Issue Type: Improvement (was: New Feature) > BooleanConverter and BooleanListConverter > - > > Key: JBEHAVE-426 > URL: http://jira.codehaus.org/browse/JBEHAVE-426 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Larry Shatzer > Fix For: 3.2 > > > Need to provide a BooleanConverter and BooleanListConverter -- 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-426) BooleanConverter and BooleanListConverter
[ http://jira.codehaus.org/browse/JBEHAVE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-426. -- Resolution: Fixed Pulled, thanks! > BooleanConverter and BooleanListConverter > - > > Key: JBEHAVE-426 > URL: http://jira.codehaus.org/browse/JBEHAVE-426 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Larry Shatzer > Fix For: 3.2 > > > Need to provide a BooleanConverter and BooleanListConverter -- 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-421) Use of String.toUpper/LowerCase() should be locale-aware
[ http://jira.codehaus.org/browse/JBEHAVE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-421: - Component/s: Core > Use of String.toUpper/LowerCase() should be locale-aware > > > Key: JBEHAVE-421 > URL: http://jira.codehaus.org/browse/JBEHAVE-421 > Project: JBehave > Issue Type: Improvement > Components: Core, Web Selenium >Affects Versions: 3.1.2 > Environment: Windows with Turkish locale, jbehave-3.1.2 >Reporter: Muammer Yucel >Assignee: Mauro Talevi > Fix For: 3.2 > > Attachments: keywords_tr.properties > > > In Turkish, there are two letters in order to symbolize English's I. They are > I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and > lower case of "İ" (I with dot) is "i". Users from different nations may > encounter with this kind of problems, which come to surface when using > String.toUpper/LowerCase(). The solution is to use > String.toUpper/LowerCase(Locale), while defaulting to Locale.getDefault() if > none specified. > String.toLowerCase() is currently used in: > - StoryReporterBuilder.formatNames(boolean): should use the locale specified > in the LocalizedKeywords to retrieve the name lower case. If not specified, > it defaults to Locale.getDefault(). > - UnderscoredCamelCaseResolver: should provide a constructor to inject a > non-default Locale > String.toUpperCase() is currently used in: > - PropertyWebDriverProvider: should provide a protected method > toUpperCase(String) which can be overridden use the desired Locale. -- 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-421) Use of String.toUpper/LowerCase() should be locale-aware
[ http://jira.codehaus.org/browse/JBEHAVE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-421: - Component/s: (was: Core) Web Selenium Description: In Turkish, there are two letters in order to symbolize English's I. They are I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and lower case of "İ" (I with dot) is "i". Users from different nations may encounter with this kind of problems, which come to surface when using String.toUpper/LowerCase(). The solution is to use String.toUpper/LowerCase(Locale), while defaulting to Locale.getDefault() if none specified. String.toLowerCase() is currently used in: - StoryReporterBuilder.formatNames(boolean): should use the locale specified in the LocalizedKeywords to retrieve the name lower case. If not specified, it defaults to Locale.getDefault(). - UnderscoredCamelCaseResolver: should provide a constructor to inject a non-default Locale String.toUpperCase() is currently used in: - PropertyWebDriverProvider: should provide a protected method toUpperCase(String) which can be overridden use the desired Locale. was: StoryReporterBuilder.formatNames(boolean) should use the locale specified in the LocalizedKeywords to retrieve the name lower case. If not specified, it defaults to Locale.getDefault(). Test case on Turkish locale: StoryReporterBuilderBehaviour.shouldBuildWithReporterOfDifferentFormats In Turkish, there are two letters in order to symbolize English's I. They are I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and lower case of "İ" (I with dot) is "i". Users from different nations may encounter with this kind of problems. Summary: Use of String.toUpper/LowerCase() should be locale-aware (was: StoryReporterBuilder.formatNames() should be locale-aware) > Use of String.toUpper/LowerCase() should be locale-aware > > > Key: JBEHAVE-421 > URL: http://jira.codehaus.org/browse/JBEHAVE-421 > Project: JBehave > Issue Type: Improvement > Components: Core, Web Selenium >Affects Versions: 3.1.2 > Environment: Windows with Turkish locale, jbehave-3.1.2 >Reporter: Muammer Yucel >Assignee: Mauro Talevi > Fix For: 3.2 > > Attachments: keywords_tr.properties > > > In Turkish, there are two letters in order to symbolize English's I. They are > I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and > lower case of "İ" (I with dot) is "i". Users from different nations may > encounter with this kind of problems, which come to surface when using > String.toUpper/LowerCase(). The solution is to use > String.toUpper/LowerCase(Locale), while defaulting to Locale.getDefault() if > none specified. > String.toLowerCase() is currently used in: > - StoryReporterBuilder.formatNames(boolean): should use the locale specified > in the LocalizedKeywords to retrieve the name lower case. If not specified, > it defaults to Locale.getDefault(). > - UnderscoredCamelCaseResolver: should provide a constructor to inject a > non-default Locale > String.toUpperCase() is currently used in: > - PropertyWebDriverProvider: should provide a protected method > toUpperCase(String) which can be overridden use the desired Locale. -- 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-394) Hudson Plugin to import JBehave reports
[ http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-394. -- Resolution: Fixed > Hudson Plugin to import JBehave 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: eclipse-jbehave-runner.png, hudson-jbehave-runner.png, > jbehave-hudson-plugin-0.1.zip, jbehave-hudson-plugin.zip, jbehave-runner.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] Resolved: (JBEHAVE-421) Use of String.toUpper/LowerCase() should be locale-aware
[ http://jira.codehaus.org/browse/JBEHAVE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-421. -- Resolution: Fixed Fix Version/s: web-3.2 > Use of String.toUpper/LowerCase() should be locale-aware > > > Key: JBEHAVE-421 > URL: http://jira.codehaus.org/browse/JBEHAVE-421 > Project: JBehave > Issue Type: Improvement > Components: Core, Web Selenium >Affects Versions: 3.1.2 > Environment: Windows with Turkish locale, jbehave-3.1.2 >Reporter: Muammer Yucel >Assignee: Mauro Talevi > Fix For: 3.2, web-3.2 > > Attachments: keywords_tr.properties > > > In Turkish, there are two letters in order to symbolize English's I. They are > I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and > lower case of "İ" (I with dot) is "i". Users from different nations may > encounter with this kind of problems, which come to surface when using > String.toUpper/LowerCase(). The solution is to use > String.toUpper/LowerCase(Locale), while defaulting to Locale.getDefault() if > none specified. > String.toLowerCase() is currently used in: > - StoryReporterBuilder.formatNames(boolean): should use the locale specified > in the LocalizedKeywords to retrieve the name lower case. If not specified, > it defaults to Locale.getDefault(). > - UnderscoredCamelCaseResolver: should provide a constructor to inject a > non-default Locale > String.toUpperCase() is currently used in: > - PropertyWebDriverProvider: should provide a protected method > toUpperCase(String) which can be overridden use the desired Locale. -- 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-421) Use of String.toUpper/LowerCase() should be locale-aware
[ http://jira.codehaus.org/browse/JBEHAVE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-421: - Description: In Turkish, there are two letters in order to symbolize English's I. They are I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and lower case of "İ" (I with dot) is "i". Users from different nations may encounter with this kind of problems, which come to surface when using String.toUpper/LowerCase(). The solution is to use String.toUpper/LowerCase(Locale), while defaulting to Locale.getDefault() if none specified. String.toLowerCase() is currently used in: - StoryReporterBuilder.formatNames(boolean): should use the locale specified in the LocalizedKeywords to retrieve the name lower case. If not specified, it defaults to Locale.getDefault(). - UnderscoredCamelCaseResolver: should provide a constructor to inject a non-default Locale String.toUpperCase() is currently used in: - PropertyWebDriverProvider: should provide a protected method usingLocale() which can be overridden use the desired Locale. was: In Turkish, there are two letters in order to symbolize English's I. They are I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and lower case of "İ" (I with dot) is "i". Users from different nations may encounter with this kind of problems, which come to surface when using String.toUpper/LowerCase(). The solution is to use String.toUpper/LowerCase(Locale), while defaulting to Locale.getDefault() if none specified. String.toLowerCase() is currently used in: - StoryReporterBuilder.formatNames(boolean): should use the locale specified in the LocalizedKeywords to retrieve the name lower case. If not specified, it defaults to Locale.getDefault(). - UnderscoredCamelCaseResolver: should provide a constructor to inject a non-default Locale String.toUpperCase() is currently used in: - PropertyWebDriverProvider: should provide a protected method toUpperCase(String) which can be overridden use the desired Locale. > Use of String.toUpper/LowerCase() should be locale-aware > > > Key: JBEHAVE-421 > URL: http://jira.codehaus.org/browse/JBEHAVE-421 > Project: JBehave > Issue Type: Improvement > Components: Core, Web Selenium >Affects Versions: 3.1.2 > Environment: Windows with Turkish locale, jbehave-3.1.2 >Reporter: Muammer Yucel >Assignee: Mauro Talevi > Fix For: 3.2, web-3.2 > > Attachments: keywords_tr.properties > > > In Turkish, there are two letters in order to symbolize English's I. They are > I and İ (I with dot). Lower case of "I" is "ı" (i without dot) and > lower case of "İ" (I with dot) is "i". Users from different nations may > encounter with this kind of problems, which come to surface when using > String.toUpper/LowerCase(). The solution is to use > String.toUpper/LowerCase(Locale), while defaulting to Locale.getDefault() if > none specified. > String.toLowerCase() is currently used in: > - StoryReporterBuilder.formatNames(boolean): should use the locale specified > in the LocalizedKeywords to retrieve the name lower case. If not specified, > it defaults to Locale.getDefault(). > - UnderscoredCamelCaseResolver: should provide a constructor to inject a > non-default Locale > String.toUpperCase() is currently used in: > - PropertyWebDriverProvider: should provide a protected method usingLocale() > which can be overridden use the desired Locale. -- 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-427) Interactive Story Navigator view
[ http://jira.codehaus.org/browse/JBEHAVE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-427: - Description: An HTML app that reads JSON and allows interactive searching through stories/scenarios Made by Dallas "GeekNight" folks was:made by Dallas "GeekNight" folks Summary: Interactive Story Navigator view (was: StoryNavigator HTML app that reads JSON and allows interactive searching through stories/scenarios) > Interactive Story Navigator view > - > > Key: JBEHAVE-427 > URL: http://jira.codehaus.org/browse/JBEHAVE-427 > Project: JBehave > Issue Type: New Feature > Components: Core >Reporter: Paul Hammant >Assignee: Paul Hammant > Fix For: 3.2 > > > An HTML app that reads JSON and allows interactive searching through > stories/scenarios > Made by Dallas "GeekNight" folks -- 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-427) Interactive Story Navigator view
[ http://jira.codehaus.org/browse/JBEHAVE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-427: Assignee: Mauro Talevi (was: Paul Hammant) > Interactive Story Navigator view > - > > Key: JBEHAVE-427 > URL: http://jira.codehaus.org/browse/JBEHAVE-427 > Project: JBehave > Issue Type: New Feature > Components: Core >Reporter: Paul Hammant >Assignee: Mauro Talevi > Fix For: 3.2 > > > An HTML app that reads JSON and allows interactive searching through > stories/scenarios > Made by Dallas "GeekNight" folks -- 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-427) Interactive Story Navigator view
[ http://jira.codehaus.org/browse/JBEHAVE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-427 started by Mauro Talevi. > Interactive Story Navigator view > - > > Key: JBEHAVE-427 > URL: http://jira.codehaus.org/browse/JBEHAVE-427 > Project: JBehave > Issue Type: New Feature > Components: Core >Reporter: Paul Hammant >Assignee: Mauro Talevi > Fix For: 3.2 > > > An HTML app that reads JSON and allows interactive searching through > stories/scenarios > Made by Dallas "GeekNight" folks -- 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-tabpanel&focusedCommentId=255419#action_255419 ] Mauro Talevi commented on JBEHAVE-398: -- Pulled up Row interface with the "raw" values, which is implemented by ChainedRow, as suggested in the patch. > 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 Map. > 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-427) Interactive Story Navigator view
[ http://jira.codehaus.org/browse/JBEHAVE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256362#action_256362 ] Mauro Talevi commented on JBEHAVE-427: -- Navigator view was not being generated because the reports view is always generated before and failures cause the stop of the execution via an exception being thrown. Changed handling logic to always generate the navigator view regardless of the results of the reports view. Removed hack-fix in EtsyStories. > Interactive Story Navigator view > - > > Key: JBEHAVE-427 > URL: http://jira.codehaus.org/browse/JBEHAVE-427 > Project: JBehave > Issue Type: New Feature > Components: Core >Reporter: Paul Hammant >Assignee: Mauro Talevi > Fix For: 3.2 > > > An HTML app that reads JSON and allows interactive searching through > stories/scenarios > Made by Dallas "GeekNight" folks -- 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-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 resolved JBEHAVE-398. -- Resolution: Fixed > 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 Map. > 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] Updated: (JBEHAVE-400) Error in WebDriverProvider intialize method ignored because of consequential NPE for StoryRunner.reporter
[
http://jira.codehaus.org/browse/JBEHAVE-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-400:
-
Affects Version/s: (was: 3.2)
web-3.1
Fix Version/s: 3.2
> Error in WebDriverProvider intialize method ignored because of consequential
> NPE for StoryRunner.reporter
> -
>
> Key: JBEHAVE-400
> URL: http://jira.codehaus.org/browse/JBEHAVE-400
> Project: JBehave
> Issue Type: Bug
> Components: Web Selenium
>Affects Versions: web-3.1
>Reporter: Paul Hammant
> Fix For: 3.2
>
> Attachments: BadlyInitializingWebDriverStepsTest.java
>
>
> {noformat}
> new WebDriverProvider() {
>public void initialize() {
> throw new RuntimeException(); // or Error or something
>}
> }
> {noformat}
> ... does not get reported. It's consumed because of a later NPE
> The NPE is in StoryRunner, concerning member variable 'reporter' which is not
> set before use, in this situation.
--
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-432) StepPattern to encapsulate both annotated and resolved patterns and report to the StepMonitor
[ http://jira.codehaus.org/browse/JBEHAVE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-432: - Description: Currently, only the resolved regex pattern is reported to the StepMonitor, e.g. stepMatchesPattern(String step, boolean matches, String pattern, Method method, Object stepsInstance) where is step is: matching steps were coded in English to make it easier for people to understand the resolved regex pattern is: matching\s+steps\s+were\s+coded\s+in\s+(.*)\s+to\s+make\s+it\s+easier\s+for\s+people\s+to\s+understand It's also useful to report the annotated pattern: matching steps were coded in $language to make it easier for people to understand A new StepPattern model class should encapsultate both annotated and resolved patterns, and the method should thus read: stepMatchesPattern(String step, boolean matches, StepPattern pattern, Method method, Object stepsInstance) was: stepMatchesPattern(String step, boolean matches, String pattern, Method method, Object stepsInstance) Of the two strings passed in, one is: matching steps were coded in English to make it easier for people to understand the other is: matching\s+steps\s+were\s+coded\s+in\s+(.*)\s+to\s+make\s+it\s+easier\s+for\s+people\s+to\s+understand I need this one too: matching steps were coded in $language to make it easier for people to understand - Paul Fix Version/s: 3.2 Assignee: Mauro Talevi Summary: StepPattern to encapsulate both annotated and resolved patterns and report to the StepMonitor (was: StepMonitor.stepMatchesPattern signature change) > StepPattern to encapsulate both annotated and resolved patterns and report to > the StepMonitor > - > > Key: JBEHAVE-432 > URL: http://jira.codehaus.org/browse/JBEHAVE-432 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Paul Hammant >Assignee: Mauro Talevi >Priority: Minor > Fix For: 3.2 > > > Currently, only the resolved regex pattern is reported to the StepMonitor, > e.g. > stepMatchesPattern(String step, boolean matches, String pattern, Method > method, Object stepsInstance) > where is step is: >matching steps were coded in English to make it easier for people to > understand > the resolved regex pattern is: > > matching\s+steps\s+were\s+coded\s+in\s+(.*)\s+to\s+make\s+it\s+easier\s+for\s+people\s+to\s+understand > It's also useful to report the annotated pattern: >matching steps were coded in $language to make it easier for people to > understand > A new StepPattern model class should encapsultate both annotated and resolved > patterns, and the method should thus read: > stepMatchesPattern(String step, boolean matches, StepPattern pattern, Method > method, Object stepsInstance) -- 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-427) Add CrossReference report
[ http://jira.codehaus.org/browse/JBEHAVE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-427: - Description: As contributed by the Dallas "GeekNight" folks, a xref JSON and XML data report that can be consumed by different views. was: An HTML app that reads JSON and allows interactive searching through stories/scenarios Made by Dallas "GeekNight" folks Summary: Add CrossReference report (was: Interactive Story Navigator view ) > Add CrossReference report > - > > Key: JBEHAVE-427 > URL: http://jira.codehaus.org/browse/JBEHAVE-427 > Project: JBehave > Issue Type: New Feature > Components: Core >Reporter: Paul Hammant >Assignee: Mauro Talevi > Fix For: 3.2 > > > As contributed by the Dallas "GeekNight" folks, a xref JSON and XML data > report that can be consumed by different views. -- 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-427) Add CrossReference report
[ http://jira.codehaus.org/browse/JBEHAVE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-427: - Comment: was deleted (was: Navigator view was not being generated because the reports view is always generated before and failures cause the stop of the execution via an exception being thrown. Changed handling logic to always generate the navigator view regardless of the results of the reports view. Removed hack-fix in EtsyStories.) > Add CrossReference report > - > > Key: JBEHAVE-427 > URL: http://jira.codehaus.org/browse/JBEHAVE-427 > Project: JBehave > Issue Type: New Feature > Components: Core >Reporter: Paul Hammant >Assignee: Mauro Talevi > Fix For: 3.2 > > > As contributed by the Dallas "GeekNight" folks, a xref JSON and XML data > report that can be consumed by different views. -- 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-427) Add CrossReference report
[ http://jira.codehaus.org/browse/JBEHAVE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-427: - Comment: was deleted (was: Part working, part not == With no failures means target/jbehave/view/navigator.html generated. With failures means target/jbehave/view/navigator.html generated is missing. For some strange reason this is unlike /reports.html. It is easy to reproduce - comment out the hack-fix override of run() in EtsyStories. Also make one of the steps fail, before running the suite.) > Add CrossReference report > - > > Key: JBEHAVE-427 > URL: http://jira.codehaus.org/browse/JBEHAVE-427 > Project: JBehave > Issue Type: New Feature > Components: Core >Reporter: Paul Hammant >Assignee: Mauro Talevi > Fix For: 3.2 > > > As contributed by the Dallas "GeekNight" folks, a xref JSON and XML data > report that can be consumed by different views. -- 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-432) StepPattern to encapsulate both annotated and resolved patterns and report to the StepMonitor
[ http://jira.codehaus.org/browse/JBEHAVE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-432. -- Resolution: Fixed > StepPattern to encapsulate both annotated and resolved patterns and report to > the StepMonitor > - > > Key: JBEHAVE-432 > URL: http://jira.codehaus.org/browse/JBEHAVE-432 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Paul Hammant >Assignee: Mauro Talevi >Priority: Minor > Fix For: 3.2 > > > Currently, only the resolved regex pattern is reported to the StepMonitor, > e.g. > stepMatchesPattern(String step, boolean matches, String pattern, Method > method, Object stepsInstance) > where is step is: >matching steps were coded in English to make it easier for people to > understand > the resolved regex pattern is: > > matching\s+steps\s+were\s+coded\s+in\s+(.*)\s+to\s+make\s+it\s+easier\s+for\s+people\s+to\s+understand > It's also useful to report the annotated pattern: >matching steps were coded in $language to make it easier for people to > understand > A new StepPattern model class should encapsultate both annotated and resolved > patterns, and the method should thus read: > stepMatchesPattern(String step, boolean matches, StepPattern pattern, Method > method, Object stepsInstance) -- 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-434) Stack Traces should be compressible in printed output
[ http://jira.codehaus.org/browse/JBEHAVE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-434: - Summary: Stack Traces should be compressible in printed output (was: Stack Traces should be smaller in printed output.) > Stack Traces should be compressible in printed output > - > > Key: JBEHAVE-434 > URL: http://jira.codehaus.org/browse/JBEHAVE-434 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Paul Hammant >Assignee: Paul Hammant >Priority: Minor > Fix For: 3.2 > > > Reflection has three lines that don't need to be in a stack for a QA engineer > to debug with. > Groovy has three different fragments of stack (4 to 6 lines each) that don't > need to be in a stack for a QA engineer to debug with. -- 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-427) Add CrossReference report
[ http://jira.codehaus.org/browse/JBEHAVE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-427. -- Resolution: Fixed > Add CrossReference report > - > > Key: JBEHAVE-427 > URL: http://jira.codehaus.org/browse/JBEHAVE-427 > Project: JBehave > Issue Type: New Feature > Components: Core >Reporter: Paul Hammant >Assignee: Mauro Talevi > Fix For: 3.2 > > > As contributed by the Dallas "GeekNight" folks, a xref JSON and XML data > report that can be consumed by different views. -- 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-434) Stack Traces should be compressible in printed output
[ http://jira.codehaus.org/browse/JBEHAVE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-434: - Description: Reflection has three lines that don't need to be in a stack for a QA engineer to debug with. Groovy has three different fragments of stack (4 to 6 lines each) that don't need to be in a stack for a QA engineer to debug with. The compression behaviour (off by default) should be configurable via a boolean flag in the StoryReporterBuilder. was: Reflection has three lines that don't need to be in a stack for a QA engineer to debug with. Groovy has three different fragments of stack (4 to 6 lines each) that don't need to be in a stack for a QA engineer to debug with. > Stack Traces should be compressible in printed output > - > > Key: JBEHAVE-434 > URL: http://jira.codehaus.org/browse/JBEHAVE-434 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Paul Hammant >Assignee: Paul Hammant >Priority: Minor > Fix For: 3.2 > > > Reflection has three lines that don't need to be in a stack for a QA engineer > to debug with. > Groovy has three different fragments of stack (4 to 6 lines each) that don't > need to be in a stack for a QA engineer to debug with. > The compression behaviour (off by default) should be configurable via a > boolean flag in the StoryReporterBuilder. -- 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-434) Stack Traces should be compressible in printed output
[ http://jira.codehaus.org/browse/JBEHAVE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-434. -- Resolution: Fixed > Stack Traces should be compressible in printed output > - > > Key: JBEHAVE-434 > URL: http://jira.codehaus.org/browse/JBEHAVE-434 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Paul Hammant >Assignee: Paul Hammant >Priority: Minor > Fix For: 3.2 > > > Reflection has three lines that don't need to be in a stack for a QA engineer > to debug with. > Groovy has three different fragments of stack (4 to 6 lines each) that don't > need to be in a stack for a QA engineer to debug with. > The compression behaviour (off by default) should be configurable via a > boolean flag in the StoryReporterBuilder. -- 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-435) MetaFilters not properly read from the configuration
[ http://jira.codehaus.org/browse/JBEHAVE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-435. -- Resolution: Fixed > MetaFilters not properly read from the configuration > > > Key: JBEHAVE-435 > URL: http://jira.codehaus.org/browse/JBEHAVE-435 > Project: JBehave > Issue Type: Bug > Components: Maven Plugin >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.2 > > > The meta filters configuration of the Maven Mojo is not properly being read > and passed as null to the Embedder. > Solution is use String[] in place of List, as generics are at times > not properly handled in Maven 2. > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-435) MetaFilters not properly read from the configuration
MetaFilters not properly read from the configuration Key: JBEHAVE-435 URL: http://jira.codehaus.org/browse/JBEHAVE-435 Project: JBehave Issue Type: Bug Components: Maven Plugin Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.2 The meta filters configuration of the Maven Mojo is not properly being read and passed as null to the Embedder. Solution is use String[] in place of List, as generics are at times not properly handled in Maven 2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-437) Allow to report stepdocs as embeddables
Allow to report stepdocs as embeddables --- Key: JBEHAVE-437 URL: http://jira.codehaus.org/browse/JBEHAVE-437 Project: JBehave Issue Type: Improvement Components: Ant Tasks, Core, Maven Plugin Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.2 Currently, we can report stepdocs by specifying the complete Embedder instance, fully configured and with CandidateSteps. Another, even more common use case, is to want to report the stepdocs for the candidate steps that are defined for given Embeddable instances, such as JUnitStory or JUnitStories. -- 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-437) Allow to report stepdocs as embeddables
[ http://jira.codehaus.org/browse/JBEHAVE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-437. -- Resolution: Fixed > Allow to report stepdocs as embeddables > --- > > Key: JBEHAVE-437 > URL: http://jira.codehaus.org/browse/JBEHAVE-437 > Project: JBehave > Issue Type: Improvement > Components: Ant Tasks, Core, Maven Plugin >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.2 > > > Currently, we can report stepdocs by specifying the complete Embedder > instance, fully configured and with CandidateSteps. > Another, even more common use case, is to want to report the stepdocs for the > candidate steps that are defined for given Embeddable instances, such as > JUnitStory or JUnitStories. -- 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-436) StoryMaps generation relies on stories in a directory (package). Packageless stories don't have a name in the final output.
[ http://jira.codehaus.org/browse/JBEHAVE-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-436: - Component/s: Core Fix Version/s: (was: 3.3) 3.2 Assignee: Mauro Talevi > StoryMaps generation relies on stories in a directory (package). Packageless > stories don't have a name in the final output. > > > Key: JBEHAVE-436 > URL: http://jira.codehaus.org/browse/JBEHAVE-436 > Project: JBehave > Issue Type: Bug > Components: Core >Reporter: Paul Hammant >Assignee: Mauro Talevi >Priority: Minor > 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-436) StoryMaps generation relies on stories in a directory (package). Packageless stories don't have a name in the final output.
[ http://jira.codehaus.org/browse/JBEHAVE-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-436. -- Resolution: Fixed Fixed UnderscoredToCapitalized impl of StoryNameResolver to allow for packageless paths. > StoryMaps generation relies on stories in a directory (package). Packageless > stories don't have a name in the final output. > > > Key: JBEHAVE-436 > URL: http://jira.codehaus.org/browse/JBEHAVE-436 > Project: JBehave > Issue Type: Bug > Components: Core >Reporter: Paul Hammant >Assignee: Mauro Talevi >Priority: Minor > 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] Assigned: (JBEHAVE-440) JBehave i18n: Some german translations in keyword_de.properties are WRONG!
[
http://jira.codehaus.org/browse/JBEHAVE-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi reassigned JBEHAVE-440:
Assignee: Mauro Talevi
> JBehave i18n: Some german translations in keyword_de.properties are WRONG!
> --
>
> Key: JBEHAVE-440
> URL: http://jira.codehaus.org/browse/JBEHAVE-440
> Project: JBehave
> Issue Type: Bug
>Reporter: Florian Beckmann
>Assignee: Mauro Talevi
> Fix For: 3.3
>
> Attachments: keywords_de.properties
>
>
> I'm using jbehave (for the first time) in a project for a german customer and
> I would, of course, like to write the user stories in german.
> I had a short look into the keyword_de.properties and would like to make some
> corrections/suggestions:
>
> 1. Scenario=Scenario:
> ---should be---
> Scenario=Szenario:
>
> Spelled with 'z' instead of 'c'.
>
> 2 GivenStories=VorgegebeneGeschichten\:
> ---should be---
> GivenStories=GegebeneStories\:
>
> Instead of "vorgegebene" simply use "gegebene". And I would not even
> translate
> Story/Stories because it's already a "germanized" term, meaning it has been
> accepted in the german language especially within the "business community".
>
> 3. Given=Vorgegeben
> ---should be---
> Given=Gegeben
>
> As mentioned before.
>
> 4. When=Wann
> ---should be---
> When=Wenn
>
> "Wann" is simply WRONG in this case. Even though a correct translation of
> the word "when", but only if it is related to "time"/ a temporal term. You
> have to use the conditional "Wenn" which you could also translate into
> english
> as "if": http://german.about.com/library/blconfus_wann.htm
>
> 5. NotPerformed=NICHT ERF\u00DCLLT
> ---should be---
> NotPerformed=NICHT AUSGEF\u00DCHRT
>
> "To perform" is "ausführen" in german, hence "NICHT AUSGEFÜHRT" would be
> the correct translation. "Erfüllen/erfüllt" actually means "fullfilled"
>
> That's it!
>
> I attached the corrected properties file. Would be nice if you or someone
> from the jbehave team could include it in the next release if possible.
>
> I know this will break compatibility with older releases, but since one
> of the main keywords ("when") is translated completely wrong I can hardly
> imagine that someone used the German translations yet. Actually it should
> even be
> replaced/patched in older releases.
>
--
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-440) JBehave i18n: Some german translations in keyword_de.properties are WRONG!
[
http://jira.codehaus.org/browse/JBEHAVE-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-440:
-
Description:
I'm using jbehave (for the first time) in a project for a german customer and I
would, of course, like to write the user stories in german.
I had a short look into the keyword_de.properties and would like to make some
corrections/suggestions:
1. Scenario=Scenario:
---should be---
Scenario=Szenario:
Spelled with 'z' instead of 'c'.
2 GivenStories=VorgegebeneGeschichten\:
---should be---
GivenStories=GegebeneStories\:
Instead of "vorgegebene" simply use "gegebene". And I would not even translate
Story/Stories because it's already a "germanized" term, meaning it has been
accepted in the german language especially within the "business community".
3. Given=Vorgegeben
---should be---
Given=Gegeben
As mentioned before.
4. When=Wann
---should be---
When=Wenn
"Wann" is simply WRONG in this case. Even though a correct translation of
the word "when", but only if it is related to "time"/ a temporal term. You
have to use the conditional "Wenn" which you could also translate into english
as "if": http://german.about.com/library/blconfus_wann.htm
5. NotPerformed=NICHT ERF\u00DCLLT
---should be---
NotPerformed=NICHT AUSGEF\u00DCHRT
"To perform" is "ausführen" in german, hence "NICHT AUSGEFÜHRT" would be
the correct translation. "Erfüllen/erfüllt" actually means "fullfilled"
That's it!
I attached the corrected properties file. Would be nice if you or someone
from the jbehave team could include it in the next release if possible.
I know this will break compatibility with older releases, but since one
of the main keywords ("when") is translated completely wrong I can hardly
imagine that someone used the German translations yet. Actually it should even
be
replaced/patched in older releases.
was:
For simplicity I just pasted our mail conversation:
---
Great stuff.
Thanks Florian, and thanks Mauro for being insanely responsive. You replied
before I even saw the email!
Cheers,
Dan
On 23 February 2011 14:02, Mauro Talevi wrote:
> Hi Florian,
>
> thanks for your feedback, much appreciated.
>
> Can you please create an issue in jira at
> http://jira.codehaus.org/browse/JBEHAVE attaching the correct keywords
> and I'll add them in.
>
> As for not traslating, Story/Stories we'll take your advice.
>
> Cheers,
> Mauro
>
> On 23/02/2011 14:55, Florian Beckmann wrote:
> > Hi Dan,
> >
> > I'm using jbehave (for the first time) in a project for a german customer
> and I
> > would, of course, like to write the user stories in german.
> >
> > I had a short look into the keyword_de.properties and would like to make
> some
> > corrections/suggestions:
> >
> > 1.
> > Scenario=Scenario:
> > ---should be--->
> > Scenario=Szenario:
> >
> > Spelled with 'z' instead of 'c'.
> >
> > 2.
> > GivenStories=VorgegebeneGeschichten\:
> > ---should be--->
> > GivenStories=GegebeneStories\:
> >
> > Instead of "vorgegebene" simply use "gegebene". And I would not even
> translate
> > Story/Stories because it's already a "germanized" term, meaning it has
> been
> > accepted in the german language especially within the "business
> community".
> >
> > 3.
> > Given=Vorgegeben
> > ---should be--->
> > Given=Gegeben
> >
> > As mentioned before.
> >
> > 4.
> > When=Wann
> > ---should be--->
> > When=Wenn
> >
> > "Wann" is simply WRONG in this case. Even though a correct translation of
> the
> > word "when", but only if it is related to "time"/ a temporal term. You
> have
> > to use the conditional "Wenn" which you could also translate into english
> as
> > "if": http://german.about.com/library/blconfus_wann.htm
> >
> > 5.
> > NotPerformed=NICHT ERF\u00DCLLT
> > ---should be--->
> > NotPerformed=NICHT AUSGEF\u00DCHRT
> >
> > "To perform" is "ausführen" in german, hence "NICHT AUSGEFÜHRT" would be
> the
> > correct translation. "Erfüllen/erfüllt" actually means "fullfilled"
> >
> > That's it!
> >
> > I attached the corrected properties file. Would be nice if you or someone
> from
> > the jbehave team could include it in the next release if possible.
> >
> > I know this will break compatibility with older releases, but since one
> of the
> > main keywords ("when") is translated completely wrong I can hardly
> imagine
> > that someone used the german translations yet. Actually it should even be
> > replaced/patched in older releases.
> >
> > cheers
> > Florian Beckmann
> >
---
Fix Version/s: 3.3
> JBehave i18n: Some german translations in keyword_de.properties are WRONG!
> --
>
> Key: JBEHAVE-440
> URL: http://jira.codehaus.org/browse/JBEHAVE-440
> Project: JBehave
> Issue Type: Bug
>Reporter: Florian Beckmann
>
