Skip to content

API for AWS Device Farm

ABAP Package /AWS1/API_DFM_IMPL
ABAP SDK "TLA" DFM
ABAP Interface /AWS1/IF_DFM

The "TLA" is a Three Letter Abbreviation that appears in ABAP class names, data dictionary objects and other ABAP objects throughout the AWS SDK for SAP ABAP. The TLA for AWS Device Farm is DFM. This TLA helps squeeze ABAP objects into the 30-character length limit of the ABAP data dictionary.

Installation

To install the AWS SDK for SAP ABAP, import the Core transport, along with the transport for the Device Farm module and other API modules you are interested in. A few modules are included in the Core transport itself. For more information, see the Developer Guide guide.

About The Service

Welcome to the AWS Device Farm API documentation, which contains APIs for:

  • Testing on desktop browsers

    Device Farm makes it possible for you to test your web applications on desktop browsers using Selenium. The APIs for desktop browser testing contain TestGrid in their names. For more information, see Testing Web Applications on Selenium with Device Farm.

  • Testing on real mobile devices

    Device Farm makes it possible for you to test apps on physical phones, tablets, and other devices in the cloud. For more information, see the Device Farm Developer Guide.

Using the SDK

In your code, create a client using the SDK module for AWS Device Farm, which is created with factory method /AWS1/CL_DFM_FACTORY=>create(). In this example we will assume you have configured an SDK profile in transaction /AWS1/IMG called ZFINANCE.

DATA(go_session)   = /aws1/cl_rt_session_aws=>create( 'ZFINANCE' ).
DATA(go_dfm)       = /aws1/cl_dfm_factory=>create( go_session ).

Your variable go_dfm is an instance of /AWS1/IF_DFM, and all of the operations in the AWS Device Farm service are accessed by calling methods in /AWS1/IF_DFM.

API Operations

For an overview of ABAP method calls corresponding to API operations in AWS Device Farm, see the Operation List.

Factory Method

/AWS1/CL_DFM_FACTORY=>create( )

Creates an object of type /AWS1/IF_DFM.

IMPORTING

Optional arguments:

IV_PROTOCOL TYPE /AWS1/RT_PROTOCOL /AWS1/RT_PROTOCOL

IO_SESSION TYPE REF TO /AWS1/CL_RT_SESSION_BASE /AWS1/CL_RT_SESSION_BASE

IV_REGION TYPE /AWS1/RT_REGION_ID /AWS1/RT_REGION_ID

IV_CUSTOM_ENDPOINT TYPE /AWS1/RT_ENDPOINT /AWS1/RT_ENDPOINT

RETURNING

OO_CLIENT TYPE REF TO /AWS1/IF_DFM /AWS1/IF_DFM

/AWS1/IF_DFM represents the ABAP client for the Device Farm service, representing each operation as a method call. For more information see the API Page page.

Configuring Programmatically

DATA(lo_config) = DATA(go_dfm)->get_config( ).

lo_config is a variable of type /AWS1/CL_DFM_CONFIG. See the documentation for /AWS1/CL_DFM_CONFIG for details on the settings that can be configured.

Paginators

Paginators for AWS Device Farm can be created via get_paginator() which returns a paginator object of type /AWS1/IF_DFM_PAGINATOR. The operation method that is being paginated is called using the paginator object, which accepts any necessary parameters to provide to the underlying API operation. This returns an iterator object which can be used to iterate over paginated results using has_next() and get_next() methods.

Details about the paginator methods available for service AWS Device Farm can be found in interface /AWS1/IF_DFM_PAGINATOR.