[jbehave-dev] [jira] Updated: (JBEHAVE-397) Failure to execute all scenarios within a story.
[ http://jira.codehaus.org/browse/JBEHAVE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-397: - Component/s: Core Fix Version/s: 3.2 > Failure to execute all scenarios within a story. > > > Key: JBEHAVE-397 > URL: http://jira.codehaus.org/browse/JBEHAVE-397 > Project: JBehave > Issue Type: Bug > Components: Core >Reporter: Daniel Godfrey > Fix For: 3.2 > > > Given a story with 2 scenarios, the 2nd of which has GivenStores, if the > first scenario fails, the second scenario will not execute fully, execution > will finish when it's first GivenStory finishes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-401) XML Scenario reporter doesn't always include a closing story xml tag
[ http://jira.codehaus.org/browse/JBEHAVE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-401: - Fix Version/s: 3.2 > XML Scenario reporter doesn't always include a closing story xml tag > > > Key: JBEHAVE-401 > URL: http://jira.codehaus.org/browse/JBEHAVE-401 > Project: JBehave > Issue Type: Bug > Components: Core >Affects Versions: 3.1.2 > Environment: Windows 7 and Linux x86 >Reporter: Alan Parkinson > Fix For: 3.2 > > Attachments: > org.jbehave.examples.trader.stories.failure_followed_by_given_stories.xml > > > When running the trader example, the story > org/jbehave/examples/trader/stories/failure_followed_by_given_stories.story > generates an invalid XML file by not including a final closing "story" tag. > Attached is the generated invalid XML file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.2-beta-1-11-g7e13bdf
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-core". The branch, master has been updated via 7e13bdf929ca49cf18901669e2d5726bed7fe95e (commit) from 1501bb0cfaf258737417b08f1c86296f02edff84 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 7e13bdf929ca49cf18901669e2d5726bed7fe95e Author: Mauro Talevi Date: Thu Dec 2 15:44:31 2010 +0100 JBEHAVE-397: Applied patch https://github.com/dgodfrey/jbehave-core/commit/1995395cd42ab1c91027af631ab81cde909e4dfa. --- Summary of changes: .../org/jbehave/core/embedder/StoryRunner.java |6 -- 1 files changed, 4 insertions(+), 2 deletions(-) hooks/post-receive -- jbehave-core To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-397) Failure to execute all scenarios within a story.
[ http://jira.codehaus.org/browse/JBEHAVE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-397. -- Resolution: Fixed Patch applied. > Failure to execute all scenarios within a story. > > > Key: JBEHAVE-397 > URL: http://jira.codehaus.org/browse/JBEHAVE-397 > Project: JBehave > Issue Type: Bug > Components: Core >Reporter: Daniel Godfrey > Fix For: 3.2 > > > Given a story with 2 scenarios, the 2nd of which has GivenStores, if the > first scenario fails, the second scenario will not execute fully, execution > will finish when it's first GivenStory finishes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-401) XML Scenario reporter doesn't always include a closing story xml tag
[ http://jira.codehaus.org/browse/JBEHAVE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-401. -- Resolution: Duplicate Duplicate of JBEHAVE-397. > XML Scenario reporter doesn't always include a closing story xml tag > > > Key: JBEHAVE-401 > URL: http://jira.codehaus.org/browse/JBEHAVE-401 > Project: JBehave > Issue Type: Bug > Components: Core >Affects Versions: 3.1.2 > Environment: Windows 7 and Linux x86 >Reporter: Alan Parkinson > Fix For: 3.2 > > Attachments: > org.jbehave.examples.trader.stories.failure_followed_by_given_stories.xml > > > When running the trader example, the story > org/jbehave/examples/trader/stories/failure_followed_by_given_stories.story > generates an invalid XML file by not including a final closing "story" tag. > Attached is the generated invalid XML file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] 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=246177#action_246177 ] Mauro Talevi commented on JBEHAVE-394: -- Hi Alan, if you are happy to contribute the plugin the JBehave project we can include it 3.2 release. > 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
