tests: Bluetooth: BR: Add test suite gap_client #88864
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
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
jerryyang35
force-pushed
the
gap_client_tc
branch
4 times, most recently
from
dacd318 to
f0c2ff9
Compare
lylezhu2012
reviewed
Apr 22, 2025
jerryyang35
force-pushed
the
gap_client_tc
branch
2 times, most recently
from
bec23cd to
4a4b598
Compare
IUT works as a Bluetooth GAP Client. The peer device (tester) is configured to respond to inquiries and process connection requests. Add tests to verify GAP client functionality for inquiry, connection, and disconnection scenarios. In the test suite, there are six test cases: Case 1: General Inquiry followed by Connection and Active Disconnection. Verifies that DUT can perform general inquiry, establish connection, and actively disconnect from tester. Case 2: General Inquiry followed by Connection and Passive Disconnection. Verifies that DUT can perform general inquiry, establish connection, and handle disconnection initiated by tester. Case 3: General Inquiry followed by Rejected Connection Request. Verifies that DUT can perform general inquiry and handle connection rejection from tester. Case 4: Limited Inquiry followed by Connection and Active Disconnection. Verifies that DUT can perform limited inquiry, establish connection, and actively disconnect from tester. Case 5: Limited Inquiry followed by Connection and Passive Disconnection. Verifies that DUT can perform limited inquiry, establish connection, and handle disconnection initiated by tester. Case 6: Limited Inquiry followed by Rejected Connection Request. Verifies that DUT can perform limited inquiry and handle connection rejection from tester. Signed-off-by: Jiawei Yang <jiawei.yang_1@nxp.com>
jerryyang35
force-pushed
the
gap_client_tc
branch
from
4a4b598 to
274cd35
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 Bluetooth GAP Client. The peer device (tester) is configured to respond to inquiries and process connection requests.
Add tests to verify GAP client functionality for inquiry, connection, and disconnection scenarios.
In the test suite, there are six test cases:
Case 1: General Inquiry followed by Connection and Active Disconnection. Verifies that DUT can perform general inquiry, establish connection, and actively disconnect from tester.
Case 2: General Inquiry followed by Connection and Passive Disconnection. Verifies that DUT can perform general inquiry, establish connection, and handle disconnection initiated by tester.
Case 3: General Inquiry followed by Rejected Connection Request. Verifies that DUT can perform general inquiry and handle connection rejection from tester.
Case 4: Limited Inquiry followed by Connection and Active Disconnection. Verifies that DUT can perform limited inquiry, establish connection, and actively disconnect from tester.
Case 5: Limited Inquiry followed by Connection and Passive Disconnection. Verifies that DUT can perform limited inquiry, establish connection, and handle disconnection initiated by tester.
Case 6: Limited Inquiry followed by Rejected Connection Request. Verifies that DUT can perform limited inquiry and handle connection rejection from tester.