I am using Capybara in combination with rspec for integration testing of rails apps. I would like any errors (routing errors, errors in a controller, anything) generated during a test to be printed the same as "puts" statements in rspec''s output. Is this possible? Additionally, is this a reasonable idea, or am I just being silly?
On Dec 16, 2011, at 8:46 AM, LeeQ wrote:> I am using Capybara in combination with rspec for integration testing > of rails apps.Even though you are using Capybara, they are still just specs. No reason why "puts" won''t work.> > I would like any errors (routing errors, errors in a controller, > anything) generated during a test to be printed the same as "puts" > statements in rspec''s output. Is this possible? Additionally, is this > a reasonable idea, or am I just being silly? > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users
Puts does work. That''s not what I''m looking for. I want all error messages (like `undefined local variable or method `junk'' for...` ) to show up in my rspec out put in *the same way as* `puts`. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20111222/5486b190/attachment.html>
On Dec 22, 2011, at 8:25 AM, LeeQ wrote:> Puts does work. That''s not what I''m looking for. > > I want all error messages (like `undefined local variable or method `junk'' for...` ) to show up in my rspec out put in the same way as `puts`. > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-usersSo basically you want the exception message to display in the output, but then have things "continue on" like it *wasn''t* an exception? I don''t see the point in that, but you could do it with `rescue`. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20111222/ca38f1fb/attachment.html>
Ah, I see what you are saying. But no, I still want the exception to act like an exception. My problem is that I''ll have a test fail for reasons unknown, and I then I need to open the test logs to find the exception. I''d like those exceptions to show up in my test output so I don''t have to dig for them. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20111222/26a4ea79/attachment-0001.html>
On Dec 22, 2011, at 11:33 AM, LeeQ wrote:> Ah, I see what you are saying. But no, I still want the exception to act like an exception. My problem is that I''ll have a test fail for reasons unknown, and I then I need to open the test logs to find the exception. I''d like those exceptions to show up in my test output so I don''t have to dig for them._______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-usersOkay I see what you''re talking about now. Take a look at this: https://github.com/jnicklas/capybara/issues/358
On Dec 22, 2011, at 12:33 PM, LeeQ <leequarella at gmail.com> wrote:> Ah, I see what you are saying. But no, I still want the exception to act like an exception. My problem is that I''ll have a test fail for reasons unknown, and I then I need to open the test logs to find the exception. I''d like those exceptions to show up in my test output so I don''t have to dig for them. > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-usersYou need to configure the logger to log to standard out. Check out this link & modify as appropriate for your Rails version: http://stackoverflow.com/questions/4800032/how-to-change-the-rails-logger-to-use-standard-out-from-rake-tasks-rails2 Pat