You can always run individual unit tests manually to determine which
one is causing the problem:
eg: ruby test\unit\<testname>.rb
Do this for each unit test in turn until you find the culprit.
On Nov 14, 8:32 am, "Eric Lin"
<eylinl...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> I have a unit test that seems to be taking a long time (~ 2 minutes),
> but with the "dot dot dot" display, I don''t know which
one it is.
> I''ve tried "rake test --trace", but that only increases
the verbosity
> of the setup phase. Is there a way for "rake test" to display
the
> test that''s running instead of just dots?
>
> Thanks,
> Eric
--~--~---------~--~----~------------~-------~--~----~
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---