Lecture Notes in Computer Science 3472

BluetoothTest
BluetoothSuite
HCI HCI LNI
p_s
p_m
Hardware
Test− p1[4]
Coordinator
LNI
TCI
SRI
p_ap
Slave−
Application
HCI LNI TCI
p_hw p_co
Master
Location
DataBase
(a) Test Package
LNI
Bluetooth−
Roaming
Fig. 17.8. Test Package & Test Context
17 UML 2.0 Testing Profile 509
BluetoothSuite
+ RList: list
− threshold: Integer
− verdict: Verdict
+ Connect_to_Master()
+ Bad_Link_Quality()
+ Good_Link_Quality()
− TestRoaming_noWarning(): Verdict
− TestRoaming_withWarning(): Verdict
(b) Test Context
In this case study, the following functionalities of the Slave Roaming layer
should be tested:
• Is the Slave Roaming layer able to choose a new master by looking up in its
roaming list when the connection with its current master gets weak?
• Does the Slave Roaming layer request a connection establishment to the chosen
master?
• Does the Slave Roaming layer wait for a connection confirmation of the master
when the connection has been established?
• Does the Slave Roaming layer send a warning to the environment, when no
master can be found and the roaming list is empty?
These test objectives assume that basic functionalities of the Slave Roaming layer
like data forwarding from the application layer to the hardware layer have already
been tested in a preceding capability test.
17.4.3 Test Architecture
First of all, a test package for the test model must be defined. The test package
is named BluetoothTest (Figure 17.8a). The test package imports the classes and
interfaces from a BluetoothRoaming package in order to get access to the classes
to be tested.
In Section 17.4.2, the Slave BTRoaming layer is assigned to SUT and other
system components are assigned to test components. The test package consists
of five test component classes, one utility part and one test context class. only
implicitly specified in the test system. triggered by validation actions in the
test cases. The test context class is called BluetoothSuite. Itshowsvarioustest
attributes, some test functions and two test cases (Figure 17.8b).
Test configuration and test control are also specified in the test context class.
The test configuration (Figure 17.9a) corresponds with the test configuration in
Figure 17.7, except that it consists of one slave and four masters m1–m4. Ports
with interfaces connect the test components and the SUT to each other.