blob: f4edd324b3a4666f89ae6397b4d0028afa1c8cb4 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
To run Twisted tests:
make -C tests/twisted check-twisted
To run an individual Twisted test:
make -C tests/twisted check-twisted \
TWISTED_TESTS=dispatcher/create-at-startup.py
Debug information (the test's own log, and Mission Control's log)
is recorded in a subdirectory of tests-twisted whose name is based
on the test's name, like tests/twisted/tmp-dispatcher_create-at-startup_py.
The same tmp-* directory also contains the account data used in the test.
If the test fails, its output will be sent to stdout.
These directories are normally deleted after a test passes or is skipped,
and kept for analysis if it fails. Set the environment variable
MC_TEST_KEEP_TEMP to avoid deleting them.
To debug an individual test you can set one of the following env variable:
* MISSIONCONTROL_TEST_VALGRIND : to run Mission Control inside valgrind. The
report is added to missioncontrol.log. You'll probably also want
MC_TEST_KEEP_TEMP to keep the logs in tests/twisted/tmp-*, even when
tests passed.
* MISSIONCONTROL_TEST_REFDBG : to run Mission Control inside refdbg. The
report is written to refdbg.log. You can change
MISSIONCONTROL_WRAPPER to use an alternative refdbg and change
REFDBG_OPTIONS to set your own parameters. Example:
export MISSIONCONTROL_TEST_REFDBG=1
export MISSIONCONTROL_WRAPPER="/path/to/refdbg"
export REFDBG_OPTIONS="btnum=16"
* MISSIONCONTROL_WRAPPER="nemiver" : to run Mission Control inside the
graphical debugger nemiver. You'll be able to set up breakpoints; then hit
the "continue" button to launch Mission Control.
|
