When TextTest doesn't do what you expect it to, the best way
to find out why is usually to enable its own internal logging mechanism
for the relevant aspect of the functionality. This is enabled
primarily by using the “Write TextTest diagnostics”
check box under “Running” and “Advanced”
tabs in the static GUI (-x option from the command line).
TextTest uses log4py
for its own logging. To configure which loggers will output and
where they will do so, you will need to edit the log4py
configuration file. The location of this is set by the field
“Configure self-diagnostics from”, in the same
location as above (-xr on command line). It defaults to
<your personal configuration directory>/log/log4py.conf (see here
for where to find your personal configuration directory).
An initial file with everything disabled is provided with the TextTest source in
the "log" subdirectory, so you should start by copying this file to the above location.
You can then open this file and look at the various loggers
in that file and enable any that seem to be related to your
problem, generally by changing the “LogLevel” to
“Normal” for it. Most loggers by default write a
file alongside the log4py.conf file in the location above, but of course you can
configure it to write anywhere you like, either via the file
itself or from the static GUI tab given above.
(If the above options are not set, TextTest will find the configuration file from
the variable TEXTTEST_LOGCONFIG and the directory to write to from TEXTTEST_DIAGDIR,
but you probably won't need to set these variables, they're mainly for the self-tests)
Unfortunately Python doesn't have a native way to do this, and "pstack" and "strace" are
rather limited when it comes to Python. TextTest has its own mechanism, whereby
sending it SIGQUIT will cause it to write out the current stack.
It's time to mail the TextTest mailing list at sourceforge
. We should be able to respond within a day or so.