Another sample

[Eric Lefevre-Ardant]

Hi guys,

I finally wrote up an actual example out of our own code. The previous own had been ad-libbed with the help of Andrew. This one is actually in our codebase.

Check it out: https://gist.github.com/667806

Any comments welcome

Eric

[Douglas Squirrel]

Hi Eric!

 

Thanks for all your work in trying out Narrative. Will be very interested to see how you use it in future. Any stumbling blocks to adoption that we could help with (besides the Throwable issue)?

 

thanks again

squirrel

[Eric Lefevre-Ardant]

well, so far, most of the critics I got from my colleagues and on Twitter are related to the number of helper classes & methods that must be written.

If anything can be done to lower that number, it would be great. I don't see how, though.

[Douglas Squirrel]

Thanks Eric. As you argued in your gist excerpt, we find that once you have invested the energy in creating the helpers, they pay off in the ease of writing future tests. So it might make sense to try it first in a new and rapidly-changing area, where you will get a rapid return on the investment by making new readable tests easy to create, rather than an old and stable bit of code where you write new tests rarely.

 

Please do let us know how it goes at Algodeal and whether you find Narrative useful over time.

 

Thanks

Squirrel

[Andrew Parker]

Yeah, there do need to be a fair number of things written to support doing these things. I've found that usually the number is not the problem, but the verbosity that java requires for them. As Squirrel points out the investment put into writing them starts to reduce over time, but of course never quite reaches zero. The number that needs to be written is of course determined by the complexity of the domain that you are working in and the number actions that can be performed on the domain concepts. If the majority of development work is around tweaking existing functionality then you get a good amount of reuse of existing Actions. If, however, you find yourself quickly growing the domain then you'll probably find yourself refactoring the Actions and adding new ones much more.

Andy
________________________________________
From: narrati...@googlegroups.com [narrati...@googlegroups.com] On Behalf Of Douglas Squirrel [douglas....@youdevise.com]
Sent: Tuesday, November 09, 2010 5:27 PM
To: narrati...@googlegroups.com
Subject: RE: Another sample

Thanks Eric. As you argued in your gist excerpt, we find that once you have invested the energy in creating the helpers, they pay off in the ease of writing future tests. So it might make sense to try it first in a new and rapidly-changing area, where you will get a rapid return on the investment by making new readable tests easy to create, rather than an old and stable bit of code where you write new tests rarely.

Please do let us know how it goes at Algodeal and whether you find Narrative useful over time.

Thanks
Squirrel

From: narrati...@googlegroups.com [mailto:narrati...@googlegroups.com] On Behalf Of Eric Lefevre-Ardant
Sent: 09 November 2010 15:54
To: narrati...@googlegroups.com
Subject: Re: Another sample

well, so far, most of the critics I got from my colleagues and on Twitter are related to the number of helper classes & methods that must be written.
If anything can be done to lower that number, it would be great. I don't see how, though.

On 8 November 2010 23:24, Douglas Squirrel <douglas....@youdevise.com<mailto:douglas....@youdevise.com>> wrote:
Hi Eric!

Thanks for all your work in trying out Narrative. Will be very interested to see how you use it in future. Any stumbling blocks to adoption that we could help with (besides the Throwable issue)?

thanks again
squirrel