[jbehave-dev] [jira] Updated: (JBEHAVE-140) new StepMonitor method - executingStep(..)

[ http://jira.codehaus.org/browse/JBEHAVE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-140: - Assignee: Mauro Talevi Affects Version/s: (was: 2.1) 2.0.1

[jbehave-dev] [jira] Updated: (JBEHAVE-141) StepsConfiguration - can it have a setMonitor(..) method please

[ http://jira.codehaus.org/browse/JBEHAVE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-141: - Assignee: Mauro Talevi Affects Version/s: 2.0 Fix Version/s: 2.1 > StepsConfigura

[jbehave-dev] [jira] Resolved: (JBEHAVE-141) StepsConfiguration - can it have a setMonitor(..) method please

[ http://jira.codehaus.org/browse/JBEHAVE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-141. -- Resolution: Fixed Added useMonitor(StepMonitor monitor) method. > StepsConfiguration - can it have

[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-136) Add Ant task integration

[ http://jira.codehaus.org/browse/JBEHAVE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149489#action_149489 ] maurotalevi edited comment on JBEHAVE-136 at 10/24/08 4:26 PM: Added

[jbehave-dev] [jira] Resolved: (JBEHAVE-136) Add Ant task integration

[ http://jira.codehaus.org/browse/JBEHAVE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-136. -- Resolution: Fixed Done > Add Ant task integration > > > Ke

[jbehave-dev] [jira] Resolved: (JBEHAVE-129) @BeforeScenario and @AfterScenario

[ http://jira.codehaus.org/browse/JBEHAVE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-129. -- Resolution: Fixed Closing as completed. > @BeforeScenario and @AfterScenario > --

[jbehave-dev] [jira] Created: (JBEHAVE-143) Improve documentation for scenario developers

Improve documentation for scenario developers -- Key: JBEHAVE-143 URL: http://jira.codehaus.org/browse/JBEHAVE-143 Project: JBehave Issue Type: Task Reporter: Mauro Talevi

[jbehave-dev] [jira] Updated: (JBEHAVE-131) Aliases for steps

[ http://jira.codehaus.org/browse/JBEHAVE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-131: - Fix Version/s: (was: 2.1) 2.2 Component/s: Core > Aliases for steps > ---

[jbehave-dev] [jira] Updated: (JBEHAVE-133) Add lightweight container support for steps

[ http://jira.codehaus.org/browse/JBEHAVE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-133: - Fix Version/s: (was: 2.1) 2.2 > Add lightweight container support for steps >

[jbehave-dev] [jira] Updated: (JBEHAVE-130) Other examples include

[ http://jira.codehaus.org/browse/JBEHAVE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-130: - Fix Version/s: (was: 2.1) 2.2 Component/s: Core > Other examples include

[jbehave-dev] [jira] Updated: (JBEHAVE-139) Convert ant build to use ivy for dependencies

[ http://jira.codehaus.org/browse/JBEHAVE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-139: - Affects Version/s: (was: 2.1) 2.0 Fix Version/s: 2.2 > Convert ant

[jbehave-dev] [jira] Resolved: (JBEHAVE-143) Improve documentation for scenario developers

[ http://jira.codehaus.org/browse/JBEHAVE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-143. -- Resolution: Fixed Updated distribution reference documentation - which we'll also make available vi

[jbehave-dev] [jira] Updated: (JBEHAVE-141) Allow mutability of StepsConfiguration instance

[ http://jira.codehaus.org/browse/JBEHAVE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-141: - Summary: Allow mutability of StepsConfiguration instance (was: StepsConfiguration - can it have a set

[jbehave-dev] [jira] Closed: (JBEHAVE-141) Allow mutability of StepsConfiguration instance

[ http://jira.codehaus.org/browse/JBEHAVE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi closed JBEHAVE-141. Added use methods for all of StepsConfiguration dependencies. They are called use methods to underline tha

[jbehave-dev] [jira] Assigned: (JBEHAVE-131) Aliases for steps

[ http://jira.codehaus.org/browse/JBEHAVE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-131: Assignee: Mauro Talevi > Aliases for steps > - > > Key: JBEHAVE-

[jbehave-dev] [jira] Work started: (JBEHAVE-131) Aliases for steps

[ http://jira.codehaus.org/browse/JBEHAVE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-131 started by Mauro Talevi. > Aliases for steps > - > > Key: JBEHAVE-131 > URL: http://jira.codehaus.org/brows

[jbehave-dev] [jira] Updated: (JBEHAVE-127) Doesn't find scenarios with numbers in the file name

[ http://jira.codehaus.org/browse/JBEHAVE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-127: - Affects Version/s: 2.1 2.0.1 2.0 > Doesn't find scenario

[jbehave-dev] [jira] Updated: (JBEHAVE-117) Should throw an exception if two candidate step methods have the same annotation

[ http://jira.codehaus.org/browse/JBEHAVE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-117: - Assignee: Mauro Talevi Affects Version/s: 2.1 2.0.1

[jbehave-dev] [jira] Resolved: (JBEHAVE-131) Aliases for steps

[ http://jira.codehaus.org/browse/JBEHAVE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-131. -- Resolution: Fixed Done - updated gameoflife and trader examples to use aliases. > Aliases for steps

[jbehave-dev] [jira] Resolved: (JBEHAVE-144) Ensure utility methods should be independent of unit-testing framework

[ http://jira.codehaus.org/browse/JBEHAVE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-144. -- Resolution: Fixed Done - snapshots deployed. Please test with JUnit3. > Ensure utility methods s

[jbehave-dev] [jira] Updated: (JBEHAVE-130) Other examples include

[ http://jira.codehaus.org/browse/JBEHAVE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-130: - Affects Version/s: (was: 2.0) > Other examples include > -- > >

[jbehave-dev] [jira] Updated: (JBEHAVE-126) GivenScenarios

[ http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-126: - Affects Version/s: (was: 2.0.1) (was: 2.1) (w

[jbehave-dev] [jira] Updated: (JBEHAVE-144) Ensure utility methods should be independent of unit-testing framework

[ http://jira.codehaus.org/browse/JBEHAVE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-144: - Assignee: Mauro Talevi Description: Refactor Ensure method to only depend on Hamcrest and n

[jbehave-dev] [jira] Updated: (JBEHAVE-126) GivenScenarios

[ http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-126: - Affects Version/s: 2.1 2.0.1 2.0 Fix Version/s: 2

[jbehave-dev] [jira] Resolved: (JBEHAVE-117) Should throw an exception if two candidate step methods have the same annotation

[ http://jira.codehaus.org/browse/JBEHAVE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-117. -- Resolution: Fixed Throws runtime DuplicateCandidateStepFoundException if duplicate found. > Should

[jbehave-dev] [jira] Updated: (JBEHAVE-127) Doesn't find scenarios with numbers in the file name

[ http://jira.codehaus.org/browse/JBEHAVE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-127: - Assignee: Mauro Talevi Fix Version/s: 2.2 Summary: Doesn't find scenarios with numbe

[jbehave-dev] [jira] Commented: (JBEHAVE-145) Unit-test runners should decorate Exceptions a bit more clearly

[ http://jira.codehaus.org/browse/JBEHAVE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152680#action_152680 ] Mauro Talevi commented on JBEHAVE-145: -- Paul - can you please provide an example or a patch det

[jbehave-dev] [jira] Resolved: (JBEHAVE-127) Doesn't find scenarios with numbers in the file name

[ http://jira.codehaus.org/browse/JBEHAVE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-127. -- Resolution: Fixed Done - snapshot deployed. > Doesn't find scenarios with numbers in the file name

[jbehave-dev] [jira] Updated: (JBEHAVE-145) Unit-test runners should decorate Exceptions a bit more clearly

[ http://jira.codehaus.org/browse/JBEHAVE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-145: - Fix Version/s: 2.2 Summary: Unit-test runners should decorate Exceptions a bit more clearly

[jbehave-dev] [jira] Commented: (JBEHAVE-27) Document best practices and suggested use cases

[ http://jira.codehaus.org/browse/JBEHAVE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152688#action_152688 ] Mauro Talevi commented on JBEHAVE-27: - Added page http://jbehave.org/documentation/best-practices

[jbehave-dev] [jira] Updated: (JBEHAVE-27) Document best practices and suggested use cases

[ http://jira.codehaus.org/browse/JBEHAVE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-27: Assignee: Mauro Talevi (was: Dan North) Description: Add page document the philosophy that dro

[jbehave-dev] [jira] Commented: (JBEHAVE-146) PendingErrorStrategy choices needs one more.

[ http://jira.codehaus.org/browse/JBEHAVE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153097#action_153097 ] Mauro Talevi commented on JBEHAVE-146: -- Paul - PASSING and SILENT are implementations of differ

[jbehave-dev] [jira] Commented: (JBEHAVE-146) PendingErrorStrategy choices needs one more.

[ http://jira.codehaus.org/browse/JBEHAVE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153166#action_153166 ] Mauro Talevi commented on JBEHAVE-146: -- That would be very welcome! :-) > PendingErrorStrategy

[jbehave-dev] [jira] Created: (JBEHAVE-147) Improve javadocs

Improve javadocs Key: JBEHAVE-147 URL: http://jira.codehaus.org/browse/JBEHAVE-147 Project: JBehave Issue Type: Task Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi

[jbehave-dev] [jira] Updated: (JBEHAVE-147) Improve javadocs

[ http://jira.codehaus.org/browse/JBEHAVE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-147: - Issue Type: Improvement (was: Task) > Improve javadocs > > > Key: JB

[jbehave-dev] [jira] Created: (JBEHAVE-148) Auto-generate steps from scenario template

Auto-generate steps from scenario template -- Key: JBEHAVE-148 URL: http://jira.codehaus.org/browse/JBEHAVE-148 Project: JBehave Issue Type: New Feature Components: Core Reporter:

[jbehave-dev] [jira] Updated: (JBEHAVE-27) Document best practices and suggested use cases

[ http://jira.codehaus.org/browse/JBEHAVE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-27: Due Date: (was: 24/Nov/04) > Document best practices and suggested use cases > --

[jbehave-dev] [jira] Created: (JBEHAVE-149) Support conversion of scenarios from non-textual formats

Support conversion of scenarios from non-textual formats Key: JBEHAVE-149 URL: http://jira.codehaus.org/browse/JBEHAVE-149 Project: JBehave Issue Type: New Feature Reporter

[jbehave-dev] [jira] Created: (JBEHAVE-150) URL-based scenario definer

URL-based scenario definer -- Key: JBEHAVE-150 URL: http://jira.codehaus.org/browse/JBEHAVE-150 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi As a scenario de

[jbehave-dev] [jira] Created: (JBEHAVE-151) Better support for web scenarios

Better support for web scenarios Key: JBEHAVE-151 URL: http://jira.codehaus.org/browse/JBEHAVE-151 Project: JBehave Issue Type: New Feature Reporter: Mauro Talevi As a web developer/QA, I want t

[jbehave-dev] [jira] Updated: (JBEHAVE-133) Add lightweight container support for steps

[ http://jira.codehaus.org/browse/JBEHAVE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-133: - Description: In acceptance/integration tests is often common to have a lightweight container (Pico,

[jbehave-dev] [jira] Assigned: (JBEHAVE-126) GivenScenarios

[ http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-126: Assignee: Mauro Talevi > GivenScenarios > -- > > Key: JBEHAVE-126 >

[jbehave-dev] [jira] Work started: (JBEHAVE-126) GivenScenarios

[ http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-126 started by Mauro Talevi. > GivenScenarios > -- > > Key: JBEHAVE-126 > URL: http://jira.codehaus.org/browse/JBEH

[jbehave-dev] [jira] Updated: (JBEHAVE-152) Scenario's in the default package cause NullPointerException

[ http://jira.codehaus.org/browse/JBEHAVE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-152: - Affects Version/s: (was: 2.2) 2.1 2.0.1

[jbehave-dev] [jira] Assigned: (JBEHAVE-152) Scenario's in the default package cause NullPointerException

[ http://jira.codehaus.org/browse/JBEHAVE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-152: Assignee: Mauro Talevi > Scenario's in the default package cause NullPointerException >

[jbehave-dev] [jira] Commented: (JBEHAVE-126) GivenScenarios

[ http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157529#action_157529 ] Mauro Talevi commented on JBEHAVE-126: -- I'm thinking that GivenStory would be more suited as ke

[jbehave-dev] [jira] Closed: (JBEHAVE-154) Scenario keyword should include any separation char, e.g. ":"

[ http://jira.codehaus.org/browse/JBEHAVE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi closed JBEHAVE-154. Resolution: Fixed > Scenario keyword should include any separation char, e.g. ":" >

[jbehave-dev] [jira] Created: (JBEHAVE-154) Scenario keyword should include any separation char, e.g. ":"

Scenario keyword should include any separation char, e.g. ":" - Key: JBEHAVE-154 URL: http://jira.codehaus.org/browse/JBEHAVE-154 Project: JBehave Issue Type: Improvement

[jbehave-dev] [jira] Commented: (JBEHAVE-152) Scenario's in the default package cause NullPointerException

[ http://jira.codehaus.org/browse/JBEHAVE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157965#action_157965 ] Mauro Talevi commented on JBEHAVE-152: -- Committed fix but not the unit test as I could not get

[jbehave-dev] [jira] Resolved: (JBEHAVE-152) Scenario's in the default package cause NullPointerException

[ http://jira.codehaus.org/browse/JBEHAVE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-152. -- Resolution: Fixed Added example to verify behaviour. > Scenario's in the default package cause Null

[jbehave-dev] [jira] Commented: (JBEHAVE-126) GivenScenarios

[ http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160633#action_160633 ] Mauro Talevi commented on JBEHAVE-126: -- I agree that story should be a separate model concept.

[jbehave-dev] [jira] Created: (JBEHAVE-156) Allow resolution of multiple textual scenarios from a single Java scenario

Allow resolution of multiple textual scenarios from a single Java scenario -- Key: JBEHAVE-156 URL: http://jira.codehaus.org/browse/JBEHAVE-156 Project: JBehave Issue Ty

[jbehave-dev] [jira] Updated: (JBEHAVE-156) Allow resolution of multiple textual scenarios from a single Java scenario

[ http://jira.codehaus.org/browse/JBEHAVE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-156: - Description: As a scenario runner, I want to be able to run multiple textual scenarios from the same

[jbehave-dev] [jira] Updated: (JBEHAVE-155) Maven plugin can't identify Scenario classes in src/test/java

[ http://jira.codehaus.org/browse/JBEHAVE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-155: - Summary: Maven plugin can't identify Scenario classes in src/test/java (was: Mven plugin can't identi

[jbehave-dev] [jira] Assigned: (JBEHAVE-155) Mven plugin can't identify Scenario classes in src/test/java

[ http://jira.codehaus.org/browse/JBEHAVE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-155: Assignee: Mauro Talevi > Mven plugin can't identify Scenario classes in src/test/java >

[jbehave-dev] [jira] Updated: (JBEHAVE-155) Maven plugin can't identify Scenario classes in src/test/java

[ http://jira.codehaus.org/browse/JBEHAVE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-155: - Fix Version/s: 2.1.1 Binil, confirmed and tracked down problem. Will release bugfix version 2.1.1 an

[jbehave-dev] [jira] Updated: (JBEHAVE-155) Maven plugin can't identify Scenario classes in src/test/java

[ http://jira.codehaus.org/browse/JBEHAVE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-155: - Fix Version/s: 2.2 Fixed in 2.1.1 and trunk. > Maven plugin can't identify Scenario classes in src/te

[jbehave-dev] [jira] Resolved: (JBEHAVE-155) Maven plugin can't identify Scenario classes in src/test/java

[ http://jira.codehaus.org/browse/JBEHAVE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-155. -- Resolution: Fixed Version 2.1.1 released. > Maven plugin can't identify Scenario classes in src/tes

[jbehave-dev] [jira] Assigned: (JBEHAVE-157) Steps class can't depend on a library with test in pom.xml

[ http://jira.codehaus.org/browse/JBEHAVE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-157: Assignee: Mauro Talevi > Steps class can't depend on a library with test in pom.xml > --

[jbehave-dev] [jira] Resolved: (JBEHAVE-157) Steps class can't depend on a library with test in pom.xml

[ http://jira.codehaus.org/browse/JBEHAVE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-157. -- Resolution: Won't Fix Just declare the steps dependency at runtime scope and the scenarios will run

[jbehave-dev] [jira] Created: (JBEHAVE-158) Generate StepsDoc from annotated methods

Generate StepsDoc from annotated methods Key: JBEHAVE-158 URL: http://jira.codehaus.org/browse/JBEHAVE-158 Project: JBehave Issue Type: New Feature Components: Core Affects Versions: 2.1

[jbehave-dev] [jira] Updated: (JBEHAVE-158) Generate StepDoc from annotated methods

[ http://jira.codehaus.org/browse/JBEHAVE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-158: - Description: Given a Steps instance, it'd be very useful to generate the list of candidate steps avai

[jbehave-dev] [jira] Assigned: (JBEHAVE-158) Generate StepDoc from annotated methods

[ http://jira.codehaus.org/browse/JBEHAVE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-158: Assignee: Mauro Talevi > Generate StepDoc from annotated methods > -

[jbehave-dev] [jira] Work started: (JBEHAVE-158) Generate StepDoc from annotated methods

[ http://jira.codehaus.org/browse/JBEHAVE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-158 started by Mauro Talevi. > Generate StepDoc from annotated methods > --- > > Key: JBEHAVE-158 >

[jbehave-dev] [jira] Assigned: (JBEHAVE-133) Add lightweight container support for steps

[ http://jira.codehaus.org/browse/JBEHAVE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-133: Assignee: (was: Mauro Talevi) > Add lightweight container support for steps > -

[jbehave-dev] [jira] Commented: (JBEHAVE-158) Generate StepDoc from annotated methods

[ http://jira.codehaus.org/browse/JBEHAVE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166634#action_166634 ] Mauro Talevi commented on JBEHAVE-158: -- Documentation added to http://jbehave.org/documentation

[jbehave-dev] [jira] Resolved: (JBEHAVE-158) Generate StepDoc from annotated methods

[ http://jira.codehaus.org/browse/JBEHAVE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-158. -- Resolution: Fixed Done > Generate StepDoc from annotated methods >

[jbehave-dev] [jira] Updated: (JBEHAVE-126) GivenScenarios

[ http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-126: - Fix Version/s: (was: 2.2) 2.3 Bumping out of 2.2 release until consensus is rea

[jbehave-dev] [jira] Updated: (JBEHAVE-156) Allow resolution of multiple textual scenarios from a single Java scenario

[ http://jira.codehaus.org/browse/JBEHAVE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-156: - Affects Version/s: (was: 2.1) 2.3 This feature may or may not be relevant a

[jbehave-dev] [jira] Updated: (JBEHAVE-156) Allow resolution of multiple textual scenarios from a single Java scenario

[ http://jira.codehaus.org/browse/JBEHAVE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-156: - Affects Version/s: (was: 2.3) 2.0 Fix Version/s: (was: 2.2) Bum

[jbehave-dev] [jira] Updated: (JBEHAVE-130) Other examples include

[ http://jira.codehaus.org/browse/JBEHAVE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-130: - Fix Version/s: (was: 2.2) 2.3 Bumping out of 2.2 release until consensus is rea

[jbehave-dev] [jira] Updated: (JBEHAVE-139) Convert ant build to use ivy for dependencies

[ http://jira.codehaus.org/browse/JBEHAVE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-139: - Bumping out of 2.2 release until some Ant-driven soul is motivated to implement Ivy-based dependency look

[jbehave-dev] [jira] Updated: (JBEHAVE-139) Convert ant build to use ivy for dependencies

[ http://jira.codehaus.org/browse/JBEHAVE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-139: - Comment: was deleted (was: Bumping out of 2.2 release until some Ant-driven soul is motivated to impl

[jbehave-dev] [jira] Updated: (JBEHAVE-139) Convert ant build to use ivy for dependencies

[ http://jira.codehaus.org/browse/JBEHAVE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-139: - Fix Version/s: (was: 2.2) Bumping out of 2.2 release until some Ant-driven soul is motivated to im

[jbehave-dev] [jira] Work stopped: (JBEHAVE-126) GivenScenarios

[ http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-126 stopped by Mauro Talevi. > GivenScenarios > -- > > Key: JBEHAVE-126 > URL: http://jira.codehaus.org/browse/JBEH

[jbehave-dev] [jira] Resolved: (JBEHAVE-27) Document best practices and suggested use cases

[ http://jira.codehaus.org/browse/JBEHAVE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-27. - Resolution: Fixed Closing for now. Wiki page will be enhanced as new use cases and best-practices be

[jbehave-dev] [jira] Updated: (JBEHAVE-127) Doesn't find scenarios with numbers in the file name

[ http://jira.codehaus.org/browse/JBEHAVE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-127: - Configured to support both resolution modes, ie treating numbers as upper case letters (the default) and

[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-127) Doesn't find scenarios with numbers in the file name

[ http://jira.codehaus.org/browse/JBEHAVE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172052#action_172052 ] Mauro Talevi edited comment on JBEHAVE-127 at 4/5/09 5:50 AM: -- Configur

[jbehave-dev] [jira] Resolved: (JBEHAVE-147) Improve javadocs

[ http://jira.codehaus.org/browse/JBEHAVE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-147. -- Resolution: Fixed > Improve javadocs > > > Key: JBEHAVE-147 >

[jbehave-dev] [jira] Resolved: (JBEHAVE-145) Unit-test runners should decorate Exceptions a bit more clearly

[ http://jira.codehaus.org/browse/JBEHAVE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-145. -- Resolution: Fixed Phil, applied patch with thanks. I've renamed decorator to StepFailureScenarioRe

[jbehave-dev] [jira] Updated: (JBEHAVE-158) Generate StepDoc from annotated methods of CandidateSteps instance

[ http://jira.codehaus.org/browse/JBEHAVE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-158: - Description: Given a CandidateSteps instance, we want generate the list of annotated candidate steps

[jbehave-dev] [jira] Created: (JBEHAVE-159) Support multiple CandidateSteps instances in Stepdoc generation

Support multiple CandidateSteps instances in Stepdoc generation --- Key: JBEHAVE-159 URL: http://jira.codehaus.org/browse/JBEHAVE-159 Project: JBehave Issue Type: Improvement

[jbehave-dev] [jira] Resolved: (JBEHAVE-159) Support multiple CandidateSteps instances in Stepdoc generation

[ http://jira.codehaus.org/browse/JBEHAVE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-159. -- Resolution: Fixed > Support multiple CandidateSteps instances in Stepdoc generation > --

[jbehave-dev] [jira] Updated: (JBEHAVE-159) Support multiple CandidateSteps instances in Stepdoc generation

[ http://jira.codehaus.org/browse/JBEHAVE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-159: - Description: Make StepdocGenerator contract more generic to support a vararg of CandidateSteps instan

[jbehave-dev] [jira] Created: (JBEHAVE-160) Improve regex-based scenario parsing

Improve regex-based scenario parsing Key: JBEHAVE-160 URL: http://jira.codehaus.org/browse/JBEHAVE-160 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 2.1

[jbehave-dev] [jira] Assigned: (JBEHAVE-160) Improve regex-based scenario parsing

[ http://jira.codehaus.org/browse/JBEHAVE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-160: Assignee: Mauro Talevi > Improve regex-based scenario parsing >

[jbehave-dev] [jira] Commented: (JBEHAVE-160) Improve regex-based scenario parsing

[ http://jira.codehaus.org/browse/JBEHAVE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173451#action_173451 ] Mauro Talevi commented on JBEHAVE-160: -- Refactored multi-scenario parsing to split scenarios by

[jbehave-dev] [jira] Resolved: (JBEHAVE-160) Improve regex-based scenario parsing

[ http://jira.codehaus.org/browse/JBEHAVE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-160. -- Resolution: Fixed > Improve regex-based scenario parsing > > >

[jbehave-dev] [jira] Created: (JBEHAVE-161) HTML-based scenario reporter

HTML-based scenario reporter Key: JBEHAVE-161 URL: http://jira.codehaus.org/browse/JBEHAVE-161 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi F

[jbehave-dev] [jira] Updated: (JBEHAVE-161) HTML-based scenario reporter

[ http://jira.codehaus.org/browse/JBEHAVE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-161: - Description: A template-based implementation of ScenarioReporter for HTML-based reporting. was: A

[jbehave-dev] [jira] Created: (JBEHAVE-164) I18N Keywords

I18N Keywords - Key: JBEHAVE-164 URL: http://jira.codehaus.org/browse/JBEHAVE-164 Project: JBehave Issue Type: Improvement Reporter: Mauro Talevi Priority: Minor Fix For: 2.3 As proposed by

[jbehave-dev] [jira] Updated: (JBEHAVE-163) Support comments in plain-test scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-163: - Fix Version/s: (was: 2.2) 2.3 > Support comments in plain-test scenarios >

[jbehave-dev] [jira] Commented: (JBEHAVE-163) Support comments in plain-test scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181761#action_181761 ] Mauro Talevi commented on JBEHAVE-163: -- Currently, comments can be placed in the scenario text

[jbehave-dev] [jira] Updated: (JBEHAVE-162) Need to be able to set order of steps for matching

[ http://jira.codehaus.org/browse/JBEHAVE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-162: - Fix Version/s: (was: 2.2) 2.3 > Need to be able to set order of steps for match

[jbehave-dev] [jira] Commented: (JBEHAVE-162) Need to be able to set order of steps for matching

[ http://jira.codehaus.org/browse/JBEHAVE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181763#action_181763 ] Mauro Talevi commented on JBEHAVE-162: -- I'm not sure that we'd gain much by adding an @Order an

[jbehave-dev] [jira] Updated: (JBEHAVE-163) Support comments in plain-text scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-163: - Summary: Support comments in plain-text scenarios (was: Support comments in plain-test scenarios) >

[jbehave-dev] [jira] Updated: (JBEHAVE-164) I18N Keywords

[ http://jira.codehaus.org/browse/JBEHAVE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-164: - Description: As proposed by Emerson Macedo on dev list, it would be useful to have keywords for diffe

[jbehave-dev] [jira] Commented: (JBEHAVE-164) I18N Keywords

[ http://jira.codehaus.org/browse/JBEHAVE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181803#action_181803 ] Mauro Talevi commented on JBEHAVE-164: -- I think we should still pursue the JDK-way, because the

[jbehave-dev] [jira] Commented: (JBEHAVE-164) I18N Keywords

[ http://jira.codehaus.org/browse/JBEHAVE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181862#action_181862 ] Mauro Talevi commented on JBEHAVE-164: -- But I'm thinking it makes sense to provide the keyword

[jbehave-dev] [jira] Created: (JBEHAVE-165) Enable scenarios to run in fail-batch mode

Enable scenarios to run in fail-batch mode -- Key: JBEHAVE-165 URL: http://jira.codehaus.org/browse/JBEHAVE-165 Project: JBehave Issue Type: Improvement Affects Versions: 2.2 Reporter:

<    1   2   3   4   5   6   7   8   9   10   >