Thanks, Fred. I don't know if this is a mini-test thing or what. But having dots show instead of test names is annoying. Do you know of a way to completely disable that behavior.
For example, this morning I am trying to diagnose a "socket is broken" issue. What I really need to know is what test was executing immediately before the first of these. I really need a full log of all output blow by blow. I will try disabling the fixtures. Should I consider looking elsewhere too? Bob Frederick Cheung wrote in post #1087528: > On Dec 2, 9:21am, Robert Buck <[email protected]> wrote: > >> happen so that you can immediately add breakpoints to the sources at the >> - no unbuffered output, and it eats my C extension trace info (printf) > You do normally get those. I seem to recall that logging (and perhaps > stdout) is silenced during fixture insertion because normally it > creates a lot of noise. You could try hobbling that silencing - all > the code relating to fixtures is in a file called fixtures.rb, if my > memory correct. > You should also be getting backtraces but if the exception is being > throw outside of the test case itself, weird stuff can happen (I've > had similar experiences with rspec in that sort of scenario) and it > ends up being handled differently to a normal test failure. > > >> - very little documentation in the README or RUNNING TESTS doc for folks >> authoring an adapter (few to none of the necessary hooks are documented) >> > > You can usually find some knowledgable people on #rails-contrib > although writing database adapters from scratch isn't something that > many have done. > > > Fred -- Posted via http://www.ruby-forum.com/. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
