Hi Eric.
The initial text file should just be used to bootstrap the process -
i.e. to generate the initial story class stubs. After that, you can use
the story runner to render the stories again, which will give you your
round-trip. As Liz suggests, you can do this as part of your build so
th
Hi Eric,
There's an Ant task for printing stories which I like to run as part of
the build. This keeps them in sync with the code, then I check them in.
Cheers,
Liz.
--
Elizabeth Keogh
[EMAIL PROTECTED]
http://sirenian.livejournal.com
http://jbehave.org
Eric Lewin <[EMAIL PROTECTED]> wrote on
Hi Mauro,
Mauro Talevi wrote:
I've applied the patches you provided and published a snapshot release.
Please try it out and let us know if you still experience problems.
I've left http://jira.codehaus.org/browse/JBEHAVE-88 open with a
comment/question for you.
You can close JBEHAVE-88.
After
Eric,
apologies for the long wait - Real Work(TM) got in the way :-)
Please use http://jira.codehaus.org/browse/JBEHAVE to attach any patch.
Anyway, I've fixed the code locally. If you like I could submit it. Is
a patch to a new Jira issue the best way to contribute?
yes please
I've appl
Eric Lewin wrote:
Hi,
I prefer to discuss the stories/scenarios with my customer before
coding, so I've rewritten the StoryGeneratorSpike so that it works as
described in "feature suggestion #2" further down.
Are you interested in that code?
Sure - I understand your point of view and it's
> > ***CodeGenerator (I know, it is in the sandbox, but it gets
distributed
> > ;O):
TODO: remove stuff that shouldn't be distributed from the build. :D Thanks
for that.
Cheers,
Liz.
--
Elizabeth Keogh
[EMAIL PROTECTED]
http://sirenian.livejournal.com
http://jbehave.org
Hi,
Mauro Talevi wrote:
Hi Eric
Eric Lewin wrote:
Hi!
I was thinking that starting with JBehave would be something like this:
1. writing story text files with the customer
2. Generating the code for givens, event and outcomes with
Ensure.pending()
3. Run the story textfile
4. Implement some
Hi Eric
Eric Lewin wrote:
Hi!
I was thinking that starting with JBehave would be something like this:
1. writing story text files with the customer
2. Generating the code for givens, event and outcomes with Ensure.pending()
3. Run the story textfile
4. Implement some givens, event and outcomes
