rspec users - Feb 2009 - Best way of writing fetaures for a wizard

Hi everyone, I am Lucas and I am starting to use cucumber in project.

I need to write  a scenario that is little bit complex.

Lets suppose I have a Thing and then I need to advance that Thing through 4
stages (something like ''import'',
''validation'', ''authorization'',
''export'').
Every stage is a special action/post/request with different outcomes, but
the presentation is the same every time, just changing a few labels and
buttons.
But the problem is that for the user/customer this process is named
"Authorization". He doesn''t care about the stages.

What I mean is that the customer only sees one scenario, while I see 4.
What Is the proper way to do this kind of multi-action/complex-process?


Well, any thoughts we''ll be very appreciated.
Thanks in advance.
-- 
Lucas Florio
Developer
----
Personal: http://www.lucasefe.com.ar/
Development: http://www.drivendevelopment.com.ar/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/rspec-users/attachments/20090211/628709b7/attachment.html>

On 11 Feb 2009, at 09:38, Lucas Florio wrote:
> Hi everyone, I am Lucas and I am starting to use cucumber in project.
>
> I need to write  a scenario that is little bit complex.
>
> Lets suppose I have a Thing and then I need to advance that Thing  
> through 4 stages (something like ''import'',
''validation'',
> ''authorization'', ''export'').
> Every stage is a special action/post/request with different  
> outcomes, but the presentation is the same every time, just changing  
> a few labels and buttons.
> But the problem is that for the user/customer this process is named  
> "Authorization". He doesn''t care about the stages.
>
> What I mean is that the customer only sees one scenario, while I see  
> 4.
> What Is the proper way to do this kind of multi-action/complex- 
> process?
Does this help?
http://blog.mattwynne.net/2008/11/14/dry-up-your-cucumber-steps/

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com

On Wed, Feb 11, 2009 at 3:38 AM, Lucas Florio <lucasefe at gmail.com>
wrote:
> Hi everyone, I am Lucas and I am starting to use cucumber in project.
>
> I need to write  a scenario that is little bit complex.
>
> Lets suppose I have a Thing and then I need to advance that Thing through 4
> stages (something like ''import'',
''validation'', ''authorization'',
''export'').
> Every stage is a special action/post/request with different outcomes, but
> the presentation is the same every time, just changing a few labels and
> buttons.
> But the problem is that for the user/customer this process is named
> "Authorization". He doesn''t care about the stages.
>
> What I mean is that the customer only sees one scenario, while I see 4.
> What Is the proper way to do this kind of multi-action/complex-process?
If you see Cucumber as customer facing and RSpec as developer facing
(as I do), then you''d want one scenario in Cucumber and then the
details in RSpec.

That make sense?

Cheers,
David
> Well, any thoughts we''ll be very appreciated.
> Thanks in advance.
> --
> Lucas Florio
> Developer
> ----
> Personal: http://www.lucasefe.com.ar/
> Development: http://www.drivendevelopment.com.ar/
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>