Mixing Cucumber with Test::Unit/Shoulda — GIANT ROBOTS SMASHING INTO OTHER GIANT ROBOTS
february 2009 by Vaguery
"We’ve been writing a “feature” for every new client request on that project – for each user-created ticket we handle, we create a .feature file (and include the ticket number in the feature title), and write steps for that request. This means that we have acceptance tests for all new client requests on that project. This approach may seem a little strange, but it’s been helpful, and we’re very happy with it so far. We’ll likely take a different approach if we use Cucumber on a project from scratch.
Now you have no excuse if your projects aren’t doing any kind of top-down testing, so get out there and write some acceptance tests!"
test-driven-development
TDD
behavior-driven-design
BDD
cucumber
shoulda
ruby
testing
agility
emergent-design
Now you have no excuse if your projects aren’t doing any kind of top-down testing, so get out there and write some acceptance tests!"
february 2009 by Vaguery
Copy this bookmark: