Just wanted to thank everyone for their replies. I actually recall
that thread now about imperative vs. declarative. I've just re-read
Ben's post along with some of the linked content off the post and now
and I feel a bit more comfortable with the direction I was going in. I
personally tend
Ben has a good post on the declarative vs imperative styles here:
http://www.benmabey.com/2008/05/19/imperative-vs-declarative-scenarios-in-user-stories/
I totally agree with Josh, and indeed wrote out my own version of his login
example before realizing I should probably read his post before repl
I find that the _first_ example of some functionality should be
imperative (say specifically how to achieve something step by step)
and subsequent mentions of the same functionality should be more
declarative (say in abstract terms what to achieve, but spare the step
by step details). For me, this
On 17 Feb 2009, at 20:27, Lenny Marks wrote:
Forgive the long post, just looking for input/advice/alternate
opinions..
Like many I think that going through the exercise of framing user
requests in Cucumber terms(Features, Scenarios..) really helps
facilitate necessary conversations and a
On Feb 17, 2009, at 3:27 PM, Lenny Marks wrote:
Forgive the long post, just looking for input/advice/alternate
opinions..
Like many I think that going through the exercise of framing user
requests in Cucumber terms(Features, Scenarios..) really helps
facilitate necessary conversations an
Forgive the long post, just looking for input/advice/alternate
opinions..
Like many I think that going through the exercise of framing user
requests in Cucumber terms(Features, Scenarios..) really helps
facilitate necessary conversations and avoid time wasted implementing
the wrong thing(
