diff options
| author | Martin Pitt <martin@piware.de> | 2023-12-28 21:13:15 +0100 |
|---|---|---|
| committer | Martin Pitt <martin@piware.de> | 2023-12-28 21:13:15 +0100 |
| commit | bd1e4698f480c6b94afa0536fc02e211ae5a87fb (patch) | |
| tree | 5e3783cd6cd0bca0fd77e3b175220ceee2646c94 | |
| parent | dfde9e2274d1c53d09bd2278cc41d72eacaabc1a (diff) | |
linux: Adjust test_bluetooth_le_device for dbusmock 0.30.1
dbusmock 0.30.1 changed the BlueZ template to set the default "Class"
property to `MOCK_PHONE_CLASS` right away instead of in PairDevice() [1].
test_bluetooth_le_device() relied on the previous implicit default of a
"0" Class value. Set this explicitly to expect a "generic" device. This
makes the test work with old and current dbusmock versions.
https://bugs.debian.org/1059467
[1] https://github.com/martinpitt/python-dbusmock/pull/192
| -rwxr-xr-x | src/linux/integration-test.py | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/linux/integration-test.py b/src/linux/integration-test.py index e686125..4c071e8 100755 --- a/src/linux/integration-test.py +++ b/src/linux/integration-test.py @@ -2162,7 +2162,9 @@ class Tests(dbusmock.DBusTestCase): alias = 'Satechi M1 Mouse' battery_level = 99 - device_properties = None + device_properties = { + 'Class': dbus.UInt32(0, variant_level=1) + } devs = self._add_bluez_battery_device(alias, device_properties, battery_level) self.assertEqual(len(devs), 1) |