search for: writersbeat

My problem has been listed here: http://railsforum.com/viewtopic.php?pid=25439#p25439 Don''t think it would be required to completely re-type it here :) Thanks! -- -Daniel Fischer http://danielfischer.com - Geek Blog http://abigfisch.com - Portfolio http://writersbeat.com - Writing Community

....rb" "spec/models/user_spec.rb" "spec/models/vote_spec.rb" --options "/Users/sparta/Projects/work/idastudios/ff/config/../spec/spec.opts" failed (See full trace by running task with --trace) Anyone have an idea what the heck is going on? Thanks, Daniel -- www.writersbeat.com www.danielfischer.com

...I want to be able to rcov all of "my" code, so where would I put this, in the regular Rakefile in the app directory? That doesn''t make much sense though, does it? (Questioning because the syntax id different). Anyway, I''m confused, and I could use help, thanks! -- www.writersbeat.com www.danielfischer.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20070525/40733570/attachment-0001.html

...test this functionality by seeing if I get redirected if I hit that page, but what if I actually want to be logged in, so I can test to see if the edit action is working? Any input on this? Thanks. -- -Daniel Fischer http://danielfischer.com - Geek Blog http://abigfisch.com - Portfolio http://writersbeat.com - Writing Community

Hey, Sorry for so many questions - I''m really bad at this right now. I''m trying to cover the following code w/ rspec def index if params[:user_id] @user = User.find(params[:user_id]) @messages = @user.messages end end So basically what I''m doing is listing all the messages for a user, provided there is an id parameter. describe

On 5/28/07, David Chelimsky <dchelimsky at gmail.com> wrote: > The behaviour you''re trying to describe is that the User should > require that passwords bear certain qualities - in this case a length > between 5 and 40. So you need to ask yourself how the User should > behave when this requirement is violated, and then specify that it > behaves that way. > >