An even simpler cucumber tagging system
August 11th, 2009
Release versions are one way to handle your tags, but as Ian pointed out, really for most people (and perhaps me) it's excessive. I'd go further to say it's superfluous, clumsy and overly bureaucratic, all in all not very agile. Not bad for something I came up with!
While this sort of thing will take some iterating and is really down to how you arrange your work, the following simple scheme may provide a good foundation.
Tags: @stable
And that's it. Write your features, when they pass mark them as @stable, and when you want to do a regression test run it against all your @stable features.
cucumber --tags @stable -f progress features
You could even rake or alias it for added comfort.
Tags: @stable @wip @pending
In the above an untagged feature can be a work in progress, or left pending for later. While this is enough for regression testing, tagging these features as well has some workflow benefits. It's your metadata, why not use it.
Take for example the feature you quickly sketched out over lunch a week ago to flesh out later, where was it again? If it were tagged you could do a project search (TextMate) or equivalent to find the elusive text. Why waste Time looking when you can Search?™
Tag it your way
One of the nice things about these tags is you can build on this scheme quite easily, by domain, release number, external resource connectivity, or whatever you like.
This is inherently YMMV, and it should be interesting to see what other people find useful.
Sorry, comments are closed for this article.