|
|
 |
The Keynote DeviceAnywhere Test Automation API empowers users to interact directly with Keynote DeviceAnywhere devices through a powerful Java interface.
Containing the underlying code for all functionality built into the Keynote DeviceAnywhere™ Studio UI, the API contains all the classes and methods to support individual device commands, as well as call into Keynote DeviceAnywhere Test Automation scripts.
Supported Functions and Features
- Send input to remote devices (hardware commands, such as connecting/disconnecting battery, opening/closing flip phone, pressing buttons, tap touch screens, etc.).
- Extract outputs from handsets (audio, video screens).
- Utilize Keynote DeviceAnywhere Test Automation scripting commands (wait for specific text, images).
- Access and execute actions (test scripts) defined through Keynote DeviceAnywhere Test Automation.
Keynote DeviceAnywhere Test Automation API Features and Benefits
- Access and control Keynote DeviceAnywhere handsets with a standards-based programming language.
- Flexibly utilize Keynote DeviceAnywhere Test Automation features either through the API or through Keynote DeviceAnywhere Studio.
- Create test scripts directly in Java or use Keynote DeviceAnywhere Test Automation’s visual scripting language, and easily generate Java code from these scripts with the click of a button.
- Use Keynote DeviceAnywhere Studio’s built-in Java editor, or utilize your own Java IDE.
- View executing tests in real time through the Keynote DeviceAnywhere Test Automation API Dashboard.
- Utilize existing test frameworks by converting existing assets into Java or creating a bridge to other programming languages, such as PERL or PhP.
- Easily extend testing capabilities to other systems by scripting actions between Keynote DeviceAnywhere devices and external elements – for example, test instant messaging between a mobile handset and a PC.
- Optionally save all results into the Enterprise Portal reporting interface.
- Access multiple devices within one session – the API methods will check to make sure all required devices are available before connecting.
- Integrate your test schedules with other internal events – for example, automatically initiate certain regression tests as new builds are released.
|
|
|
 |
|
|