Collapse all Symbian^3 Product Developer Library

T_BTGavdpAPI Test Suite

This section describes BLUETOOTH-GAVDP Test Suite. It provides an overview of the test suite, its coverage, how to set up the test environment to execute the test suite, and how to find further information about the test cases offered by this test suite.

The aim of the BLUETOOTH-GAVDP Test Suite is to provide and deliver a product quality set of test suites that can be used internally within Symbian, and by external groups who have access to the Symbian test source code.

BLUETOOTH-GAVDP component test suite

Test Suite overview

The BLUETOOTH_USER Test Suite is grouped into two sub-suites:

These sub-suites contain several regression tests for the classes stated in the following table:

T_BTGavdpAPI	T_BTUserAPI
`RGavdp`	`TavdtpContentProtectionCapabilities`
`MGavdpUser`	`TAvdtpHeaderCompressionCapabilities`
	`TAvdtpMediaCodecCapabilities`
	`TAvdtpMediaTransportCapabilities`
	`TAvdtpRecoveryCapabilities`
	`TAvdtpReportingCapabilities`
	`TAvdtpSEPInfo`
	`TAvdtpServiceCapability`
	`TAvdtpServiceCategories`
	`TAvdtpSockAddr`
	`TSEID`

All APIs that Symbian classify as PublishedPartner in BLUETOOTH_USER and BLUETOOTH_GAVDP are tested within each class.

Test approach

The test suite is a means of confidence that the APIs work as expected. Negative testing is performed wherever it is needed, to confirm that correct errors are returned when incorrect parameters are given.

All test scripts are completely automated.

Coverage omissions

None

Test Suite details

Test script source tree location

Descriptions of the test cases can be found in the following location:

...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-avdtpcontentprotectioncapa-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-avdtpcontentprotectioncapa-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-avdtpheadercompressioncapa-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-avdtpmediatransportcapabilities-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-avdtprecoverycapabilities-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-avdtpreportingcapabilities-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-avdtpsepinfo-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-avdtpservicecategories-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-avdtpsockaddr-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-converttosymbianerror-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-nonsbccodeccapabilities-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\scripts\ bt-user-seid-publishedpartner.script
...\bluetoothapitest\bluetoothsvs\T_BTGavdpAPI\scripts\bt-gavdp-publishedpartner-active-master.script
...\bluetoothapitest\bluetoothsvs\T_BTGavdpAPI\scripts\bt-gavdp-publishedpartner-active-slave.script
...\bluetoothapitest\bluetoothsvs\T_BTGavdpAPI\scripts\bt-gavdp-publishedpartner-passive-master.script
...\bluetoothapitest\bluetoothsvs\T_BTGavdpAPI\scripts\bt-gavdp-publishedpartner-passive-slave.script

Test script EPOC tree location

When the tests are built, the scripts are first exported into the following locations in the EPOC tree:

T_BTGavdpAPI scripts:

%EPOCROOT%\epoc32\data\Z\bluetooth\gavdp
T_BTUserAPI scripts:

%EPOCROOT%\epoc32\data\Z\bluetooth\user\

Note: Any mention of “epoc32” is offset by %EPOCROOT%; that is, the full path where the EPOC tree is installed.

Test script build location

When the tests are built, the scripts are built into the following locations:

T_BTGavdpAPI scripts: %EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\bluetooth\gavdp
T_BTUserAPI scripts: %EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\bluetooth\user\

Note: When the tests are built to be executed on hardware the files are built into the z: drive of the ROM.

Test data source tree location

The test data files can be found in the following location:

...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\testdata\bt-user-avdtpcontentprotectioncapa-publishedpartner.ini
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\testdata\bt-user-avdtpheadercompressioncapa-publishedpartner.ini
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\testdata\bt-user-avdtpmediatransportcapabilities-publishedpartner.ini
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\testdata\bt-user-avdtprecoverycapabilities-publishedpartner.ini
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\testdata\bt-user-avdtpreportingcapabilities-publishedpartner.ini
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\testdata\bt-user-avdtpsepinfo-publishedpartner.ini
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\testdata\bt-user-avdtpservicecategories-publishedpartner.ini
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\testdata\bt-user-avdtpsockaddr-publishedpartner.ini
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\testdata\bt-user-converttosymbianerror-publishedpartner.ini
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\testdata\bt-user-nonsbccodeccapabilities-publishedpartner.ini
...\bluetoothapitest\bluetoothsvs\T_BTUserAPI\testdata\bt-user-seid-publishedpartner.ini
...\bluetoothapitest\bluetoothsvs\T_BTSockAPI\testdata\bt-gavdp-publishedpartner-active-master.ini
...\bluetoothapitest\bluetoothsvs\ T_BTGavdpAPI \testdata\bt-gavdp-publishedpartner-active-slave.ini
...\bluetoothapitest\bluetoothsvs\ T_BTGavdpAPI \testdata\bt-gavdp-publishedpartner-passive-master.ini
...\bluetoothapitest\bluetoothsvs\ T_BTGavdpAPI \testdata\bt-gavdp-publishedpartner-passive-slave.ini
...\bluetoothapitest\bluetoothsvs\ T_BTGavdpAPI \testdata\ucc-control-channel-config.ini

Test data EPOC tree location

When the tests are built, the test data files are first exported into the following location in the EPOC tree:

T_BTGavdpAPI test data:

%EPOCROOT%\epoc32\data\Z\bluetooth\gavdp
T_BTUserAPI test data:

%EPOCROOT%\epoc32\data\Z\bluetooth\user\

Test data build location

When the tests are built, the test data files are built into the following location:

T_BTGavdpAPI test data:

%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\bluetooth\gavdp
T_BTUserAPI test data:

%EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\bluetooth\user\

Note: When the tests are built to be executed on hardware the files are built into the z: drive of the ROM.

Test .driver file

The bluetooth.driver file found in the following location:

…\bluetoothapitest\bluetoothsvs\testsuites\bluetooth

This file is used by the test driver to construct the test suite tree structure and export all the appropriate files to the correct location in the epoc32 tree and on the device.

When the tests are built, the .driver file is built into the following location:

%EPOCROOT%\epoc32\testdriver\testproduct

TCS file source location

The .tcs file can be found in the following location:

...\bluetoothapitest\bluetoothsvs\config\t_bluetooth.tcs

TCS Build Location

When the tests are built, the .tcs file is generated at the t_bluetooth.tcs: %EPOCROOT%\epoc32\release\<winscw|armv5>\<udeb|urel>\Z\bluetooth\ location.

Note: When the tests are built to be executed on the hardware, the files are built into the z: drive of the ROM.

Test environment and execution

Device setup

See Bluetooth Test Technology for further information regarding test environment and build and execution procedure.

Support

For support issues related to this Test Suite description and issues to running the tests, test pass rates, and potential defects, contact Symbian or your SDK provider. In most instances, this will be either through the Symbian technical consulting teams, the SDK provider forums or through the developer area of Symbian website.

Parent topic: Bluetooth Verification Suite