Documentation for 3.15
Other versions: trunk  3.27  3.26  3.25  3.24  3.23  3.22  3.21  3.20  3.19  3.18  Older...

Troubleshooting: using TextTest's internal logging
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 now uses the standard Python logging module for its internal logging. To configure which loggers will output and where they will do so, you will need to edit the logging 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/logging.debug (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 uncommenting the "level" and "args" lines in the relevant section. Most loggers by default write a file alongside the logging.debug 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.
There also exist default files for batch mode, the console interface and the GUI. If you wish to enable different logging for any of these modes "permanently", you can just do the same thing, i.e. copy them to your personal configuration directory and edit the copy there.
(If the above options are not set, TextTest will find the personal logging directory from the environment variable TEXTTEST_PERSONAL_LOG, but you probably won't need to set this variable, it's mainly for the self-tests)
Some hints / examples:
  • My environment files don't do what I want!“ : enable “read environment”
  • My test data isn't found!“ : enable “prepare writedir”
  • My run-dependent text isn't filtering as I want!” : enable “run dependent text”
  • I want to see the generated command line” : enable “run test”
Getting a Python stack out if TextTest is hanging (on UNIX)
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.
If you're still stuck...
It's time to mail the TextTest mailing list at sourceforge. We should be able to respond within a day or so.

Last updated: 05 October 2012