Ignore:
Timestamp:
2013-02-21T13:16:26Z (11 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
06eef80
Parents:
e4f5ca8 (diff), 9754c2f (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Merge from vmiklos. Mostly Skype stuff and further deprecating a nogaim
function.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • protocols/skype/HACKING

    re4f5ca8 r12f500f  
    18184) irssi
    1919
     20
    2021== Tests
    2122
    22 The plugin is tested with a mocked IRC client and a mocked skyped. To add a new
    23 test, the following steps are necessary:
     23The plugin is tested with a mocked IRC client and a mocked skyped.
     24
     25=== Requirements
     26
     27Python pexpect module is required to run the tests.
     28
     29To run tests with bitlbee built in a development tree and not (the one)
     30installed in the system (e.g. /usr), make sure to specify --plugindir= option to
     31./configure script during the build process:
     32
     33bitlbee% ./configure --skype=1 --plugindir="$(realpath .)"
     34
     35Otherwise bitlbee will try to load skype.so (among other things) from /usr/lib,
     36which is probably not what you want to test, or produce "Unknown protocol"
     37error.
     38
     39=== Running
     40
     41Tests can be run by running test.py script in this ("protocols/skype")
     42directory.
     43
     44For more control over how/which tests are being run from there, use "python -m
     45unittest" command:
     46
     47bitlbee/protocols/skype% python -m unittest test
     48bitlbee/protocols/skype% python -m unittest -f test
     49bitlbee/protocols/skype% python -m unittest test.Test.testMsg
     50
     51If bitlbee crashes during tests with SIGSEGV (segmentation fault), it's likely
     52that there is some problem with skype.c plugin.
     53To get a backtrace of such crash, use:
     54
     55bitlbee/protocols/skype% ATTACH_GDB=true python -m unittest test.Test.testMsg
     56
     57Example shows running "testMsg" test with gdb attached to bitlbee, which will
     58produce full backtrace in "t/gdb-<pid>.log" files (see pid in pexpect error
     59output of the test).
     60
     61=== Adding new tests
     62
     63To add a new test, the following steps are necessary:
    2464
    25651) Add a new -skyped.mock file: just do the test manually, copy&paste the
Note: See TracChangeset for help on using the changeset viewer.