blob: bc617405945db381ce039e5e65c11d5c592e4dd4 (
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
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
|
To run all tests:
make check
or with coverage info:
./configure --enable-compiler-coverage
make lcov-check
== C tests ==
To run all C tests (assuming the current directory is $top_srcdir):
make -C tests check-TESTS
To run an individual test:
make -C tests check-TESTS TESTS=test-handles
To run tests under Valgrind:
make -C tests check-valgrind
To run an individual test under Valgrind:
make -C tests check-valgrind TESTS=test-handles
== Twisted tests ==
To run all Twisted tests:
make check-twisted
To run an individual Twisted test:
make -C tests/twisted check-twisted TWISTED_TESTS=test-connect.py
or:
cd tests/twisted
sh tools/with-session-bus.sh --config-file=tools/tmp-session-bus.conf \
-- python test-connect.py
To run with debug information:
make -C tests/twisted check-twisted TWISTED_TESTS=test-connect.py \
CHECK_TWISTED_VERBOSE=1
or:
cd tests/twisted
sh tools/with-session-bus.sh --config-file=tools/tmp-session-bus.conf \
-- python test-connect.py -v
To debug an individual test you can set one of the following env variable:
* GABBLE_TEST_VALGRIND : to run Gabble inside valgrind. The report is
added to tools/gabble-testing.log.
export GABBLE_TEST_VALGRIND=1
* GABBLE_TEST_REFDBG : to run Gabble inside refdbg. The report is written
to tools/refdbg.log. You can change GABBLE_WRAPPER to use an alternative
refdbg and change REFDBG_OPTIONS to set your own parameters. Example:
export GABBLE_TEST_REFDBG=1
export GABBLE_WRAPPER="/path/to/refdbg"
export REFDBG_OPTIONS="btnum=16"
* GABBLE_WRAPPER="nemiver" : to run Gabble inside the graphical debugger
nemiver. You'll be able to set up breakpoints; then hit the "continue"
button to launch Gabble.
|