Taking this as a basis, a normal execution of test steps via the client API requires - in general - the following steps:
Connect to an already running instance of the AUT-Agent.
Instruct it to start an AUT or retrieve a list of all currently known AUT identifier.
Connect to the AUT by using the AUT identifier.
Execute an arbitrary amount of CAPs (Component Action Parameter also known as Test steps) on this established connection to an AUT. Note: there is no result processing implemented.
Disconnect from the AUT.
Stop the AUT.
Disconnect from the AUT-Agent.
Figure 2.2, “The most important classes and their methods” allows to get a general overview of the toolkit neutral parts of the client API.