Comments on: 12 Steps to Testing in Rails http://www.thirdbit.net/articles/2007/08/17/12-steps-to-testing-in-rails/ Reqs. Code. Docs. Done. Sun, 12 Oct 2008 10:46:34 +0000 http://wordpress.org/?v=2.2 By: Discover From Your Favorite Topic or Web Page: urlmarkr.org/ http://www.thirdbit.net/articles/2007/08/17/12-steps-to-testing-in-rails/#comment-1019 Discover From Your Favorite Topic or Web Page: urlmarkr.org/ Thu, 01 Nov 2007 16:08:46 +0000 http://www.thirdbit.net/articles/2007/08/17/12-steps-to-testing-in-rails/#comment-1019 <!--%kramer-ref-pre%-->[...] (ruby rubyonrails merb programming) Bookmark  [Discover] Steps to Testing in Rails | thirdbIT http://www.thirdbit.net/articles/2007/08/17/12-steps-to-testing-in-rails/ (testing tdd ruby advice) [...]<!--%kramer-ref-post%--> Kramer auto Pingback[…] (ruby rubyonrails merb programming) Bookmark  [Discover] Steps to Testing in Rails | thirdbIT http://www.thirdbit.net/articles/2007/08/17/12-steps-to-testing-in-rails/ (testing tdd ruby advice) […]

]]> By: Steve http://www.thirdbit.net/articles/2007/08/17/12-steps-to-testing-in-rails/#comment-593 Steve Sun, 19 Aug 2007 23:09:29 +0000 http://www.thirdbit.net/articles/2007/08/17/12-steps-to-testing-in-rails/#comment-593 I'd echo what mike said about at least looking at rSpec. It really has helped me think much more about what I'm trying to achieve with my tests/specs. I’d echo what mike said about at least looking at rSpec. It really has helped me think much more about what I’m trying to achieve with my tests/specs.

]]> By: mike http://www.thirdbit.net/articles/2007/08/17/12-steps-to-testing-in-rails/#comment-585 mike Fri, 17 Aug 2007 18:54:48 +0000 http://www.thirdbit.net/articles/2007/08/17/12-steps-to-testing-in-rails/#comment-585 Fantastic article. Great pep talk. The only point I differ on is exploring other testing tools. I was still not dilligent about writing tests after moving from .NET to Rails (where tests are "baked in") until I discovered RSpec. For some reason the syntax just clicked and writing tests no longer seemed like such a chore. I would suggest that you don't get wrapped up in autotest, heckle and other add-ons until you get comfortable at just writing tests. I'll admit that I still write most of my tests after the fact but I'm trying. Lord knows I'm trying. Maybe we can start a support group..."Hi, I'm Mike and I don't write tests for my code." Fantastic article. Great pep talk.

The only point I differ on is exploring other testing tools. I was still not dilligent about writing tests after moving from .NET to Rails (where tests are “baked in”) until I discovered RSpec. For some reason the syntax just clicked and writing tests no longer seemed like such a chore. I would suggest that you don’t get wrapped up in autotest, heckle and other add-ons until you get comfortable at just writing tests.

I’ll admit that I still write most of my tests after the fact but I’m trying. Lord knows I’m trying.

Maybe we can start a support group…”Hi, I’m Mike and I don’t write tests for my code.”

]]> By: Lori http://www.thirdbit.net/articles/2007/08/17/12-steps-to-testing-in-rails/#comment-584 Lori Fri, 17 Aug 2007 17:36:08 +0000 http://www.thirdbit.net/articles/2007/08/17/12-steps-to-testing-in-rails/#comment-584 Good advice, all of it. One more addition. It is inevitable that under the heat of a tight deadline, with project managers breathing down your neck about squeezing in one last feature, and testers reporting bugs that HAVE to be fixed for this iteration, you will find yourself in a position where it will be easy to fix a bug, but hard to write the test for it. Forgive yourself for being human, and skipping the test part. But don't forget to log yourself a bug/task to go back and write that test in a less pressured moment. Good advice, all of it. One more addition. It is inevitable that under the heat of a tight deadline, with project managers breathing down your neck about squeezing in one last feature, and testers reporting bugs that HAVE to be fixed for this iteration, you will find yourself in a position where it will be easy to fix a bug, but hard to write the test for it. Forgive yourself for being human, and skipping the test part. But don’t forget to log yourself a bug/task to go back and write that test in a less pressured moment.

]]>