[rspec-users] features and form filling - going declarative?
apremdas at gmail.com
Fri Nov 7 10:44:58 EST 2008
+1 for abstract and concrete as it gives an indication of what the
story should contain i.e.
I should get an error
I should be told my email must have an @ sign and be ...
2008/11/7 David Chelimsky <dchelimsky at gmail.com>:
> On Fri, Nov 7, 2008 at 9:58 AM, David Chelimsky <dchelimsky at gmail.com> wrote:
>> On Fri, Nov 7, 2008 at 9:54 AM, Matt Wynne <matt at mattwynne.net> wrote:
>>> One technique is to have a single noisy 'declarative' scenario that
>>> explicitly walks around filling things in, then all the rest use more
>>> 'imperative' style steps where most of the detail is buried away.
>> You've got those backwards :)
>> declarative: when I fill in the form correctly
>> imperative: when I enter "David" in the "Name" field ....
> Although - maybe we need to reconsider this naming, because you could
> argue that either are declarative, whereas imperative, meaning
> important/urgent, doesn't really convey the explicit nature. I think
> abstract/concrete could work. Maybe general/specific.
> Other ideas?
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-users