mirror of
https://gitlab.freedesktop.org/libinput/libei.git
synced 2025-12-30 09:30:09 +01:00
7115e9c4c8
DBusMock is unittest based and the documentation points users to that approach. That approach is limiting however because we can't use all pytest features (see [1]). Luckily, the parent class in dbusmock doesn't really do much so we can emulate the functionality ourselves - all we need to do is call the same setUp/tearDowns and be done with it. This means we can move the dbus-monitor and mainloop handling into fixtures too which makes the code a fair bit nicer to read. [1] https://docs.pytest.org/en/7.1.x/how-to/unittest.html#pytest-features-in-unittest-testcase-subclasses |
||
|---|---|---|
| .. | ||
| templates | ||
| buildtest.c | ||
| buildtest.cc | ||
| conftest.py | ||
| eierpecken.c | ||
| eierpecken.h | ||
| eiproto.py.tmpl | ||
| meson.build | ||
| test-ei-device.c | ||
| test-ei-seat.c | ||
| test-ei.c | ||
| test-eis.c | ||
| test-main.c | ||
| test_oeffis.py | ||
| test_protocol.py | ||
| test_scanner.py | ||
| unit-tests.c | ||