Development list for jBehave project

Elizabeth Keogh | 1 Feb 2007 15:41

Story documentation

Hi all,

I don't care if we go to 1.0 before documentation, really - anyone who really wants to know how to use JBehave can get hold of the examples.

However, I think we should update it soon. Below is a first draft of some Story documentation, based on my next breakable toy. When I move it to a web page I will of course provide links to all the various APIs, Ant home page, etc.

I'm particularly pleased with the way you can use JBehave's APIs in English sentences; eg: A Renderer can renderAny(Object).

On that note, I would like to rename Run to BehaviourRunner, and all the JBehave<whatever> tasks to BehaviourTask, StoryTask, StoryPrintingTask, etc. They don't need the JBehave qualifiers, IMHO.

Cheers,
Liz.

--

How to use JBehave's Story Framework
------------------------------------

<CUSTOMER>

As a customer, you are someone with a stake or interest in the outcome of the project. Maybe you're in charge of the money,
or you're an end user. Lots of articles have been written about Agile Customers. Go read them.

For the examples in this story, the customer is a Frustrated Sudoku Solver. If the project is successful then he will
be able to quickly solve any sudoku just by typing it into a web interface. That's his interest in the project.

<The Story>

First, think of a story which gives you something you want. Think of a name which encapsulates it and write it down as Title: <story name>, eg:

- Title: Reduces potentials when definite in same row or column

<The Narrative>

Then, write down your role, what you want and the value you'd like to get from it, using the form:

- As a <role>
- I want <some feature>
- So that <some benefit>

eg:

- As a <frustrated sudoku solver>
- I want <a digit to be removed from potential digits in a cell when that digit definitely exists in the same row or column>
- So that <I can get closer to the solution>

<The Scenarios>

Now think of scenarios which will help you to determine whether you've got the system behaviour you want. The scenarios should be
specific. They don't need to fully cover the behaviour you're looking for, but they should give you a reasonable certainty that
the system works as you expect. If you ever find out that it isn't giving you what you want, you can add more scenarios later.

Your QAs - and maybe even the devs - can help with this.

Think of a name which encapsulates each scenario, and write it down as Scenario: <Scenario name>. eg:

Scenario: A three appears in the last cell when the square has threes in two rows and two columns.

The scenarios should be of the form: given <some context>, when <some events happen>, then <some outcome should result>.

Write them down in the form

- Given <some context>
- When <some event happens>
- Then <some outcome should result>

eg:

- Given the grid looks like
3..|...|...
...|...|...
...|...|...
-----------
..3|...|...
...|...|...
...|...|...
-----------
...|3..|...
...|...|...
...|...|..3
- When the next step is taken
- Then the grid should look like
3..|...|...
...|...|...
...|...|...
-----------
..3|...|...
...|...|...
...|...|...
-----------
...|3..|...
.3.|...|...
...|...|..3

<Reusing scenarios>

You can use previously created scenarios as the context for new ones. Think carefully about the scenario name if you
do this, because it will have to make sense in the context of the new scenario too:

- Given a three appears in the last cell when the square has threes in two rows and two columns
- Given I have three black sheep therefore three balls of black wool
- Given I buy a bike and have £250 less in my bank account

Usually expressing both the event and the outcome in the scenario name helps with this.

When you have enough scenarios, write them all down and give the story to your developer.

<DEVELOPER>

If the text file that your customer has given you is of the form <some name>.story, then you can use the JBehave
Eclipse plugin to help you generate your empty code. Just ctrl-click on the story title, the scenario name,
the givens, events, outcomes, etc.

If you can't or don't want to use the plugin, the code can be manually generated.

<The Story>

Your class name should be a camel-cased version of the story name, eg: ReducesPotentialsWhenDefiniteInSameRowOrColumn.java

The class must be a Story - we suggest it should be a ScenarioDrivenStory. You'll notice that you need to provide a Narrative,
and you must specify() your scenarios. addScenario() for each scenario your customer's asked for, creating a new class for
each Scenario.

Each scenario will be run or printed along with the story.

<The Scenarios>

Each scenario has a series of steps, which are Givens, Events and Outcomes. specifySteps() by providing a new instance of each
step in the order in which they happen. For instance:

String NL = System.getProperty("line.separator");

given(new TheGridLooksLike(
"3..|...|..." + NL +
"...|...|..." + NL +
"...|...|..." + NL +
"-----------" + NL +
"..3|...|..." + NL +
"...|...|..." + NL +
"...|...|..." + NL +
"-----------" + NL +
"...|3..|..." + NL +
"...|...|..." + NL +
"...|...|..3"
));
when(new TheNextStepIsTaken());
then(new TheGridShouldLookLike(
"3..|...|..." + NL +
"...|...|..." + NL +
"...|...|..." + NL +
"-----------" + NL +
"..3|...|..." + NL +
"...|...|..." + NL +
"...|...|..." + NL +
"-----------" + NL +
"...|3..|..." + NL +
".3.|...|..." + NL + //<-- new digit
"...|...|..3"
));

These should match the steps which your customer has provided you.

<Scenario steps>

Each scenario step can be a Given, Event or Outcome. We suggest they should be <step>UsingMiniMock.

As the story runs, Givens will setUp() the world, Events will occurIn() the world and Outcomes will verify() the world.
The implementation of each step is up to you. The World in which these steps take place is the same for all the steps
in a Story, so anything you put() into the World, you can get() out later.

<Running a story>

The StoryRunner runs stories. So does the JBehaveStoryTask for Ant.

<Printing a story>

The StoryPrinter prints stories.

If you're passing parameters to your steps, scenarios or stories, we suggest that you narrateTo(Renderer) yourself.
A Renderer can renderAny(Object). For instance:

public class TheGridShouldLookLike extends OutcomeUsingMiniMock {

private final String asciiGrid;

public TheGridShouldLookLike(String asciiGrid) {
this.asciiGrid = asciiGrid;
}

// ...

public void narrateTo(Renderer renderer) {
super.narrateTo(renderer);
renderer.renderAny(asciiGrid);
}
}

If your customer hasn't provided you with the text of a story, printing a Story will give you that text.

If the customer has provided you with story text, then hopefully printing the Story will look just the same.

--
Elizabeth Keogh
liz-IFekc9qy6S0WhyVFc8JwjA@public.gmane.org
http://www.livejournal.com/users/sirenian

headers

Mauro Talevi | 4 Feb 2007 12:19

Maven repositories at Codehaus

Hi folks,

the Maven repos have been created at Codehaus.  They are:

- http://repository.codehaus.org/org/jbehave/ - this is for stable and versioned releases, which is 
synched with Maven's Central Repo every few hours.
- http://snapshots.repository.codehaus.org/org/jbehave/ - for snapshots

I've uploaded the latest stable and latest snapshot.

Independently of the synching, you can use the Maven plugin by configuring in your POM (typically 
your parent POM):

    <pluginRepositories>
         <pluginRepository>
             <id>codehaus-plugin-repository</id>
             <name>Codehaus Plugin Repository</name>
             <url>http://repository.codehaus.org</url>
         </pluginRepository>
         <pluginRepository>
             <id>codehaus-plugin-snapshot-repository</id>
             <name>Codehaus Plugin Snapshot Repository</name>
             <url>http://snapshots.repository.codehaus.org</url>
             <snapshots>
                 <enabled>true</enabled>
             </snapshots>
         </pluginRepository>
     </pluginRepositories>

If you are just using stable releases, the above configuration becomes redundant after a few hours 
of the release, as the Central Maven Repo is configured by default.   These are more useful if you 
are developing and don't want to wait until the synch is done or are using snapshot releases.

To use the jBehave plugin in your project

           <plugin>
                 <groupId>org.jbehave</groupId>
                 <artifactId>jbehave-maven-plugin</artifactId>
                 <version>0.9.0</version>
                 <executions>
                     <execution>
                         <phase>integration-test</phase>
                         <goals>
                             <goal>run</goal>
                         </goals>
                         <configuration>
                             <behavioursClassName>
                                 jbehave.AcceptanceBehaviours
                             </behavioursClassName>
                         </configuration>
                     </execution>
                 </executions>
             </plugin>

The run goal will verify all the behaviours specified by the Behaviours class.
At the moment, because Behaviours can encode multiple behaviour classes, it is a single class that 
can be specified.  We can easily extend it to a list, though.

One thing that I would also like to add is the includes/excludes patterns.

Cheers

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

headers

Carlos Villela | 4 Feb 2007 18:59

Re: Failure on slow Macs

Thanks Liz, it's been fixed!

On 1/19/07, Elizabeth Keogh <ekeogh@...> wrote:
>
> Take a look at the Typer (can't remember what the class is called) used by
> the DefaultWindowWrapper. I added a listener to the events which hangs until
> it receives it, then waits for the event queue to empty. One would hope that
> would mean that other listeners had, by then, also been informed.
>
> Unfortunately, sometimes the Typer's listeners aren't getting the posted
> events _at all_ on Ubuntu, so they're timing out. Haven't worked out why
> that's the case.
>
> I haven't added this checker to the button clicks yet, but can do so. Any
> chance we can check I've fixed it on your Mac?
>
> Cheers,
> Liz.
>
> --
>  Elizabeth Keogh
>  liz@...
>  http://www.livejournal.com/users/sirenian
>
>
> "Carlos Villela" <carlos.villela@...> wrote on 16/01/2007 20:51:37:
>
>
>  > Hey gang,
>  >
>  > I've noticed the build's been failing on my iBook G4, like this:
>  >
>  > [run behaviours] 1) DefaultWindowWrapper should click a button on a
> window:
>  > [run behaviours] VerificationException: Expected at least 1 calls but
>  > got 0 for actionListener.actionPerformed[anything]:
>  > (...)
>  > at
> org.jbehave.core.minimock.UsingMiniMock.verifyMocks(UsingMiniMock.java:63)
>  > at
> org.jbehave.threaded.swing.DefaultWindowWrapperBehaviour.
>  >
> shouldClickAButtonOnAWindow(DefaultWindowWrapperBehaviour.java:50)
>  > (...)
>  >
>  > Apparently, putting a Thread.sleep(500) around line 45 in
>  > DefaultWindowWrapperBehaviour fixes it - but I know this is far from
>  > acceptable.
>  >
>  > Any ideas on how to go about it?
>  >
>  > Cheers,
>  >
>  > - Carlos
>  >
>  >
> ---------------------------------------------------------------------
>  > To unsubscribe from this list please visit:
>  >
>  >     http://xircles.codehaus.org/manage_email
>  >
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

headers

Dan North | 5 Feb 2007 22:57

Documenting BDD [was: Story documentation]

I love it.

I presented a BDD session at the recent Software Architecture Workshop in Switzerland and got a) lots of positive feedback (like, lots - really lots - I think it's going somewhere), and b) a request that I write more of it down rather than just explaining it to small groups of people.

The immediate fix for b) is to get this kind of documentation on jbehave.org and to start blogging some mini-articles about BDD. The first one is called "What's in a story?" and will be published some time this week. It's come in at about 1500-2000 words, so it's a bit of an experiment in terms of how much people will bother to read. I'll tune the subsequent ones based on feedback.

Also, someone pointed me to a thread on an XP newsgroup about stories in BDD, which I replied to, so feel free to chime in there too.

Cheers,
Dan

Elizabeth Keogh wrote:

Hi all,

I don't care if we go to 1.0 before documentation, really - anyone who really wants to know how to use JBehave can get hold of the examples.

However, I think we should update it soon. Below is a first draft of some Story documentation, based on my next breakable toy. When I move it to a web page I will of course provide links to all the various APIs, Ant home page, etc.

I'm particularly pleased with the way you can use JBehave's APIs in English sentences; eg: A Renderer can renderAny(Object).

On that note, I would like to rename Run to BehaviourRunner, and all the JBehave<whatever> tasks to BehaviourTask, StoryTask, StoryPrintingTask, etc. They don't need the JBehave qualifiers, IMHO.

Cheers,
Liz.

--

How to use JBehave's Story Framework
------------------------------------

<CUSTOMER>

As a customer, you are someone with a stake or interest in the outcome of the project. Maybe you're in charge of the money,
or you're an end user. Lots of articles have been written about Agile Customers. Go read them.

For the examples in this story, the customer is a Frustrated Sudoku Solver. If the project is successful then he will
be able to quickly solve any sudoku just by typing it into a web interface. That's his interest in the project.

<The Story>

First, think of a story which gives you something you want. Think of a name which encapsulates it and write it down as Title: <story name>, eg:

- Title: Reduces potentials when definite in same row or column

<The Narrative>

Then, write down your role, what you want and the value you'd like to get from it, using the form:

- As a <role>
- I want <some feature>
- So that <some benefit>

eg:

- As a <frustrated sudoku solver>
- I want <a digit to be removed from potential digits in a cell when that digit definitely exists in the same row or column>
- So that <I can get closer to the solution>

<The Scenarios>

Now think of scenarios which will help you to determine whether you've got the system behaviour you want. The scenarios should be
specific. They don't need to fully cover the behaviour you're looking for, but they should give you a reasonable certainty that
the system works as you expect. If you ever find out that it isn't giving you what you want, you can add more scenarios later.

Your QAs - and maybe even the devs - can help with this.

Think of a name which encapsulates each scenario, and write it down as Scenario: <Scenario name>. eg:

Scenario: A three appears in the last cell when the square has threes in two rows and two columns.

The scenarios should be of the form: given <some context>, when <some events happen>, then <some outcome should result>.

Write them down in the form

- Given <some context>
- When <some event happens>
- Then <some outcome should result>

eg:

- Given the grid looks like
3..|...|...
...|...|...
...|...|...
-----------
..3|...|...
...|...|...
...|...|...
-----------
...|3..|...
...|...|...
...|...|..3
- When the next step is taken
- Then the grid should look like
3..|...|...
...|...|...
...|...|...
-----------
..3|...|...
...|...|...
...|...|...
-----------
...|3..|...
.3.|...|...
...|...|..3

<Reusing scenarios>

You can use previously created scenarios as the context for new ones. Think carefully about the scenario name if you
do this, because it will have to make sense in the context of the new scenario too:

- Given a three appears in the last cell when the square has threes in two rows and two columns
- Given I have three black sheep therefore three balls of black wool
- Given I buy a bike and have £250 less in my bank account

Usually expressing both the event and the outcome in the scenario name helps with this.

When you have enough scenarios, write them all down and give the story to your developer.

<DEVELOPER>

If the text file that your customer has given you is of the form <some name>.story, then you can use the JBehave
Eclipse plugin to help you generate your empty code. Just ctrl-click on the story title, the scenario name,
the givens, events, outcomes, etc.

If you can't or don't want to use the plugin, the code can be manually generated.

<The Story>

Your class name should be a camel-cased version of the story name, eg: ReducesPotentialsWhenDefiniteInSameRowOrColumn.java

The class must be a Story - we suggest it should be a ScenarioDrivenStory. You'll notice that you need to provide a Narrative,
and you must specify() your scenarios. addScenario() for each scenario your customer's asked for, creating a new class for
each Scenario.

Each scenario will be run or printed along with the story.

<The Scenarios>

Each scenario has a series of steps, which are Givens, Events and Outcomes. specifySteps() by providing a new instance of each
step in the order in which they happen. For instance:

String NL = System.getProperty("line.separator");

given(new TheGridLooksLike(
"3..|...|..." + NL +
"...|...|..." + NL +
"...|...|..." + NL +
"-----------" + NL +
"..3|...|..." + NL +
"...|...|..." + NL +
"...|...|..." + NL +
"-----------" + NL +
"...|3..|..." + NL +
"...|...|..." + NL +
"...|...|..3"
));
when(new TheNextStepIsTaken());
then(new TheGridShouldLookLike(
"3..|...|..." + NL +
"...|...|..." + NL +
"...|...|..." + NL +
"-----------" + NL +
"..3|...|..." + NL +
"...|...|..." + NL +
"...|...|..." + NL +
"-----------" + NL +
"...|3..|..." + NL +
".3.|...|..." + NL + //<-- new digit
"...|...|..3"
));

These should match the steps which your customer has provided you.

<Scenario steps>

Each scenario step can be a Given, Event or Outcome. We suggest they should be <step>UsingMiniMock.

As the story runs, Givens will setUp() the world, Events will occurIn() the world and Outcomes will verify() the world.
The implementation of each step is up to you. The World in which these steps take place is the same for all the steps
in a Story, so anything you put() into the World, you can get() out later.

<Running a story>

The StoryRunner runs stories. So does the JBehaveStoryTask for Ant.

<Printing a story>

The StoryPrinter prints stories.

If you're passing parameters to your steps, scenarios or stories, we suggest that you narrateTo(Renderer) yourself.
A Renderer can renderAny(Object). For instance:

public class TheGridShouldLookLike extends OutcomeUsingMiniMock {

private final String asciiGrid;

public TheGridShouldLookLike(String asciiGrid) {
this.asciiGrid = asciiGrid;
}

// ...

public void narrateTo(Renderer renderer) {
super.narrateTo(renderer);
renderer.renderAny(asciiGrid);
}
}

If your customer hasn't provided you with the text of a story, printing a Story will give you that text.

If the customer has provided you with story text, then hopefully printing the Story will look just the same.

--
Elizabeth Keogh
liz-IFekc9qy6S0WhyVFc8JwjA@public.gmane.org
http://www.livejournal.com/users/sirenian

headers

Dan North | 5 Feb 2007 22:59

Re: Maven repositories at Codehaus

Great stuff Mauro.

Can you document this on the website please?

Mauro Talevi wrote:
> Hi folks,
>
> the Maven repos have been created at Codehaus.  They are:
>
> - http://repository.codehaus.org/org/jbehave/ - this is for stable and 
> versioned releases, which is synched with Maven's Central Repo every 
> few hours.
> - http://snapshots.repository.codehaus.org/org/jbehave/ - for snapshots
>
> I've uploaded the latest stable and latest snapshot.
>
> Independently of the synching, you can use the Maven plugin by 
> configuring in your POM (typically your parent POM):
>
>    <pluginRepositories>
>         <pluginRepository>
>             <id>codehaus-plugin-repository</id>
>             <name>Codehaus Plugin Repository</name>
>             <url>http://repository.codehaus.org</url>
>         </pluginRepository>
>         <pluginRepository>
>             <id>codehaus-plugin-snapshot-repository</id>
>             <name>Codehaus Plugin Snapshot Repository</name>
>             <url>http://snapshots.repository.codehaus.org</url>
>             <snapshots>
>                 <enabled>true</enabled>
>             </snapshots>
>         </pluginRepository>
>     </pluginRepositories>
>
> If you are just using stable releases, the above configuration becomes 
> redundant after a few hours of the release, as the Central Maven Repo 
> is configured by default.   These are more useful if you are 
> developing and don't want to wait until the synch is done or are using 
> snapshot releases.
>
> To use the jBehave plugin in your project
>
>           <plugin>
>                 <groupId>org.jbehave</groupId>
>                 <artifactId>jbehave-maven-plugin</artifactId>
>                 <version>0.9.0</version>
>                 <executions>
>                     <execution>
>                         <phase>integration-test</phase>
>                         <goals>
>                             <goal>run</goal>
>                         </goals>
>                         <configuration>
>                             <behavioursClassName>
>                                 jbehave.AcceptanceBehaviours
>                             </behavioursClassName>
>                         </configuration>
>                     </execution>
>                 </executions>
>             </plugin>
>
> The run goal will verify all the behaviours specified by the 
> Behaviours class.
> At the moment, because Behaviours can encode multiple behaviour 
> classes, it is a single class that can be specified.  We can easily 
> extend it to a list, though.
>
> One thing that I would also like to add is the includes/excludes 
> patterns.
>
> Cheers
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

headers

Shane Duan | 6 Feb 2007 02:36

Re: Maven repositories at Codehaus

Sorry I forgot to mention that I updated it already.  I always have my
laptop with me when watching TV and there were nothing interesting on
that day.

On 2/5/07, Dan North <dan@...> wrote:
> Great stuff Mauro.
>
> Can you document this on the website please?
>
>
> Mauro Talevi wrote:
> > Hi folks,
> >
> > the Maven repos have been created at Codehaus.  They are:
> >
> > - http://repository.codehaus.org/org/jbehave/ - this is for stable and
> > versioned releases, which is synched with Maven's Central Repo every
> > few hours.
> > - http://snapshots.repository.codehaus.org/org/jbehave/ - for snapshots
> >
> > I've uploaded the latest stable and latest snapshot.
> >
> > Independently of the synching, you can use the Maven plugin by
> > configuring in your POM (typically your parent POM):
> >
> >    <pluginRepositories>
> >         <pluginRepository>
> >             <id>codehaus-plugin-repository</id>
> >             <name>Codehaus Plugin Repository</name>
> >             <url>http://repository.codehaus.org</url>
> >         </pluginRepository>
> >         <pluginRepository>
> >             <id>codehaus-plugin-snapshot-repository</id>
> >             <name>Codehaus Plugin Snapshot Repository</name>
> >             <url>http://snapshots.repository.codehaus.org</url>
> >             <snapshots>
> >                 <enabled>true</enabled>
> >             </snapshots>
> >         </pluginRepository>
> >     </pluginRepositories>
> >
> > If you are just using stable releases, the above configuration becomes
> > redundant after a few hours of the release, as the Central Maven Repo
> > is configured by default.   These are more useful if you are
> > developing and don't want to wait until the synch is done or are using
> > snapshot releases.
> >
> > To use the jBehave plugin in your project
> >
> >           <plugin>
> >                 <groupId>org.jbehave</groupId>
> >                 <artifactId>jbehave-maven-plugin</artifactId>
> >                 <version>0.9.0</version>
> >                 <executions>
> >                     <execution>
> >                         <phase>integration-test</phase>
> >                         <goals>
> >                             <goal>run</goal>
> >                         </goals>
> >                         <configuration>
> >                             <behavioursClassName>
> >                                 jbehave.AcceptanceBehaviours
> >                             </behavioursClassName>
> >                         </configuration>
> >                     </execution>
> >                 </executions>
> >             </plugin>
> >
> > The run goal will verify all the behaviours specified by the
> > Behaviours class.
> > At the moment, because Behaviours can encode multiple behaviour
> > classes, it is a single class that can be specified.  We can easily
> > extend it to a list, though.
> >
> > One thing that I would also like to add is the includes/excludes
> > patterns.
> >
> > Cheers
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> >    http://xircles.codehaus.org/manage_email
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--

-- 
Shane
http://www.shaneduan.com

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

headers

Mauro Talevi | 6 Feb 2007 13:16

Re: Maven repositories at Codehaus

Shane Duan wrote:
> Sorry I forgot to mention that I updated it already.  I always have my
> laptop with me when watching TV and there were nothing interesting on
> that day.
> 

Thanks.  I've now re-updated it, adding the new run-story goal.

I seem to have done something wrong in the formatting/indenting, but can't figure out what 

Can some wordpress expert have a look?

Cheers

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

headers

Shane Duan | 6 Feb 2007 17:30

Re: Re: Maven repositories at Codehaus

I think workpress is using Textile.  So you can probably check out
textile reference:

http://hobix.com/textile/

On 2/6/07, Mauro Talevi <mauro.talevi@...> wrote:
> Shane Duan wrote:
> > Sorry I forgot to mention that I updated it already.  I always have my
> > laptop with me when watching TV and there were nothing interesting on
> > that day.
> >
>
> Thanks.  I've now re-updated it, adding the new run-story goal.
>
> I seem to have done something wrong in the formatting/indenting, but can't figure out what 
>
> Can some wordpress expert have a look?
>
> Cheers
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--

-- 
Shane
http://www.shaneduan.com

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

headers

Elizabeth Keogh | 21 Feb 2007 13:55

Apologies, and another push for 1.0

Hi all,

Sorry there's not been much work done on JBehave over the last few weeks; illness distracted me. The doctor has replaced my immune system with a new one in pill form so hopefully we can get back on track.

Things I know that still need doing:

- Tidy up of the code base - I'd like to rename the runners and tasks with a little more consistency. "Run", particularly, I want to get rid of; I think more people will be interested in JBehave for the stories than the behaviours anyway.
- Ant StoryPrinterTask (should print all stories to a destination dir).
- Remove Cotta from the code base

Not much, really! Can you think of anything else? I don't know where the plugins are at the moment...

I'm just going to get on with these in the order above, if no one objects; please shout if you'd like to take any of them on.

Cheers,
Liz.

--
Elizabeth Keogh
liz-IFekc9qy6S0WhyVFc8JwjA@public.gmane.org
http://www.livejournal.com/users/sirenian

headers

Dan North | 21 Feb 2007 14:49

Re: Apologies, and another push for 1.0

Apologies from me too. My world is just a bit too frantic at the moment.

Once Liz (and volunteers?) has finished the snagging list below, I'll roll a 1.0 release, including IDEA and eclipse plugins.

Cheers,
Dan

Elizabeth Keogh wrote:

Hi all,

Sorry there's not been much work done on JBehave over the last few weeks; illness distracted me. The doctor has replaced my immune system with a new one in pill form so hopefully we can get back on track.

Things I know that still need doing:

- Tidy up of the code base - I'd like to rename the runners and tasks with a little more consistency. "Run", particularly, I want to get rid of; I think more people will be interested in JBehave for the stories than the behaviours anyway.
- Ant StoryPrinterTask (should print all stories to a destination dir).
- Remove Cotta from the code base

Not much, really! Can you think of anything else? I don't know where the plugins are at the moment...

I'm just going to get on with these in the order above, if no one objects; please shout if you'd like to take any of them on.

Cheers,
Liz.

--
Elizabeth Keogh
liz-IFekc9qy6S0WhyVFc8JwjA@public.gmane.org
http://www.livejournal.com/users/sirenian

Mon	Tue	Wed	Thu	Fri	Sat	Sun

			1	2	3	4
5	6	7	8	9	10	11
12	13	14	15	16	17	18
19	20	21	22	23	24	25
26	27	28

46	May 2013
67	April 2013
40	March 2013
31	February 2013
24	January 2013
80	December 2012
159	November 2012
81	October 2012
61	September 2012
106	August 2012
110	July 2012
30	June 2012
47	May 2012
109	April 2012
152	March 2012
114	February 2012
107	January 2012
196	December 2011
107	November 2011
51	October 2011
81	September 2011
65	August 2011
83	July 2011
96	June 2011
144	May 2011
152	April 2011
108	March 2011
100	February 2011
72	January 2011
81	December 2010
74	November 2010
135	October 2010
99	September 2010
28	August 2010
52	July 2010
107	June 2010
94	May 2010
102	April 2010
33	March 2010
75	February 2010
44	January 2010
104	December 2009
43	November 2009
81	October 2009
74	September 2009
25	August 2009
6	July 2009
22	June 2009
24	April 2009
14	March 2009
38	February 2009
37	January 2009
13	December 2008
29	November 2008
63	October 2008
27	September 2008
24	August 2008
68	July 2008
6	June 2008
21	November 2007
6	October 2007
22	September 2007
20	August 2007
89	July 2007
23	June 2007
21	May 2007
27	April 2007
112	March 2007
14	February 2007
39	January 2007
70	December 2006
53	November 2006