Cucumber testing is great for the high level stuff, especially when you want to get the non-technical users involved in writing stories about what the application should do. But if you're doing developer facing testing then development is slower than it needs to be because you have to write translations from pidgin english into test code. Getting that right is a pain, using other peoples canned examples requires using their assumptions about your code and application. Modifying their example translations takes time & so on. If someone else is paying it's a nice way to do things. You've got quasi-natural language scenarios you can sign off, protect your arse and get paid.
If you're writing code for yourself, and paying for your own time, then the extra layer of syntactical sugar just gets in the way. I now use test unit and Shoulda for most stuff, and mix it with WebRat for the integration testing. Writing the tests is faster, I understand the integration scenarios and because they're close to the actual code they make more sense to me than high level syntactically sugared stuff. I always write masses of unit tests for each model following the TDD philosophy. YMMV John Small -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
