[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-scm] [871] trunk/jbehave-core/src/java/org/jbehave/scenario/steps: [Liz] We no longer care about whitespace in args
Title: [871] trunk/jbehave-core/src/java/org/jbehave/scenario/steps: [Liz] We no longer care about whitespace in args
Revision 871
Author sirenian
Date 2008-07-18 08:29:54 -0500 (Fri, 18 Jul 2008)
Log Message
[Liz] We no longer care about whitespace in args
Modified Paths
trunk/examples/gameoflife/src/behaviour/com/lunivore/gameoflife/domain/GameBehaviour.java
trunk/examples/gameoflife/src/behaviour/com/lunivore/gameoflife/view/string/StringRendererBehaviour.java
trunk/examples/gameoflife/src/java/com/lunivore/gameoflife/view/string/StringRenderer.java
trunk/examples/gameoflife/src/scenario/com/lunivore/gameoflife/i_can_toggle_a_cell
trunk/examples/gameoflife/src/scenario/com/lunivore/gameoflife/the_grid_starts_empty
trunk/jbehave-core/src/behaviour/org/jbehave/scenario/steps/DollarStepPatternBuilderBehaviour.java
trunk/jbehave-core/src/java/org/jbehave/scenario/steps/DollarStepPatternBuilder.java
Diff
Modified: trunk/examples/gameoflife/src/behaviour/com/lunivore/gameoflife/domain/GameBehaviour.java (870 => 871)
--- trunk/examples/gameoflife/src/behaviour/com/lunivore/gameoflife/domain/GameBehaviour.java 2008-06-27 11:50:05 UTC (rev 870)
+++ trunk/examples/gameoflife/src/behaviour/com/lunivore/gameoflife/domain/GameBehaviour.java 2008-07-18 13:29:54 UTC (rev 871)
@@ -16,7 +16,7 @@
StringRenderer renderer = new StringRenderer();
Game game = new Game(6, 4);
game.setObserver(renderer);
- ensureThat(renderer.asString(), CoreMatchers.equalTo(NL +
+ ensureThat(renderer.asString(), CoreMatchers.equalTo(
.. + NL +
.. + NL +
.. + NL +
@@ -29,19 +29,19 @@
Game game = new Game(6, 4);
game.setObserver(renderer);
game.toggleCellAt(2, 1);
- ensureThat(renderer.asString(), CoreMatchers.equalTo(NL +
+ ensureThat(renderer.asString(), CoreMatchers.equalTo(
.. + NL +
..X... + NL +
.. + NL +
..));
game.toggleCellAt(2, 2);
- ensureThat(renderer.asString(), CoreMatchers.equalTo(NL +
+ ensureThat(renderer.asString(), CoreMatchers.equalTo(
.. + NL +
..X... + NL +
..X... + NL +
..));
game.toggleCellAt(2, 1);
- ensureThat(renderer.asString(), CoreMatchers.equalTo(NL +
+ ensureThat(renderer.asString(), CoreMatchers.equalTo(
.. + NL +
.. + NL +
..X... + NL +
Modified: trunk/examples/gameoflife/src/behaviour/com/lunivore/gameoflife/view/string/StringRendererBehaviour.java (870 => 871)
--- trunk/examples/gameoflife/src/behaviour/com/lunivore/gameoflife/view/string/StringRendererBehaviour.java 2008-06-27 11:50:05 UTC (rev 870)
+++ trunk/examples/gameoflife/src/behaviour/com/lunivore/gameoflife/view/string/StringRendererBehaviour.java 2008-07-18 13:29:54 UTC (rev 871)
@@ -22,7 +22,7 @@
stub(grid.hasLife(3, 4)).toReturn(true);
renderer.gridChanged(grid);
- ensureThat(renderer.asString(), equalTo(NL +
+ ensureThat(renderer.asString(), equalTo(
. + NL +
. + NL +
. + NL +
Modified: trunk/examples/gameoflife/src/java/com/lunivore/gameoflife/view/string/StringRenderer.java (870 => 871)
--- trunk/examples/gameoflife/src/java/com/lunivore/gameoflife/view/string/StringRenderer.java 2008-06-27 11:50:05 UTC (rev 870)
+++ trunk/examples/gameoflife/src/java/com/lunivore/gameoflife/view/string/StringRenderer.java 2008-07-18 13:29:54 UTC (rev 871)
@@ -10,7 +10,6 @@
public String asString() {
StringBuilder builder = new StringBuilder();
- builder.append(NL);
for (int row = 0; row grid.getHeight(); row++) {
for (int column = 0; column grid.getWidth(); column++) {
builder.append(grid.hasLife(column, row) ? X : .);
Modified: trunk/examples/gameoflife/src/scenario/com/lunivore/gameoflife/i_can_toggle_a_cell (870 => 871)
--- trunk/examples/gameoflife/src/scenario/com/lunivore/gameoflife/i_can_toggle_a_cell 2008-06-27 11:50:05 UTC (rev 870)
+++ trunk/examples/gameoflife/src/scenario/com/lunivore/gameoflife/i_can_toggle_a_cell 2008-07-18 13:29:54 UTC (rev 871)
@@ -1,20 +1,20 @@
Given a 5 by 5 game
When I toggle the cell at (2, 3)
-Then the grid should look like
+Then the grid should look like
.
.
.
..X..
.
When I toggle the cell at (2, 4)
-Then the grid should look like
+Then the grid should look like
.
.
.
..X..
..X..
When I toggle the cell at (2, 3)
-Then the grid should look like
+Then the grid should look like
.
.
.
Modified: trunk/examples/gameoflife/src/scenario/com/lunivore/gameoflife/the_grid_starts_empty (870 => 871)
--- trunk/examples/gameoflife/src/scenario/com/lunivore/gameoflife/the_grid_starts_empty 2008-06-27 11:50:05 UTC (rev 870)
+++ trunk/examples/gameoflife/src/scenario/com/lunivore/gameoflife/the_grid_starts_empty 2008-07-18 13:29:54 UTC (rev 871)
@@ -1,7 +1,7 @@
Given a 5 by 5 game
-Then the grid should look like
+Then the grid should look like
.
.
.
.
-.
\ No newline at end of file
+.
Modified:
