On 11/20/12, Ryan Ollos <rjol...@gmail.com> wrote: > On Tue, Nov 20, 2012 at 2:11 PM, Ryan Ollos <rjol...@gmail.com> wrote: > >> [...] >> >>> You >>> should use the log in functional tests and anywhere you have access to >>> an environment (<= indeed if that's the case those will be functional >>> tests already ;) . >> >> >> I don't follow. How does this help me debug a unit test? >> >> > Nevermind my comment. I see now that you were just making a side comment > about functional tests, which I misread as somehow being a comment about > unit tests, but in a way that I couldn't understand. >
That suggestion is similar to Ethan's , yes . They both consist in using Python logging infrastructure , that way you could either send msgs to stdout or a file and then «tail -f» it . If you are lazy (jftr *LIKE ME* :P ) and one environment is handy inside test method body , just reuse it and «tail -f» ./log/trac.log file of the disposable environment used for testing purposes. ;) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
