Last updated: Jul 26, 2020 11:31
Basic information units
The SDK defines a small set of classes that provide the interface (detailed below) to perform the process outlined above:
|ReportiumImportClient||Specifies the Reporting client for passing test information for tests executed on an external server.|
|ImportExecutionContext||Provides the context within which the test report information is generated.|
|ReportiumImportClientFactory||Generates the Reporting client instance, based on the reporting server, context (generated by ImportExecutionContext), and additional test information.|
Establish a connection
To turn any execution into a report, pass the information to the Perfecto Reporting server. The test information is stored in a repository on the Reporting server.
Establish the connection by using the classes of the SDK. The following code snippet performs the following steps to establish a very basic and simple connection:
- Create a new instance of the context class for the data-import functionality.
- Prepare the connection parameters.
- Create a new instance of the Reportium client, ready to receive the data regarding the external test.
Use the following format for the URI of the reporting server:
Your personal authentication token provides secure access to the Reporting server. To generate the token, follow the procedure presented here.
Basic test information
When creating the test report for execution, the STR includes basic information regarding the test. In particular, the report identifies the test with:
- The device/platform the test was run on
- The job name and number that the test is part of
- Tags to be associated with the test
The SDK includes a Platform class that encapsulates the information regarding the device. The Platform class includes the following information:
|Device Type||MOBILE | BROWSER||The type of device used. This is an enum value that supports only the documented values.|
|Device||Device instance||An instance of the Device class (see below) that describes the device used. The class comes in two flavors.|
|Platform OS||String||OS of the platform, normally Android or iOS, or Windows or MacOS.|
|Platform Version||String||The version of the OS used.|
|Screen Resolution||String||The screen resolution used for the test.|
Mobile device information
The MobileInfo class provides the following information related to the mobile device:
|Model||String||The model name of the device, such as Nexus6P or iPhone8|
|Manufacturer||String||The maker of the device, such as LG or Samsung|
|Device ID||String||The identifier of the device|
The following code snippet creates a Platform instance that includes a mobile device:
Browser device information
The BrowserInfo class provides the following information related to the mobile device:
|The type of browser used in the test|
|Version||String||The version number of the browser used for the test|
The following code snippet creates a Platform instance that includes a browser device:
The ImportExecutionContext class supports all test labeling parameters supported by the PerfectoExecutionContext class. These include:
- Job Number and Name
- Project information
- Platform information
The following snippet shows how to set the parameters of the ImportExecutionContext instance:
Add test start, steps, and stop
After creating the ReportiumImportClient instance, use the testStart, stepStart, stepEnd, and testStop methods as they are used for the ReportiumClient instance. Supply the test result as part of activating the testStop method.
Your test may be embedded between the steps. Do not pass the driver variable to the ReportiumClient instance because this is not linked to the Perfecto system.
Collect execution information
Normally, a test step (code between the stepStart and stepEnd methods) includes automation operations whose results should be reported. This SDK for external automation testing offers the following options for reporting the operations executed by the script:
- Using Perfecto extension of the Selenium EventFiringWebDriver class to automatically generate reporting items from each Selenium/Appium operation
- Using a ReportiumImportClient method to generate entries in the report collector, specifying the actions performed and the results
By default, the execution information is sent asynchronously to the Smart Reporting server by a background thread, to minimize the overhead on the test execution. If there is a need to have the execution information sent by the foreground test script, use the setAsyncUpload() method of the ReportiumImportClient instance. To turn off the asynchronous event transfer:
Turning off the AsyncUpload feature may affect the execution time of the test script because each command transmits an event to the Reporting server.
Perfecto supplies an extension of the Selenium EventFiringWebDriver class that activates the basic automation driver of the script, generates a reporting event for each action, and communicates information to the ReportiumImportClient as report units. Using this class allows the report to be generated together with information regarding any Selenium/Appium actions in a transparent methodology.
To use the PerfectoEventFiringWebDriver class:
- Add a project dependency on the reportium-import-selenium jar file.
Add the following code to your automation script, after creating the ReportiumImportClient instance:
From this point on, use the perfectoDriver instance in place of your rwdDriver, for example:
Use the ReportiumImportClient.command() method
The ReportiumImportClient class supports a command() method whereby you can explicitly add information regarding an operation performed by the automation script. This is particularly useful in cases where:
- The automation performs some operations that are not part of Selenium/Appium, for example an internal framework.
- You do not need to report all automation operations and wish to focus only on a small set of logical operations.
The command() method accepts a Command class instance configured with information to add to the report entry. The Command class supports the following report entry information units:
- Command name (withName method)
- Command status (withStatus method)
- Execution description (withMessage method)
- Start and End times (withStartTime and withEndTime methods)
- Add parameter values (addParameter method)
- Add screenshot artifact (addScreenshotAttachment method)
The following snippets demonstrate the use of this class and the command() method:
Limitations of dataIn command fields
The limitations specified in the table apply to the
datain command fields according to the following values:
FIELD_MAX_LENGTH = 256;
URL_MAX_LENGTH = 1024;
MAX_NUM_SCREENSHOTS = 1024;
MESSAGE_MAX_LENGTH = 12000;
Number of screenshots limited
All fields of type text
Attach files to the test report
If the test script generates or accesses files or streamed information that is important to attach to the test report, to provide context or additional information in analyzing the results, you can perform this by doing the following:
- Create an Attachment instance by using the Attachment.Builder() method ) that provides the vital metadata for the attachment.
- Use the addArtifacts() method of the ReportiumImportClient instance.
The API supports adding any type of attachment. When creating the Attachment object, supply the following:
- Content Type: the MIME type that best describes how to display the file.
- Type: A string used by the Smart Reporting server to classify the data file. (This is optional for Text or Screenshot attachments.)
- File Name: Name of the file to save.
- Supply at least one of the following:
- Input Stream: For streamed data.
- Absolute Path: For non-streamed data. Indicates where the data is taken from.
Additional optional information includes:
- Extension: Extension of the data file. Smart Reporting will try to determine this if not supplied.
- Zipped: An indication if the attachment is a condensed file. Smart Reporting will determine this if the file extension is .zip.
The following shows how to use the Attachment type to attach a generic file attachment:
Special attachment types
The Reporting SDK supports the following special classes of Attachments:
- Text attachments: Use the dedicated TextAttachment Builder() method
- Screenshot attachments: Use the dedicated ScreenshotAttachment Builder() method (see example above)
If the attachment can be represented as text (regardless of the format, for example JSON, XML, or plain text), you can attach these to the test report for the execution by:
- Preparing the file's metadata for the reporting server with the TextAttachment's build() method
- Providing the set of TextAttachment instances to the ReportiumImportClient's addArtifacts() method.
The TextAttachment class supports methods to define either a static file's path or a connection to an incoming text stream.(see the following example snippet):
Complete the test script
When using asynchronous reporting events (default, see here), you should add the following command to the script after closing the automation driver (for example RemoteWebDriver, ChromeDriver, or AppiumDriver):
This allows the asynchronous events to complete before closing the test program, which will guarantee that your report includes all test information.
Retrieve the report link
Use the getReportURL method to retrieve the link to the STR.
See simple code samples in the GitHub Repository.