Elizabeth Keogh wrote:
Sorry, removing the name "Run", not the class - I'd like it to be called
BehaviourRunner.
Yep - that's great!
> Also, apart from Run, what runners did you have in mind for renaming?
>
> > - Ant StoryPrinterTask (should print all stories to a destination dir).
There's a BehaviourRunnerTask that doesn't seem to be used at the
moment. I think the command line runner is more flexible (we can fork in
future, for instance) and I would like to keep that. Can we remove this
and rename the other tasks?
Fine with me.
Our Ant tasks are currently called "JBehave<Something>Task". I'd like to
get rid of the "JBehave" on the class names; the package namespaces them
anyway. So we would have:
- BehaviourRunnerTask (but not the current BehaviourRunnerTask)
- StoryRunnerTask
- StoryPrinterTask
Yep - that's the same convention I use for the Maven Mojos.
> I'd like to add equivalent functionality to maven plugin.
> Let's agree on what the plugins/task should provide:
> - run behaviours in a Behaviours class (which can consist of many
behaviours)
> - run story
> - print story
That gives me everything I (as JBehave user) need for both the Hellbound
project and the Sudoku solver I'm writing at the moment.
I've added:
- StoryLoader (as was noted in TODO)
- Refactored StoryPrinter to have StoryLoader and Renderer as injectable deps.
- Added StoryPrinterMojo (Maven plugin)
The StoryPrinterTask should be simple variant of StoryRunnerTask.
Note that I've removed the StoryPrinter main method - as the deps are in their own right buildable
in different ways.
I've not added any more behaviour tests - but I have added an end-to-end integration test via maven
plugin.
I'd like to add a couple more behaviour tests before the release.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
