-
Notifications
You must be signed in to change notification settings - Fork 6.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
tests: Bluetooth: Mesh: Add op_agg coex test
Adds coexistence Bsim test for Opcode Aggregator models. The test verifies that the Opcode Aggregator server and client can be present and functional when operating on the same device. Signed-off-by: Anders Storrø <[email protected]>
- Loading branch information
1 parent
af32dbb
commit a7f648c
Showing
2 changed files
with
98 additions
and
26 deletions.
There are no files selected for viewing
This file contains 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
31 changes: 31 additions & 0 deletions
31
tests/bsim/bluetooth/mesh/tests_scripts/op_agg/model_coex.sh
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
#!/usr/bin/env bash | ||
# Copyright 2022 Nordic Semiconductor | ||
# SPDX-License-Identifier: Apache-2.0 | ||
|
||
source $(dirname "${BASH_SOURCE[0]}")/../../_mesh_test.sh | ||
|
||
# Test that Opcode aggregator server and client can coexist on the same device. | ||
# In this test scenario, the DUT has a sequence in progress on the Opcode | ||
# Aggregator client model that is interrupted by an incoming sequence to the Opcode | ||
# Aggregator server model. The test verifies that both the incoming and outgoing | ||
# sequence on the DUT completes successfully. | ||
# | ||
# Test procedure: | ||
# 1. Both Tester and DUT device initialize both Opcode aggregator server and client. | ||
# Both devices starts an Opcode aggregator sequence and populates the buffer. | ||
# 2. The Tester device immediately starts sending the sequence. | ||
# 3. The DUT device waits, and verifies that the sequence is correctly received. | ||
# Then it starts sending its own aggregated sequence. | ||
# 4. The Tester device confirms that it received all status messages related to its | ||
# own aggregated sequence from the DUT device, then it verifies that the | ||
# aggregated sequence from the DUT device is correctly received. | ||
# 5. Finally, the DUT device waits and confirms that it received all status messages | ||
# related to its own aggregated sequence from the cli device. | ||
conf=prj_mesh1d1_conf | ||
RunTest mesh_op_agg_model_coex \ | ||
op_agg_tester_model_coex op_agg_dut_model_coex | ||
|
||
conf=prj_mesh1d1_conf | ||
overlay=overlay_psa_conf | ||
RunTest mesh_op_agg_model_coex \ | ||
op_agg_tester_model_coex op_agg_dut_model_coex |