[rspec-devel] Stories vs. examples

Dan North tastapod at gmail.com
Wed Nov 7 10:28:52 EST 2007

Exactly. The behaviour description works in conjunction with other material
that help with the non-behavioural aspects, like screen layouts or design
guidelines. You would probably have a lo-fi mock-up of the login screen
(just a drawing) with the User and Password fields and Login button
labelled. Then the story would refer to those elements.

On 11/7/07, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Nov 7, 2007 2:04 AM, Matthijs Langenberg <mlangenberg at gmail.com> wrote:
> > Would this also mean that the guy writing the story is defining the
> > functional part of the GUI?
> > Since it's the most outer layer of the system, would that be described
> in a
> > story first?
> > Like: "Given a user and a form with a button, when a user clicks the
> button,
> > then the world should come to an end."
> There should likely be both interaction stories like that AND business
> rule stories, like the one Dan uses in
> http://dannorth.net/2007/06/introducing-rbehave. If every story takes
> you through every step, they all become too big IMO.
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/rspec-devel/attachments/20071107/bbb8cbc8/attachment.html 

More information about the rspec-devel mailing list