Changeset 3e23850 for protocols/skype/HACKING

Timestamp:

2013-02-11T12:56:03Z (11 years ago)

Author:

Miklos Vajna <vmiklos@…>

Branches:

master

Children:

5a0ffa2

Parents:

7e5b4bd

git-author:

Mike Kazantsev <mk.fraggod@…> (11-02-13 12:56:03)

git-committer:

Miklos Vajna <vmiklos@…> (11-02-13 12:56:03)

Message:

skype: add ATTACH_GDB env flag, extend hacking instructions with info on pexpect/gdb

File:

• protocols/skype/HACKING (modified) (2 diffs)

protocols/skype/HACKING

@@ -18 +18 @@
 4) irssi
 
+
 == Tests
 
 The plugin is tested with a mocked IRC client and a mocked skyped.
+
+=== Requirements
+
+Python pexpect module is required to run the tests.
 
 To run tests with bitlbee built in a development tree and not (the one)
@@ -31 +36 @@
 which is probably not what you want to test, or produce "Unknown protocol"
 error.
+
+=== Running
+
+Tests can be run by running test.py script in this ("protocols/skype")
+directory.
+
+For more control over how/which tests are being run from there, use "python -m
+unittest" command:
+
+bitlbee/protocols/skype% python -m unittest test
+bitlbee/protocols/skype% python -m unittest -f test
+bitlbee/protocols/skype% python -m unittest test.Test.testMsg
+
+If bitlbee crashes during tests with SIGSEGV (segmentation fault), it's likely
+that there is some problem with skype.c plugin.
+To get a backtrace of such crash, use:
+
+bitlbee/protocols/skype% ATTACH_GDB=true python -m unittest test.Test.testMsg
+
+Example shows running "testMsg" test with gdb attached to bitlbee, which will
+produce full backtrace in "t/gdb-<pid>.log" files (see pid in pexpect error
+output of the test).
+
+=== Adding new tests
 
 To add a new test, the following steps are necessary: