From: Pauli Virtanen <pav@iki.fi>
To: linux-bluetooth@vger.kernel.org
Cc: Pauli Virtanen <pav@iki.fi>
Subject: [PATCH BlueZ 0/3] test: functional: add mpris-proxy end-to-end tests
Date: Tue, 15 Sep 2026 03:07:17 +0300 [thread overview]
Message-ID: <cover.1789430529.git.pav@iki.fi> (raw)
Add tests for:
MPRIS -> local player -> AVRCP / MCP -> remote player -> MPRIS
Connection and basic operations are tested on smoketest level.
The code is LLM-assisted, with manual design and details input. I
reviewed and tested the result.
Assisted-by: opencode:qwen3.8-flash-next
Pauli Virtanen (3):
test: functional: add mpris-proxy BR/EDR test cases
test: functional: deduce pairing bearer in shared fixtures
test: functional: run mpris-proxy tests over LE via MCP
Makefile.am | 1 +
doc/functional-mpris-proxy.rst | 180 +++++++++++
doc/functional-testing.rst | 7 +-
test/functional/conftest.py | 23 +-
test/functional/le_utils.py | 195 ++++++++++++
test/functional/test_avrcp.py | 4 +-
test/functional/test_mpris_proxy.py | 467 ++++++++++++++++++++++++++++
test/functional/test_obex.py | 8 +-
8 files changed, 873 insertions(+), 12 deletions(-)
create mode 100644 doc/functional-mpris-proxy.rst
create mode 100644 test/functional/le_utils.py
create mode 100644 test/functional/test_mpris_proxy.py
--
2.55.0
next reply other threads:[~2026-09-15 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 0:07 Pauli Virtanen [this message]
2026-09-15 0:07 ` [PATCH BlueZ 1/3] test: functional: add mpris-proxy BR/EDR test cases Pauli Virtanen
2026-09-15 1:55 ` test: functional: add mpris-proxy end-to-end tests bluez.test.bot
2026-09-15 0:07 ` [PATCH BlueZ 2/3] test: functional: deduce pairing bearer in shared fixtures Pauli Virtanen
2026-09-15 0:07 ` [PATCH BlueZ 3/3] test: functional: run mpris-proxy tests over LE via MCP Pauli Virtanen
2026-09-15 20:50 ` [PATCH BlueZ 0/3] test: functional: add mpris-proxy end-to-end tests patchwork-bot+bluetooth
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=cover.1789430529.git.pav@iki.fi \
--to=pav@iki.fi \
--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.