sorry for the late response, filter malfuncfion :-/
CP server should obey standard configuration, so this is more of a Django
configuration issue, harder to fix as Django is not using logging yet.
If You are using twill, since https://github.com/Almad/django-sane-
testing/commit/2e96fc3785f7ff67fd80350aa20891bc5c43e9bf , You should see the
traceback as a part of failing test message.
As a hack, I would probably write a middleware with process_exception. I have
not written one myself, as I am mostly having either reproducable errors or I
am able to figure it out from traceback.
One trick I have been using is also to use
self.selenium.capture_entire_page_screenshot(filename) or
self.selenium.capture_screenshot(filename), which is helpful (wanted some
wrappers to be part of DST, but had no time for that yet).
It also depends - are You running tests with DEBUG set to True or False?
Almad