On 13 Dec 2008, at 20:58, Steve Molitor wrote:
What's the best way to handle a requirement that shows up as a sub-
requirement requirement in other features? For example let's say
users can enter dates in various forms throughout my application.
There is one set of global rules
Thanks -- that gets me closer. Here's an example. Let's say I have two
features, 'Create new patient' and 'Create new incident'. To create a new
patient you have to enter a valid birth date. To create a new patient you
must enter a valid birth date. To create a new incident you must enter a
On 9 Dec 2008, at 09:43, aslak hellesoy wrote:
Hi folks,
Cucumber has become popular a lot quicker than I had anticipated.
Still, with its plain text nature it is still limited to programmers
(in most teams).
I want to close the gap between customers/product owners/business
analysts and
Hi Steve,
I likely would only write two scenarios, one for a valid date and one
for an invalid one. Then I would write object-level specs to determine
what a valid date is. Extract this to a validator that you can reuse
throughout your model.
If it's important that you write features for each
Why not make a web client that manipulates git based projects in the
background? I've been messing around with Grit and doing things like
this lately for http://rdocul.us a site I run and it is very easy to do.
If everything is in a standard location you could just add a project via
an
I've added Given/When/Then as valid methods to take regexp as an
argument to my Ruby.tmbundle, if its helpful (via bjeanes)
http://github.com/drnic/ruby-tmbundle
Commit:
http://github.com/drnic/ruby-tmbundle/commit/2cff40d43dd65aad3d8cd050654823db6d7517cb
Cheers
Nic
On Nov 15, 2:13 am, Ashley
