Yes that is nice because you know what files aren't really being used. That is asiming you tested everything that is being used! Sent via BlackBerry from T-Mobile
-----Original Message----- From: Scott Taylor <[EMAIL PROTECTED]> Date: Sun, 16 Sep 2007 15:45:34 To:rspec-users <rspec-users@rubyforge.org> Subject: Re: [rspec-users] [ANN] rspec_todo -- spec'ing backwards >> >> >> I agree with David (you can also look at the ZenTest suite, which has >> a similar tool). I haven't looked at the tool, but how about >> modifying it to create comments in the specs, somthing like this: >> >> # You haven't specified the behaviour of User#method1! >> # You haven't specified the behaviour of User#method2! >> >> Scott >> >> _______________________________________________ >> rspec-users mailing list >> rspec-users@rubyforge.org >> http://rubyforge.org/mailman/listinfo/rspec-users >> > > Why not use RCov? Seeing a bunch of red is a much bigger motivator > than a lame comment. Good point. Just out of curiosity - Have you noticed that rcov won't pick up all of the files in a Rails project unless there is an explicit spec file for it (or the class/model isn't called) ? Scott _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
