[jbehave-dev] [jira] Created: (JBEHAVE-236) Checking out, building and testing JBehave from scratch
Checking out, building and testing JBehave from scratch --- Key: JBEHAVE-236 URL: http://jira.codehaus.org/browse/JBEHAVE-236 Project: JBehave Issue Type: New Feature Components: Documentation Affects Versions: 2.4 Reporter: Elizabeth Keogh Hi Mauro, The Maven build has completely superseded the Ant build, which is now very broken. This is fair, since you've done all the work lately - thanks! Could you please put a small amount of documentation out to show how to build JBehave from check-out, for those of us who don't know Maven? The learning curve has been off-putting even for those of us who care a lot ;) Cheers, Liz. -- 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-214) Allow for multiple aliases for a given step
Allow for multiple aliases for a given step --- Key: JBEHAVE-214 URL: http://jira.codehaus.org/browse/JBEHAVE-214 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Fix For: 2.4 I've got a machine which outputs messages. I've found three different ways of expressing that in steps: Then the machine should tell me that $message Then the machine should tell me to $message Then the machine should say $message I'd like to be able to put more than one alias on a step. (@Aliases ?) -- 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-126) GivenScenarios
[ http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160629#action_160629 ] Elizabeth Keogh commented on JBEHAVE-126: - GivenStory doesn't make any sense to me. I'm starting to think that Story, being another BDD domain term, should be a completely separate object from Scenario (and the various types of Scenario). It might have Scenarios as part of it. To run a GivenScenario, we might want to identify which Scenario in the Story is being run. Running all the Scenarios in a story to set up the context for anther Scenario makes no sense to me. Each Scenario could well leave the application in a different state, so what context would you set up in the Given? What state would you have, in which to perform the other steps? No idea how Story as a separate object would work, but it feels like the right thing to do. Thoughts? 3.0 maybe? GivenScenarios -- Key: JBEHAVE-126 URL: http://jira.codehaus.org/browse/JBEHAVE-126 Project: JBehave Issue Type: New Feature Components: Core Reporter: Elizabeth Keogh Assignee: Mauro Talevi Fix For: 2.2 As someone writing scenarios, I want to be able to use another scenario as a Given, so that I don't have to write big long scenarios. Not sure how this would work - at the moment we can get around it on the code side. I'm guessing we're looking for something like Given the glider where the_glider is a scenario file. (What would we do if the_glider had two scenarios in it? Throw an exception, maybe?) -- 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-113) Sort out the website
[ http://jira.codehaus.org/browse/JBEHAVE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-113. --- Resolution: Fixed Good enough for now! Can add more docs as we find out what people most need. Sort out the website Key: JBEHAVE-113 URL: http://jira.codehaus.org/browse/JBEHAVE-113 Project: JBehave Issue Type: New Feature Components: Website Reporter: Elizabeth Keogh Fix For: 2.0 for JBehave 2.0 - examples - full documentation - download links 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] Created: (JBEHAVE-130) Other examples include
Other examples include -- Key: JBEHAVE-130 URL: http://jira.codehaus.org/browse/JBEHAVE-130 Project: JBehave Issue Type: New Feature Affects Versions: 2.0 Reporter: Elizabeth Keogh Assignee: Elizabeth Keogh Fix For: 2.1 Antony and other Fitnesse / Concordion users would like something along these lines: Given a user Fred Bloggs with username fbloggs and password Pa55word When fbloggs logs in with password Pa55word Then the page should say Welcome, Fred Bloggs! Other examples include: name | username | password | attempted | message -- Jane Brown | jbrown| F*bble | F*bble | Welcome, Jane Brown Terri Smith | tsmith | W*bble | w*bble | Incorrect username or password Terri Smith | tsmith | W*bble | W*bble | Welcome, Terri Smith Fred Bloggs | fbloggs | Pa55word | Password | Incorrect username or password where the table headings are the same as the parameters in the various steps. -- Reckon this could be done, either by using paranamer or by catching the parameter names in the steps (which we don't do at the moment). Shouldn't be too hard. Will look at it over the weekend. -- 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-131) Aliases for steps
Aliases for steps - Key: JBEHAVE-131 URL: http://jira.codehaus.org/browse/JBEHAVE-131 Project: JBehave Issue Type: New Feature Affects Versions: 2.0 Reporter: Elizabeth Keogh Fix For: 2.1 We would like to be able to introduce aliases for steps, eg: @Given(a $width x $height grid) @Aliases(a grid of $width by $height, a $width by $height grid) ... -- 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-128) Candidate step should support generic parameter conversion
[ http://jira.codehaus.org/browse/JBEHAVE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-128. --- Resolution: Fixed Works for me :) Candidate step should support generic parameter conversion -- Key: JBEHAVE-128 URL: http://jira.codehaus.org/browse/JBEHAVE-128 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 2.0 It is quite common to have step parameters which are CSV of strings or numbers. The candidate step should support them as it does with strings and numbers. More in general, it should generic and injectable parameter converters that allow users to convert objects from a string representations that make sense in the scenario domain. -- 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-125) Custom converters
[ http://jira.codehaus.org/browse/JBEHAVE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-125. --- Resolution: Fixed Fix Version/s: 2.0 Custom converters - Key: JBEHAVE-125 URL: http://jira.codehaus.org/browse/JBEHAVE-125 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Fix For: 2.0 As a developer, I want to provide converters for my scenarios so that I can convert from a String to anything that can be represented as a String (eg: a Grid, an Image, 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] Resolved: (JBEHAVE-79) Localisation
[ http://jira.codehaus.org/browse/JBEHAVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh resolved JBEHAVE-79. Resolution: Fixed ...and we're done. Localisation Key: JBEHAVE-79 URL: http://jira.codehaus.org/browse/JBEHAVE-79 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Assignee: Elizabeth Keogh Fix For: 2.0 As proposed by Alexandre Martins, localisation of Narrative would be useful for use with non-english languages. Eg, the narrative in portuguese would be: Como um [papel] Eu quero [função] De forma que [benefício] Both the story codegen and the renderer would need to support a Localiser component that know how to translate the keywords in the different locales. -- 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-108) Story narratives
[ http://jira.codehaus.org/browse/JBEHAVE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-108. --- Resolution: Fixed Introduced StoryDefinition and ScenarioDefinition Story narratives Key: JBEHAVE-108 URL: http://jira.codehaus.org/browse/JBEHAVE-108 Project: JBehave Issue Type: New Feature Components: Core Reporter: Elizabeth Keogh Fix For: 2.0 Given a story file with several scenarios Given the story has a narrative When I output the scenarios Then I should see the narrative -- 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-79) Localisation
[ http://jira.codehaus.org/browse/JBEHAVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh reopened JBEHAVE-79: Assignee: Elizabeth Keogh Regressed this while sorting out the Story / Scenario - will put it back with some examples! Localisation Key: JBEHAVE-79 URL: http://jira.codehaus.org/browse/JBEHAVE-79 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Assignee: Elizabeth Keogh Fix For: 2.0 As proposed by Alexandre Martins, localisation of Narrative would be useful for use with non-english languages. Eg, the narrative in portuguese would be: Como um [papel] Eu quero [função] De forma que [benefício] Both the story codegen and the renderer would need to support a Localiser component that know how to translate the keywords in the different locales. -- 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-106) Should be able to have multiple scenarios in a story
[ http://jira.codehaus.org/browse/JBEHAVE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-106. --- Resolution: Fixed Done - use Scenario: Title steps Scenario: Title steps Should be able to have multiple scenarios in a story Key: JBEHAVE-106 URL: http://jira.codehaus.org/browse/JBEHAVE-106 Project: JBehave Issue Type: New Feature Components: Core Reporter: Elizabeth Keogh Fix For: 2.0 Should be able to detect multiple scenarios in a story file (split on the first Given?) -- 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-111) Only output broken scenarios
[ http://jira.codehaus.org/browse/JBEHAVE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-111. --- Resolution: Fixed Can configure output of all scenarios with system property org.jbehave.outputall Only output broken scenarios Key: JBEHAVE-111 URL: http://jira.codehaus.org/browse/JBEHAVE-111 Project: JBehave Issue Type: New Feature Components: Core Reporter: Elizabeth Keogh Assignee: Elizabeth Keogh Fix For: 2.0 Given I have many scenarios, some of which are broken Given I choose not to output working scenarios When I run the build Then I should only see the output from broken scenarios -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Closed: (JBEHAVE-112) Output pending scenarios as well as broken when option to break build on pending is selected
[ http://jira.codehaus.org/browse/JBEHAVE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-112. --- Resolution: Fixed I'm outputting all scenarios that require attention by default; feedback suggests this is most useful and holistic option. Output pending scenarios as well as broken when option to break build on pending is selected Key: JBEHAVE-112 URL: http://jira.codehaus.org/browse/JBEHAVE-112 Project: JBehave Issue Type: New Feature Components: Core Reporter: Elizabeth Keogh Assignee: Elizabeth Keogh Fix For: 2.0 Given I have chosen to break the build on pending scenarios Given I have several scenarios, some of which are pending When I run the build Then I should see the pending scenarios in the output -- 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-110) Pending steps optionally break the build
[ http://jira.codehaus.org/browse/JBEHAVE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-110. --- Resolution: Fixed Can be done either by specifying the strategy as part of the configuration, or by setting the System property -Dorg.jbehave.failonpending to something non-null. Pending steps optionally break the build Key: JBEHAVE-110 URL: http://jira.codehaus.org/browse/JBEHAVE-110 Project: JBehave Issue Type: New Feature Components: Core Reporter: Elizabeth Keogh Assignee: Elizabeth Keogh Fix For: 2.0 Given a scenario with pending steps Given I choose to break the build on pending steps When I run the scenario Then my build should break -- 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-124) Eclipse can't find the test to run when it's in JBehave's jar
[ http://jira.codehaus.org/browse/JBEHAVE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-124. --- Resolution: Fixed Making the source available. Alternative is for projects suffering this problem to create their own extension of the Scenario class and delegate the test method. Eclipse can't find the test to run when it's in JBehave's jar - Key: JBEHAVE-124 URL: http://jira.codehaus.org/browse/JBEHAVE-124 Project: JBehave Issue Type: Improvement Reporter: Elizabeth Keogh Fix For: 2.0 This works fine when we have the source available. Is there a way of including the source for Scenario in the jar, to get Eclipse to notice that there really is a test? -- 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-127) Doesn't find scenarios with numbers in the title
Doesn't find scenarios with numbers in the title Key: JBEHAVE-127 URL: http://jira.codehaus.org/browse/JBEHAVE-127 Project: JBehave Issue Type: Bug Reporter: Elizabeth Keogh cells_with_3_neighbours_are_born - CellsWith3NeighboursAreBorn, throws ScenarioNotFoundException cells_with3_neighbours_are_born works OK, but should be able to do either. -- 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-123) JBehave configuration classes
[ http://jira.codehaus.org/browse/JBEHAVE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-123. --- Resolution: Fixed Andy Palmer and I paired on this; introduced the Technique class. JBehave configuration classes - Key: JBEHAVE-123 URL: http://jira.codehaus.org/browse/JBEHAVE-123 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Assignee: Elizabeth Keogh Fix For: 2.0 I'm starting to find that there are multiple different things I might want to do, and the dependency injection mechanism isn't really working as well as I'd like for this. It would be nice to produce a configuration that's easy to set up, and use that for everything. We could then have different ways of configuring JBehave, eg: environment-driven, settable, null (so you have to specify everything yourself), etc. Going to have a play with this, driving it using the broken scenarios only. BTW, every time I get a broken scenario or error output story, I'm driving it by actually breaking a story. You won't see these broken stories checked into the build, but it's easy enough to replicate yourself! -- 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-124) Eclipse can't find the test to run when it's in JBehave's jar
Eclipse can't find the test to run when it's in JBehave's jar - Key: JBEHAVE-124 URL: http://jira.codehaus.org/browse/JBEHAVE-124 Project: JBehave Issue Type: Improvement Reporter: Elizabeth Keogh Fix For: 2.0 This works fine when we have the source available. Is there a way of including the source for Scenario in the jar, to get Eclipse to notice that there really is a test? -- 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-126) GivenScenarios
GivenScenarios -- Key: JBEHAVE-126 URL: http://jira.codehaus.org/browse/JBEHAVE-126 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh As someone writing scenarios, I want to be able to use another scenario as a Given, so that I don't have to write big long scenarios. Not sure how this would work - at the moment we can get around it on the code side. I'm guessing we're looking for something like Given the glider where the_glider is a scenario file. (What would we do if the_glider had two scenarios in it? Throw an exception, maybe?) -- 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-123) JBehave configuration classes
JBehave configuration classes - Key: JBEHAVE-123 URL: http://jira.codehaus.org/browse/JBEHAVE-123 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Fix For: 2.0 I'm starting to find that there are multiple different things I might want to do, and the dependency injection mechanism isn't really working as well as I'd like for this. It would be nice to produce a configuration that's easy to set up, and use that for everything. We could then have different ways of configuring JBehave, eg: environment-driven, settable, null (so you have to specify everything yourself), etc. Going to have a play with this, driving it using the broken scenarios only. BTW, every time I get a broken scenario or error output story, I'm driving it by actually breaking a story. You won't see these broken stories checked into the build, but it's easy enough to replicate yourself! -- 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-117) Should throw an exception if two candidate step methods have the same annotation
Should throw an exception if two candidate step methods have the same annotation Key: JBEHAVE-117 URL: http://jira.codehaus.org/browse/JBEHAVE-117 Project: JBehave Issue Type: Bug Reporter: Elizabeth Keogh -- 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-118) Check that punctuation after args doesn't stop it working
Check that punctuation after args doesn't stop it working - Key: JBEHAVE-118 URL: http://jira.codehaus.org/browse/JBEHAVE-118 Project: JBehave Issue Type: Task Reporter: Elizabeth Keogh -- 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-104) Support 'And' after Given, When or Then
[ http://jira.codehaus.org/browse/JBEHAVE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-104. --- Resolution: Fixed This was easy to do once localisation and specifying your own starting words was in place Support 'And' after Given, When or Then --- Key: JBEHAVE-104 URL: http://jira.codehaus.org/browse/JBEHAVE-104 Project: JBehave Issue Type: New Feature Components: Core Reporter: Elizabeth Keogh Should be able to do: Given a context And another context When an event And another event Then an outcome And another outcome -- 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-79) Localisation
[ http://jira.codehaus.org/browse/JBEHAVE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-79. -- Resolution: Fixed Now injecting all starting words (Given, When, Then, And) - which means you can choose your own. Localisation Key: JBEHAVE-79 URL: http://jira.codehaus.org/browse/JBEHAVE-79 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Fix For: 2.0 As proposed by Alexandre Martins, localisation of Narrative would be useful for use with non-english languages. Eg, the narrative in portuguese would be: Como um [papel] Eu quero [função] De forma que [benefício] Both the story codegen and the renderer would need to support a Localiser component that know how to translate the keywords in the different locales. -- 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-114) Build isn't running the scenarios
[ http://jira.codehaus.org/browse/JBEHAVE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-114. --- Resolution: Fixed Fixed. Build isn't running the scenarios - Key: JBEHAVE-114 URL: http://jira.codehaus.org/browse/JBEHAVE-114 Project: JBehave Issue Type: Bug Components: Build system Reporter: Elizabeth Keogh Fix For: 2.0 Ryan has sent me a patch for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Closed: (JBEHAVE-105) Should not require a space before a new line
[ http://jira.codehaus.org/browse/JBEHAVE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-105. --- Resolution: Fixed Fixed. Should not require a space before a new line Key: JBEHAVE-105 URL: http://jira.codehaus.org/browse/JBEHAVE-105 Project: JBehave Issue Type: Bug Components: Core Reporter: Elizabeth Keogh Fix For: 2.0 Currently I have a space after the 'When' line in multiline steps. eg: Given a grid that looks like -- there's a space after this line Should be able to work without the space. -- 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-115) Undoable steps
Undoable steps -- Key: JBEHAVE-115 URL: http://jira.codehaus.org/browse/JBEHAVE-115 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Fix For: The Distant Future Sometimes when we set up a context or cause an event to happen, it's nice to clean up any changes so that we don't affect other tests running. No idea how to make the undoable work, but doesn't stop me wanting it! -- 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-66) JBehave is not running its build in Codehaus's automated builds.
[ http://jira.codehaus.org/browse/JBEHAVE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-66. -- Resolution: Fixed We managed without automated builds the entirety of JBehave 1. JBehave is not running its build in Codehaus's automated builds. Key: JBEHAVE-66 URL: http://jira.codehaus.org/browse/JBEHAVE-66 Project: JBehave Issue Type: Wish Components: Build system Reporter: Elizabeth Keogh -- 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-35) Ant task documentation is out of date.
[ http://jira.codehaus.org/browse/JBEHAVE-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-35. -- Resolution: Fixed Redundant - JBehave 2.0 uses JUnit and can use the same tasks Ant task documentation is out of date. -- Key: JBEHAVE-35 URL: http://jira.codehaus.org/browse/JBEHAVE-35 Project: JBehave Issue Type: Improvement Components: Ant extension Environment: All Reporter: Elizabeth Keogh Assignee: Shane Duan Priority: Minor Original Estimate: 2 minutes Remaining Estimate: 2 minutes Ant task javadocs talk about specs instead of behaviour classes. The given example doesn't work. -- 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-37) Eclipse plugin - right-click and run behaviour method
[ http://jira.codehaus.org/browse/JBEHAVE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-37. -- Resolution: Fixed Can use JUnit's plugins for 2.0 Eclipse plugin - right-click and run behaviour method - Key: JBEHAVE-37 URL: http://jira.codehaus.org/browse/JBEHAVE-37 Project: JBehave Issue Type: Sub-task Components: Eclipse plugin Reporter: Elizabeth Keogh As a developer, I want to be able to quickly run a JBehave behaviour method so that I can quickly check that the code described by the behaviour ain't misbehaving. See JUnitRunner's plugin for an example. When you right-click on a piece of code, you get a Run as option which allows you to run a single method in the JUnit test case. If the cursor is between methods, the entire test case is run. I'd like to see a similar thing for 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-46) MiniMock should fail unpon unmatched calls
[ http://jira.codehaus.org/browse/JBEHAVE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-46. -- Resolution: Fixed No minimock in 2.0 - use Mockito instead MiniMock should fail unpon unmatched calls -- Key: JBEHAVE-46 URL: http://jira.codehaus.org/browse/JBEHAVE-46 Project: JBehave Issue Type: Improvement Components: Core Reporter: Shane Duan The minimock should fail immediately when unspecified call comes in, instead of waiting for verification -- 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-75) F3 / ctrl-MouseClick through to class file matching Story component (Felix)
[ http://jira.codehaus.org/browse/JBEHAVE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-75. -- Resolution: Fixed 2.0 extends JUnit, can use their plugins - thanks Felix for all the help! F3 / ctrl-MouseClick through to class file matching Story component (Felix) --- Key: JBEHAVE-75 URL: http://jira.codehaus.org/browse/JBEHAVE-75 Project: JBehave Issue Type: New Feature Components: Eclipse plugin Reporter: Elizabeth Keogh Assignee: Elizabeth Keogh (Worked by Felix, not Liz) Felix has a really nifty tool which allows you to put the mouse on a line of story text, press F3 and it takes you to the class file matching that text. He promises a ctrl-mouse-click some time. -- 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-15) JBehave Eclipse Plugin
[ http://jira.codehaus.org/browse/JBEHAVE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-15. -- Resolution: Fixed 2.0 extends JUnit, can use their plugins - thanks Felix for all the help! JBehave 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 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-52) Have a way to register a setup and a teardown that will be invoked before and after EACH method
[ http://jira.codehaus.org/browse/JBEHAVE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-52. -- Resolution: Fixed Extending JUnit which supports this already as part of 2.0 Have a way to register a setup and a teardown that will be invoked before and after EACH method --- Key: JBEHAVE-52 URL: http://jira.codehaus.org/browse/JBEHAVE-52 Project: JBehave Issue Type: New Feature Components: Core Reporter: Shane Duan You probably would not need this in an ideal enviornment. But in the case where you want to make sure that everyone on the team is cleaning up after themselves (deleting the test data from database, cleaning up the files, etc), it is something that can save days of work. An enhanced version would be to allow dependency injection into each behaviour class so that it won't have to use singleton on certain case (like database connection). Yes I konw you are not supposed to do database connection tests, but in order to fix the existing tests a feature like this would come in very handy. -- 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-39) Eclipse plugin - run behaviours in own window with red / green bar
[ http://jira.codehaus.org/browse/JBEHAVE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-39. -- Resolution: Fixed 2.0 extends JUnit, can use their plugins - thanks Felix for all the help! Eclipse plugin - run behaviours in own window with red / green bar -- Key: JBEHAVE-39 URL: http://jira.codehaus.org/browse/JBEHAVE-39 Project: JBehave Issue Type: Sub-task Components: Eclipse plugin Reporter: Elizabeth Keogh Priority: Minor Again, see JUnit for an example of this. I would like to see a JBehave icon appear with its own graphical window in which pass or fail is shown by a green or red bar. -- 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-11) Example codebase for JMock extension
[ http://jira.codehaus.org/browse/JBEHAVE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-11. -- Resolution: Fixed No mocks in 2.0 - we recommend you use Mockito instead Example codebase for JMock extension Key: JBEHAVE-11 URL: http://jira.codehaus.org/browse/JBEHAVE-11 Project: JBehave Issue Type: New Feature Components: JMock extension Reporter: Dan North Assignee: Manish Shah Create example codebase under extensions/jmock/example using UsingJMock, 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] Closed: (JBEHAVE-58) Roundtrip story editor in Eclipse
[ http://jira.codehaus.org/browse/JBEHAVE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-58. -- Resolution: Fixed Using plain-text scenarios to generate flow now, so we have round-tripness out of the box Roundtrip story editor in Eclipse - Key: JBEHAVE-58 URL: http://jira.codehaus.org/browse/JBEHAVE-58 Project: JBehave Issue Type: Wish Components: Story runner Reporter: Matt Savage Priority: Minor Use Ozgur Turner's BNF plugin for Eclipse. -- 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-40) Eclipse plugin - run window displays failed behaviours
[ http://jira.codehaus.org/browse/JBEHAVE-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-40. -- Resolution: Fixed 2.0 extends JUnit, can use their plugins - thanks Felix for all the help! Eclipse plugin - run window displays failed behaviours -- Key: JBEHAVE-40 URL: http://jira.codehaus.org/browse/JBEHAVE-40 Project: JBehave Issue Type: Sub-task Components: Eclipse plugin Reporter: Elizabeth Keogh Priority: Minor As a developer, I want JBehave to show me which behaviours aren't behaving by listing them in the window which shows the red / green bar, so that I can easily diagnose and / or fix the code. See JUnit for an example. I want to click on a failed behaviour in the failed behaviour list and see a stack trace or failure message beneath the failed behaviour. I also want the stack trace of the error to be hyperlinked to the behaviour which produced it. -- 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-12) Example codebase for JUnit extension
[ http://jira.codehaus.org/browse/JBEHAVE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-12. -- Resolution: Fixed Extending JUnit anyway Example codebase for JUnit extension Key: JBEHAVE-12 URL: http://jira.codehaus.org/browse/JBEHAVE-12 Project: JBehave Issue Type: New Feature Components: JUnit extension Reporter: Dan North Create codebase under extensions/junit/example -- 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-38) Eclipse plugin - right-click and run story
[ http://jira.codehaus.org/browse/JBEHAVE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-38. -- Resolution: Fixed 2.0 extends JUnit, can use their plugins - thanks Felix for all the help! Eclipse plugin - right-click and run story -- Key: JBEHAVE-38 URL: http://jira.codehaus.org/browse/JBEHAVE-38 Project: JBehave Issue Type: Sub-task Components: Eclipse plugin Reporter: Elizabeth Keogh Priority: Minor As a developer, I want to be able to quickly run a JBehave story class so that I can quickly check that the system described by the story ain't misbehaving. See JUnit's plugin for an example. When you right-click on a piece of code, you get a Run as option which allows you to run the code in the editor as a JUnit test case. I'd like to see the same thing for JBehave's story classes. The Run class which runs stories is different to the behaviour Run class. This would be the equivalent of running a functional test using Abbot or some such. This is less important IMHO than the behaviour runner, as it can take time to run the stories anyway, comparative to the more granular behaviour classes. -- 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-9) Document JUnitAdapter on website
[ http://jira.codehaus.org/browse/JBEHAVE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-9. - Resolution: Fixed No JUnit adapter in 2.0 Document JUnitAdapter on website Key: JBEHAVE-9 URL: http://jira.codehaus.org/browse/JBEHAVE-9 Project: JBehave Issue Type: Improvement Components: Website Reporter: Dan North Explain how to use it - especially Damian's excellent Eclipse hack that allows you to run the current behaviour class under the cursor. -- 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-51) JUnit to Behaviour test converter
[ http://jira.codehaus.org/browse/JBEHAVE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-51. -- Resolution: Fixed Extending JUnit in 2.0 JUnit to Behaviour test converter - Key: JBEHAVE-51 URL: http://jira.codehaus.org/browse/JBEHAVE-51 Project: JBehave Issue Type: New Feature Reporter: Mauro Talevi To facilitate the conversion of integration/acceptance tests that have been written as JUnit tests it would be useful to have converter. -- 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-55) FIT adapter
[ http://jira.codehaus.org/browse/JBEHAVE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=142305#action_142305 ] Elizabeth Keogh commented on JBEHAVE-55: Oh, and you can include your own parser - so you can use any format of file you like to drive the scenarios. Any further requirements after 2.0rc please reopen! 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 - 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] Created: (JBEHAVE-104) Support 'And' after Given, When or Then
Support 'And' after Given, When or Then --- Key: JBEHAVE-104 URL: http://jira.codehaus.org/browse/JBEHAVE-104 Project: JBehave Issue Type: New Feature Components: Core Reporter: Elizabeth Keogh Should be able to do: Given a context And another context When an event And another event Then an outcome And another outcome -- 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-105) Should not require a space before a new line
Should not require a space before a new line Key: JBEHAVE-105 URL: http://jira.codehaus.org/browse/JBEHAVE-105 Project: JBehave Issue Type: Bug Reporter: Elizabeth Keogh Currently I have a space after the 'When' line in multiline steps. eg: Given a grid that looks like -- there's a space after this line Should be able to work without the space. -- 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-108) Story narratives
Story narratives Key: JBEHAVE-108 URL: http://jira.codehaus.org/browse/JBEHAVE-108 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Given a story file with several scenarios Given the story has a narrative When I output the scenarios Then I should see the narrative -- 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-109) Story titles
Story titles Key: JBEHAVE-109 URL: http://jira.codehaus.org/browse/JBEHAVE-109 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Given a story with several scenarios Given the story has a title When I run the story Then I should see the title in the output -- 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-111) Only output broken scenarios
Only output broken scenarios Key: JBEHAVE-111 URL: http://jira.codehaus.org/browse/JBEHAVE-111 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Given I have many scenarios, some of which are broken Given I choose not to output working scenarios When I run the build Then I should only see the output from broken scenarios -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-112) Output pending scenarios as well as broken when option to break build on pending is selected
Output pending scenarios as well as broken when option to break build on pending is selected Key: JBEHAVE-112 URL: http://jira.codehaus.org/browse/JBEHAVE-112 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Given I have chosen to break the build on pending scenarios Given I have several scenarios, some of which are pending When I run the build Then I should see the pending scenarios in the output -- 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-113) Sort out the website
[ http://jira.codehaus.org/browse/JBEHAVE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh updated JBEHAVE-113: Fix Version/s: 2.0 Sort out the website Key: JBEHAVE-113 URL: http://jira.codehaus.org/browse/JBEHAVE-113 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Fix For: 2.0 for JBehave 2.0 - examples - full documentation - download links - 2.0rc download 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] Closed: (JBEHAVE-56) Add examples to documentation
[ http://jira.codehaus.org/browse/JBEHAVE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-56. -- Resolution: Duplicate Now contained within the whole 'update the website' task Add examples to documentation - Key: JBEHAVE-56 URL: http://jira.codehaus.org/browse/JBEHAVE-56 Project: JBehave Issue Type: New Feature Components: Website Reporter: Matt Savage -- 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-103) issue
[ http://jira.codehaus.org/browse/JBEHAVE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-103. --- Resolution: Incomplete Guessing this issue was created in error? If not, please attach a description - is not meaningful! Ta - Liz issue - Key: JBEHAVE-103 URL: http://jira.codehaus.org/browse/JBEHAVE-103 Project: JBehave Issue Type: Bug Affects Versions: 0.9 Reporter: amouche habiba Priority: Blocker -- 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-83) Stack trace overflow when UsingMatchers.either(...)
Stack trace overflow when UsingMatchers.either(...) --- Key: JBEHAVE-83 URL: http://jira.codehaus.org/browse/JBEHAVE-83 Project: JBehave Issue Type: Bug Affects Versions: 1.0 Reporter: Elizabeth Keogh Priority: Critical Fix For: 1.1 UsingMatchers.either(...) was calling UsingMatchers.either(...) instead of UsingMatchers.or(...) Doh! -- 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-83) Stack trace overflow when UsingMatchers.either(...)
[ http://jira.codehaus.org/browse/JBEHAVE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-83. -- Assignee: Elizabeth Keogh Resolution: Fixed Fixed. Stack trace overflow when UsingMatchers.either(...) --- Key: JBEHAVE-83 URL: http://jira.codehaus.org/browse/JBEHAVE-83 Project: JBehave Issue Type: Bug Affects Versions: 1.0 Reporter: Elizabeth Keogh Assigned To: Elizabeth Keogh Priority: Critical Fix For: 1.1 UsingMatchers.either(...) was calling UsingMatchers.either(...) instead of UsingMatchers.or(...) Doh! -- 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-84) UsingMatchers.nothing()
UsingMatchers.nothing() --- Key: JBEHAVE-84 URL: http://jira.codehaus.org/browse/JBEHAVE-84 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh This should ensure that you can explicitly stub a method with no arguments, when there exists a method of the same name which takes arguments. -- 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-84) UsingMatchers.nothing()
[ http://jira.codehaus.org/browse/JBEHAVE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-84. -- Assignee: Elizabeth Keogh Resolution: Fixed Fix Version/s: 1.1 Done. UsingMatchers.nothing() --- Key: JBEHAVE-84 URL: http://jira.codehaus.org/browse/JBEHAVE-84 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Assigned To: Elizabeth Keogh Fix For: 1.1 This should ensure that you can explicitly stub a method with no arguments, when there exists a method of the same name which takes arguments. -- 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-82) Behaviour plugin produces multiple launches for the same behaviour.
[ http://jira.codehaus.org/browse/JBEHAVE-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh updated JBEHAVE-82: --- Fix Version/s: (was: 1.1) 1.2 Behaviour plugin produces multiple launches for the same behaviour. --- Key: JBEHAVE-82 URL: http://jira.codehaus.org/browse/JBEHAVE-82 Project: JBehave Issue Type: Bug Components: Eclipse plugin Affects Versions: 1.0 Reporter: Elizabeth Keogh Fix For: 1.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] Closed: (JBEHAVE-85) CustomWorld for those people who want to define their own World accessors
[ http://jira.codehaus.org/browse/JBEHAVE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elizabeth Keogh closed JBEHAVE-85. -- Resolution: Fixed Fix Version/s: (was: 1.2) 1.1 CustomWorld for those people who want to define their own World accessors - Key: JBEHAVE-85 URL: http://jira.codehaus.org/browse/JBEHAVE-85 Project: JBehave Issue Type: New Feature Affects Versions: 1.0 Reporter: Elizabeth Keogh Fix For: 1.1 See javadoc in the CustomWorld class -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Closed: (JBEHAVE-81) Scenario steps should throw Exception in their signature.
[
http://jira.codehaus.org/browse/JBEHAVE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elizabeth Keogh closed JBEHAVE-81.
--
Resolution: Fixed
Scenario steps throw Exception in their main perform-method.
They do _not_ throw Exception in their cleanUp. This is because cleanUp happens
in a finally {} clause, and you have to decide what you want to do with any
exception you throw.
Scenario steps should throw Exception in their signature.
-
Key: JBEHAVE-81
URL: http://jira.codehaus.org/browse/JBEHAVE-81
Project: JBehave
Issue Type: Improvement
Affects Versions: 1.0
Reporter: Elizabeth Keogh
Fix For: 1.1
For the same reason that should... methods should be able to throw an
exception, so should ScenarioSteps. This prevents me having to wrap code that
shouldn't be throwing exceptions anyway.
--
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-81) Scenario steps should throw Exception in their signature.
Scenario steps should throw Exception in their signature. - Key: JBEHAVE-81 URL: http://jira.codehaus.org/browse/JBEHAVE-81 Project: JBehave Issue Type: Improvement Affects Versions: 1.0 Reporter: Elizabeth Keogh Fix For: 1.1 For the same reason that should... methods should be able to throw an exception, so should ScenarioSteps. This prevents me having to wrap code that shouldn't be throwing exceptions anyway. -- 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-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
