tests: Bluetooth: BR: Add GAP Server role test suite #88884
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
area: Bluetooth Classic
github-actions
bot
requested review from
gzh-terry,
jhedberg,
lylezhu2012,
makeshi and
MarkWangChinese
jerryyang35
force-pushed
the
gap_servert_tc
branch
from
6cdfbb3 to
9980ef9
Compare
IUT works as a GAP Server (Peripheral) in the Bluetooth system. The peer device, GAP Client, is a PC running Bumble as a test tool. This test suite implements the following test cases: Case 1, Non-connectable Mode Testing. Verifies DUT can operate in non-connectable mode without allowing connections. Case 2, Connectable Non-discoverable Mode with Active Disconnection. Verifies DUT can accept connections and initiate disconnection. Case 3, Connectable Non-discoverable Mode with Passive Disconnection. Verifies DUT can accept connections and handle passive disconnection. Case 4, Connectable Non-discoverable Mode with Connection Rejection. Verifies DUT can reject connection requests. Case 5, Limited Discoverable Mode with Active Disconnection. Verifies DUT in limited discoverable mode can be discovered, accept connections and initiate disconnection. Case 6, Limited Discoverable Mode with Passive Disconnection. Verifies DUT can be discovered, accept connections and handle passive disconnection. Case 7, Limited Discoverable Mode with Connection Rejection. Verifies DUT can be discovered but reject connection requests. Case 8, General Discoverable Mode with Active Disconnection. Verifies DUT in general discoverable mode can be discovered, accept connections and initiate disconnection. Case 9, General Discoverable Mode with Passive Disconnection. Verifies DUT can be discovered, accept connections and handle passive disconnection. Case 10, General Discoverable Mode with Connection Rejection. Verifies DUT can be discovered but reject connection requests. Signed-off-by: Jiawei Yang <[email protected]>
jerryyang35
force-pushed
the
gap_servert_tc
branch
from
9980ef9 to
c5e8533
Compare
lylezhu2012
approved these changes
May 7, 2025
dleach02
approved these changes
May 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
IUT works as a GAP Server (Peripheral) in the Bluetooth system. The peer device, GAP Client,
is a PC running Bumble as a test tool.
This test suite implements the following test cases: Case 1, Non-connectable Mode Testing. Verifies DUT can operate in non-connectable mode without allowing connections. Case 2, Connectable Non-discoverable Mode with Active Disconnection. Verifies DUT can accept connections and initiate disconnection. Case 3, Connectable Non-discoverable Mode with Passive Disconnection. Verifies DUT can accept connections and handle passive disconnection. Case 4, Connectable Non-discoverable Mode with Connection Rejection. Verifies DUT can reject connection requests.
Case 5, Limited Discoverable Mode with Active Disconnection. Verifies DUT in limited discoverable mode can be discovered, accept connections and initiate disconnection.
Case 6, Limited Discoverable Mode with Passive Disconnection. Verifies DUT can be discovered, accept connections and handle passive disconnection.
Case 7, Limited Discoverable Mode with Connection Rejection. Verifies DUT can be discovered but reject connection requests. Case 8, General Discoverable Mode with Active Disconnection. Verifies DUT in general discoverable mode can be discovered, accept connections and initiate disconnection.
Case 9, General Discoverable Mode with Passive Disconnection. Verifies DUT can be discovered, accept connections and handle passive disconnection.
Case 10, General Discoverable Mode with Connection Rejection. Verifies DUT can be discovered but reject connection requests.