Bluetooth Special Interest Group Inc. BTSIG15A Manual De Usuario
69
Extended Automating
Automating PTS
The Profile Tuning Suite (PTS) offers three features which can be used in automated testing:
1.
“Operator-less Operation” allows the interactive prompts that appear during the execution of a test case to be
processed by user written software which can inspect each message and take appropriate action.
processed by user written software which can inspect each message and take appropriate action.
2.
This feature can be used with either of the following program control features and is described in the
“Automating – Using Implicit Send” reference document.
“Automating – Using Implicit Send” reference document.
3.
“Scripted Operation” where a set of test cases can be selected and run as a group. The group can be executed
as needed, or scheduled for execution at a later time.
as needed, or scheduled for execution at a later time.
4.
The "Scripting" reference document describes this feature.
5.
“Fully Automated Operation” – PTS provides an Application Programming Interface (API) which allows complete
control of the software. User written programs can take advantage of the API in order to open Workspaces,
select Projects, execute Test Cases, and many other functions.
control of the software. User written programs can take advantage of the API in order to open Workspaces,
select Projects, execute Test Cases, and many other functions.
This document describes “Fully Automated Operation”.
"Fully Automated Operation"
Completely unattended operation of PTS can be achieved by using the PTS Control API. There are three parts to “Fully
Automated Operation”:
Automated Operation”:
1.
PTS.exe: The main application program for the Profile Tuning Suite. It accepts calls from user written programs
that use the PTS Control API and takes the appropriate action;
that use the PTS Control API and takes the appropriate action;
2.
Client Application: An application program written by a PTS user that makes use of the PTS Control API in
order to have PTS carry out various functions. The PTS Control API portion of a Client Application may be part
of a larger program that interfaces to a test system platform that has the capability of also controlling the
Bluetooth device that is being tested;
order to have PTS carry out various functions. The PTS Control API portion of a Client Application may be part
of a larger program that interfaces to a test system platform that has the capability of also controlling the
Bluetooth device that is being tested;
3.
PTSControl.dll: A Windows Dynamic Link Library (DLL) that provides the PTS Control API interface and data
type information to the Component Object Model (COM) manager. This information is normally registered with
COM during the installation of PTS.
type information to the Component Object Model (COM) manager. This information is normally registered with
COM during the installation of PTS.
The PTS Control API is implemented using Microsoft’s Component Object Model (COM) which means that any Windows
based programming language that supports COM can be used to develop the Client Application. Some test system
platforms also support the use of COM directly, eliminating the need to create a separate Client Application program.
based programming language that supports COM can be used to develop the Client Application. Some test system
platforms also support the use of COM directly, eliminating the need to create a separate Client Application program.
A C/C++ header file (PTSControl.h) is provided for developers using Microsoft’s Visual C or Visual C++. The information
in the file can be used as a guideline for developing the proper COM interface declarations for other programming
languages or COM enabled applications.
in the file can be used as a guideline for developing the proper COM interface declarations for other programming
languages or COM enabled applications.
A sample Client Application – PTSControlClient – is also provided as part of the PTS installation. This application, written
in Visual C++, exercises many of the functions available in the API. It can be a valuable reference when developing your
own Client Applications.
in Visual C++, exercises many of the functions available in the API. It can be a valuable reference when developing your
own Client Applications.
The source code for PTSControlClient, the PTSControl.h file, and Visual Studio (2008) build files are located in the
C:\Program Files\Bluetooth SIG\Bluetooth PTS\Custom\PTSControlClient
folder in the PTS installation.