Ruby on Rails Friday, November 30, 2012

On Fri, Nov 30, 2012 at 12:13 PM, Robert Buck <lists@ruby-forum.com> wrote:
> It would be nice if the test framework for rails AT LEAST spit out the
> line where this happened.

You are blaming Rails for a problem created by another person?

>
> So, without any useful information from the test suite, what I wanted to
> do was to find out blow by blow when bad things happen so I can
> correlate it to the step-wise actions in a debugger, and so trace WHERE
> the bad thing is happening. But no, the test suite eats all STDOUT and
> only spits it out after all tests have completed.

There is plenty of useful information, that is what logs are for, and
a test log is kept, try looking in log/test.log which will have all
that in there from start to finish of each request.

> Does anyone know how to get Rails to emit all stdout immediately instead
> of buffering it until after ALL tests have completed?

With RSpec use fail fast.

--
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment