[jbehave-dev] [jira] Resolved: (JBEHAVE-71) Our build script appears to be running some behaviours three times each.
[ http://jira.codehaus.org/browse/JBEHAVE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh resolved JBEHAVE-71. Resolution: Fixed Ant tasks now use filesets. Our build script appears to be running some behaviours three times each. Key: JBEHAVE-71 URL: http://jira.codehaus.org/browse/JBEHAVE-71 Project: JBehave Issue Type: Bug Components: Build system Reporter: Elizabeth Keogh Fix For: 0.9 Are we picking up some AllBehaviours as well as the Behaviours themselves somewhere? -- 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-19) broken links....
[ http://jira.codehaus.org/browse/JBEHAVE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh updated JBEHAVE-19: --- Affects Version/s: 1.0 Fix Version/s: (was: 0.9) 1.0 Website has been updated, but there are still some broken links. broken links Key: JBEHAVE-19 URL: http://jira.codehaus.org/browse/JBEHAVE-19 Project: JBehave Issue Type: Bug Components: Website Affects Versions: 1.0 Reporter: Robert Dawson Fix For: 1.0 http://jbehave.codehaus.org/development.html has a couple of broken links. These are to: http://jbehave.codehaus.org/architecture.html, and http://builds.codehaus.org/log/jbehave/ -- 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] Closed: (JBEHAVE-54) Story runner Ant task
[ http://jira.codehaus.org/browse/JBEHAVE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-54. -- Resolution: Fixed Done. Story runner Ant task - Key: JBEHAVE-54 URL: http://jira.codehaus.org/browse/JBEHAVE-54 Project: JBehave Issue Type: New Feature Components: Ant extension Reporter: Matt Savage Assigned To: Mauro Talevi Fix For: 1.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Closed: (JBEHAVE-48) jBehave WebSite needs a facelifting
[ http://jira.codehaus.org/browse/JBEHAVE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-48. -- Resolution: Fixed It got a facelifting. Using webdav to upload and WordPress to generate now. jBehave WebSite needs a facelifting --- Key: JBEHAVE-48 URL: http://jira.codehaus.org/browse/JBEHAVE-48 Project: JBehave Issue Type: Improvement Components: Website Reporter: Shane Duan Assigned To: Shane Duan Fix For: 1.0 Need to update jBehave website using the template engine from BuildMaster for easy website updating -- 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-15) JBehave needs an Eclipse Plugin
[ http://jira.codehaus.org/browse/JBEHAVE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh updated JBEHAVE-15: --- Fix Version/s: (was: 1.0) 1.1 JBehave needs an Eclipse Plugin --- Key: JBEHAVE-15 URL: http://jira.codehaus.org/browse/JBEHAVE-15 Project: JBehave Issue Type: New Feature Components: Eclipse plugin Reporter: Dan North Fix For: The Distant Future Probably besed very closely on the JUnit plugin code, if not a simple extension to the JUnit plugin itself. You can use the existing JUnit plugin with the JUnit Adapter, but it only gives you basic functionality. You can't double-click on a responsibility name in the plugin and navigate to the actual method, for instance. Also, searching for behaviour classes would be nice (anything ending in Behaviour or containing a public void should...() method?) -- 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-15) JBehave needs an Eclipse Plugin
[ http://jira.codehaus.org/browse/JBEHAVE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh updated JBEHAVE-15: --- Fix Version/s: (was: 1.1) The Distant Future JBehave needs an Eclipse Plugin --- Key: JBEHAVE-15 URL: http://jira.codehaus.org/browse/JBEHAVE-15 Project: JBehave Issue Type: New Feature Components: Eclipse plugin Reporter: Dan North Fix For: The Distant Future Probably besed very closely on the JUnit plugin code, if not a simple extension to the JUnit plugin itself. You can use the existing JUnit plugin with the JUnit Adapter, but it only gives you basic functionality. You can't double-click on a responsibility name in the plugin and navigate to the actual method, for instance. Also, searching for behaviour classes would be nice (anything ending in Behaviour or containing a public void should...() method?) -- 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] Closed: (JBEHAVE-68) JBehave should have no dependencies - remove Cotta
[ http://jira.codehaus.org/browse/JBEHAVE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-68. -- Resolution: Fixed Done. JBehave should have no dependencies - remove Cotta -- Key: JBEHAVE-68 URL: http://jira.codehaus.org/browse/JBEHAVE-68 Project: JBehave Issue Type: Task Reporter: Elizabeth Keogh Fix For: 1.0 We should take the functionality we need and put it into JBehave's namespace. Shane has asked that make it easy for any changes we need to that functionality to be mirrored in Cotta (ie: keep the package structure and class names the same if we can). -- 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] Closed: (JBEHAVE-76) Scenarios do not need a description.
[ http://jira.codehaus.org/browse/JBEHAVE-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-76. -- Resolution: Fixed The description is now taken from the class name. Scenarios do not need a description. Key: JBEHAVE-76 URL: http://jira.codehaus.org/browse/JBEHAVE-76 Project: JBehave Issue Type: Improvement Components: Core Reporter: Elizabeth Keogh Fix For: 1.0 Constructing scenarios has become more complex than originally envisioned, and they're also being used in GivenScenarios. Because of this they tend to extend ScenarioUsingMiniMock, rather than merely being an instance of it. Therefore, they don't need a description. This may require some changes to the StoryPrinter, or whatever else uses the Scenario's description. -- 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] Closed: (JBEHAVE-78) We should be able to mock classes.
[ http://jira.codehaus.org/browse/JBEHAVE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-78. -- Resolution: Fixed We can mock classes. We should be able to mock classes. -- Key: JBEHAVE-78 URL: http://jira.codehaus.org/browse/JBEHAVE-78 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Assigned To: Elizabeth Keogh Fix For: 1.0 Currently JBehave throws an error if an attempt to mock a class, rather than an interface, is made. The ability to mock classes means that users don't have to create interfaces artificially. In many instances, where a default implementation of a class exists (eg: repositories, file handlers, etc.) there will only ever be one implementation outside of the behaviours. -- 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-55) FIT adapter
[ http://jira.codehaus.org/browse/JBEHAVE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh updated JBEHAVE-55: --- Affects Version/s: The Distant Future Fix Version/s: (was: 1.0) FIT adapter --- Key: JBEHAVE-55 URL: http://jira.codehaus.org/browse/JBEHAVE-55 Project: JBehave Issue Type: New Feature Components: Story runner Affects Versions: The Distant Future Reporter: Matt Savage - If I have existing FIT fixtures I would like to be able to use them from the story runner. In this case, JBehave would give me the structure of expressing requirements as GWT, but I would be able to easily wrap my current FIT test suite in JBehave stories. - In some cases, a FIT table fixture may be the most appropriate way to express the semantics of a given/when/then- I want to be able to choose to use this where appropriate. -- 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-55) FIT adapter
[ http://jira.codehaus.org/browse/JBEHAVE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh updated JBEHAVE-55: --- Affects Version/s: (was: The Distant Future) 0.9 Fix Version/s: The Distant Future FIT adapter --- Key: JBEHAVE-55 URL: http://jira.codehaus.org/browse/JBEHAVE-55 Project: JBehave Issue Type: New Feature Components: Story runner Affects Versions: 0.9 Reporter: Matt Savage Fix For: The Distant Future - If I have existing FIT fixtures I would like to be able to use them from the story runner. In this case, JBehave would give me the structure of expressing requirements as GWT, but I would be able to easily wrap my current FIT test suite in JBehave stories. - In some cases, a FIT table fixture may be the most appropriate way to express the semantics of a given/when/then- I want to be able to choose to use this where appropriate. -- 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] Closed: (JBEHAVE-42) JBehave Maven Plugin
[ http://jira.codehaus.org/browse/JBEHAVE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-42. -- Resolution: Fixed Maven plugin is in. JBehave Maven Plugin Key: JBEHAVE-42 URL: http://jira.codehaus.org/browse/JBEHAVE-42 Project: JBehave Issue Type: New Feature Components: Maven Plugin Reporter: Shane Duan Assigned To: Mauro Talevi Fix For: 1.0 As a JBehave user, I would like to be able to type mvn jbehave and verify all the behaviours of the system. -- 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-80) I can't use enums as World keys.
I can't use enums as World keys. Key: JBEHAVE-80 URL: http://jira.codehaus.org/browse/JBEHAVE-80 Project: JBehave Issue Type: Improvement Affects Versions: 1.0 Reporter: Elizabeth Keogh Priority: Critical Fix For: 1.1 Can't think of any reason why we're only allowing Strings as World keys. This is madness, I tell you! Madness! -- 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
