{"push_id":1653796032,"size":2,"distinct_size":2,"ref":"refs/heads/feature/DBUS-15","head":"4a1408c6e230f3a082160acf1e8014b5b8c12602","before":"8fbb73aeb348f8a6f188f50e894555adab0b2f73","commits":[{"sha":"9e818dafb4067b3540502aed833b2d8cca1f4e3e","author":{"name":"elbenfreund","email":"41fd8290700e741bcbc5427937c120387501b71f@DenkenInEchtzeit.net"},"message":"Add integration tests for dbus objects\n\nAfter a conversation with Martin Pitt it became clear that there seems\nto be no existing approach for proper unittests for dbus 'service\nobjects'. The recomended solution is to just write integration tests.\nThis is what this commit provides.\n\nBesides moving ``hamster_dbus.objects`` related tests and fixtures to a\nseperate directory we also provide two important new fixtures.\n- ``private_session_bus`` takes an example from ``python-dbusmock`` in\nproviding a new private session bus in order to not pollute the regular\nsession bus.\n- ``live_service`` launches a trivial service connected to our private\nbus and exports the objects to be tested to it. Data stored by this\nservice is stored in an 'in-memory' sqlite database.\n\nBy using such a setup we are able to reuse most of our test that have\nbeen removed in ``fa3babc342667a4d63f65b4281087849e2faf845``.\n\nOne unfortunate consequence of this integration test based solution is\nthat we can not actually reach full coverage for\n``hamster_dbus.objects``, but this is more of a superficial issue.","distinct":true,"url":"https://api.github.com/repos/projecthamster/hamster-dbus/commits/9e818dafb4067b3540502aed833b2d8cca1f4e3e"},{"sha":"4a1408c6e230f3a082160acf1e8014b5b8c12602","author":{"name":"elbenfreund","email":"41fd8290700e741bcbc5427937c120387501b71f@DenkenInEchtzeit.net"},"message":"Versioning for main 'HamsterDBus' interface\n\nAlso remove obsolete comment.","distinct":true,"url":"https://api.github.com/repos/projecthamster/hamster-dbus/commits/4a1408c6e230f3a082160acf1e8014b5b8c12602"}]}
{"actor":{"display_login":"elbenfreund"}}