From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 499d91: test: functional: add mpris-proxy BR/EDR test cases
Date: Mon, 14 Sep 2026 17:50:28 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1164934/000000-9183ed@github.com> (raw)
Branch: refs/heads/1164934
Home: https://github.com/bluez/bluez
Commit: 499d91699cfc7f0a079984806abd8c8e109165b0
https://github.com/bluez/bluez/commit/499d91699cfc7f0a079984806abd8c8e109165b0
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-09-15 (Tue, 15 Sep 2026)
Changed paths:
M Makefile.am
A doc/functional-mpris-proxy.rst
M doc/functional-testing.rst
A test/functional/test_mpris_proxy.py
Log Message:
-----------
test: functional: add mpris-proxy BR/EDR test cases
Add functional tests for mpris-proxy over BR/EDR: a dummy MPRIS player
on the server is bridged by mpris-proxy to an AVRCP Target, and a
second mpris-proxy on the client, run with --export, exports the
remote player back to the client session bus as an MPRIS player, which
the tests control as MPRIS clients.
test/functional/test_mpris_proxy.py::test_mpris_proxy_playback_control
test/functional/test_mpris_proxy.py::test_mpris_proxy_track_control
Assisted-by: opencode:qwen3.8-flash-next
Commit: 4f360a485a85119fcbd5c35b91ae056ee30f9876
https://github.com/bluez/bluez/commit/4f360a485a85119fcbd5c35b91ae056ee30f9876
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-09-15 (Tue, 15 Sep 2026)
Changed paths:
M doc/functional-testing.rst
M test/functional/conftest.py
A test/functional/le_utils.py
M test/functional/test_avrcp.py
M test/functional/test_mpris_proxy.py
M test/functional/test_obex.py
Log Message:
-----------
test: functional: deduce pairing bearer in shared fixtures
Make paired_hosts deduce the pairing bearer from the host
configuration instead of using BR/EDR only, with the LE pairing helper
pair_le in le_utils. No behavior change.
Assisted-by: opencode:qwen3.8-flash-next
Commit: 9183ed5ea3578a4b4f829104f8dcd81e6413111d
https://github.com/bluez/bluez/commit/9183ed5ea3578a4b4f829104f8dcd81e6413111d
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-09-15 (Tue, 15 Sep 2026)
Changed paths:
M doc/functional-mpris-proxy.rst
M test/functional/le_utils.py
M test/functional/test_mpris_proxy.py
Log Message:
-----------
test: functional: run mpris-proxy tests over LE via MCP
Also run the mpris-proxy tests over LE, where the player is exposed via
MCS instead of AVRCP.
Add an LE advertisement helper for connecting the service.
test/functional/test_mpris_proxy.py::test_mpris_proxy_playback_control[le-vm2]
test/functional/test_mpris_proxy.py::test_mpris_proxy_track_control[le-vm2]
Assisted-by: opencode:qwen3.8-flash-next
Compare: https://github.com/bluez/bluez/compare/499d91699cfc%5E...9183ed5ea357
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-15 0:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bluez/bluez/push/refs/heads/1164934/000000-9183ed@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.