Copy the dependencies in the pom.xml file and paste them into the pom.xml file of your own project. This step is essential because the imports in our final script only work when the dependencies specified in this file are available.

Generate your security token through the Perfecto UI. Then define your security token as a system variable called securityToken. The script uses this variable to retrieve the security token:

String securityToken = System.getProperty("securityToken");
...
capabilities.setCapability("securityToken", securityToken);

This is the recommended way of including the security token, but of course you can also keep the token in Jenkins or even hard-code it in the script.

To generate a security token:

1. In the Perfecto UI at <YourCloud>.app.perfectomobile.com (where YourCloud is your actual cloud name, such as mobilecloud), click your user name and select My security token. 
   
   
2. In the My security token form, click Generate Security Token.
   

3. Click Copy to clipboard. Then paste it into any scripts that you want to run with Perfecto. See Use a security token in automation scripts below.
   

4. Click Close.

Use capabilities to select a device from the Perfecto lab. You can be as generic or specific as needed. In our script, we have included the these capabilities, as shown in the following code snippet:

• model: The device model
• openDeviceTimeout: The timeout, in minutes, to wait for a specific device in case it is not available at the start of the script (use with caution)
• appPackage: The Java package of the Android app you want to run

For more information on capabilities, see:

• Define capabilities
• Supported Appium capabilities
• Use capabilities to select a device

DesiredCapabilities capabilities = new DesiredCapabilities(browserName, "", Platform.ANY);
...	
capabilities.setCapability("model", "Galaxy.*");
capabilities.setCapability("openDeviceTimeout", 2);
capabilities.setCapability("appPackage", "com.sec.android.app.popupcalculator");

You can use the Manual Testing view in the Perfecto UI to generate a code snippet with device-specific capabilities that you can then copy-paste into your script. 

To generate capabilities (for mobile or web devices) through the Perfecto UI:

1. On the Perfecto landing page, under Manual Testing, click Open Device.
2. In the Manual Testing view, do the following to generate capabilities:
   
   1. In the list or tile view, click a device.
   2. In the details pane on the right, click the Capabilities tab.
   3. (Mobile device only) Depending on what you want to see in your code sample, select Device attributes or Device ID.
      
   4. From the drop-down list, select the programming language to use.
   5. The code snippet is updated automatically.
   6. Click Copy to clipboard.
   7. Paste into your existing script.

As part of creating an instance of the RemoteWebDriver, you need to supply the URL of your Perfecto cloud. Define the name of your Perfecto cloud as a system variable called cloudName., for example: demo.

The general structure of the URL string is as follows:

"https://" + cloudName + "/perfectomobile.com/nexperience/perfectomobile/wd/hub" 

Here are the respective lines from our sample script:

String cloudName = System.getProperty("cloudName");
...
RemoteWebDriver driver = new RemoteWebDriver(new URL("https://" + cloudName + ".perfectomobile.com/nexperience/perfectomobile/wd/hub"), capabilities);

To get the most out of running your test in Perfecto, you need to create an instance of the Smart Reporting client (ReportiumClient). This will allow you to later retrieve and analyze the test report. The reporting client is responsible for gathering basic information about the test and transmitting it to the Smart Reporting system.

In our script, we show how to use the ReportiumClientFactory class' createPerfectoReportiumClient() method. Use the PerfectoExecutionContext class to supply the link to the factory class creating the client instance. Use the withWebDriver() method to supply the link of the driver instance.

Use the build() method to create the context object's instance and supply this to the createPerfectoReportiumClient() method when creating the ReportiumClient instance.

PerfectoExecutionContext perfectoExecutionContext;
if(System.getProperty("reportium-job-name") != null) {
		perfectoExecutionContext = new PerfectoExecutionContext.PerfectoExecutionContextBuilder()
				.withProject(new Project("My Project", "1.0"))
				.withJob(new Job(System.getProperty("reportium-job-name") , Integer.parseInt(System.getProperty("reportium-job-number"))))
				.withContextTags("tag1")
				.withWebDriver(driver)
				.build();
} else {
		perfectoExecutionContext = new PerfectoExecutionContext.PerfectoExecutionContextBuilder()
				.withProject(new Project("My Project", "1.0"))
				.withContextTags("tag1")
				.withWebDriver(driver)
				.build();
}
ReportiumClient reportiumClient = new ReportiumClientFactory().createPerfectoReportiumClient(perfectoExecutionContext);

In addition to supplying the driver link, the context supports optional settings, such as adding:

• Reporting tags: Tags are used as a freestyle text for filtering the reports in the Reporting app. Use the withContextTags() method as shown in the following code snippet.
• CI job information: Job information is used to add your test runs to the CI Dashboard view. Use the withJob() method of the PerfectoExecutionContext instance, supplying the job name and job number, when creating the ReportiumClient instance.
  Our sample script uses system variables to fetch the reportium-job-name and the reportium-job-number values . Both system variables are sent from CI tools like Jenkins as a Maven -D system property. For example:
  -Dreportium-job-name=${JOB_NAME} -Dreportium-job-number=${BUILD_NUMBER}
  The following figure illustrates how the reportium-job-name and the reportium-job-number system variables get their value from Jenkins. These variables are passed as -D parameters for install goals of Maven.
  
  Our script supports both local and CI-based executions (for more information, see Add reporting to Jenkins > Supply Maven or Ivy parameters).

Replace the existing test code in the try bock with your own test information.

try {
	reportiumClient.testStart("My Calculator Test", new TestContext("tag2", "tag3"));
	reportiumClient.stepStart("Perform addition");
	driver.findElement(By.xpath("//*[contains(@resource-id,'1')]")).click();
	driver.findElement(By.xpath("//*[contains(@resource-id,'add')]")).click();
	driver.findElement(By.xpath("//*[contains(@resource-id,'1')]")).click();
	driver.findElement(By.xpath("//*[contains(@resource-id,'equal')]")).click();
	reportiumClient.stepEnd();
	reportiumClient.stepStart("Verify Total");
	WebElement results=driver.findElement(By.xpath("//*[contains(@class,'EditText')]"));
	if (!results.getText().equals("2"))
		throw new RuntimeException("Actual calculated number is : \"+results.getText() + \". It did not match with expected value: 2");
	reportiumClient.stepEnd();
		//STOP TEST
	TestResult testResult = TestResultFactory.createSuccess();
	reportiumClient.testStop(testResult);
}

In our example, the test is separated into logical groupings of actions as logical steps. Each step is labeled and appears in the Execution Report together with the component actions. The beginning of each logical step is indicated with the stepStart() method, providing the label of the step, and the end of each logical step with the stepEnd() method (for the report).

To end the test, supply an indication of the final outcome of the test by generating a TestResult instance.

//STOP TEST
    TestResult testResult = TestResultFactory.createSuccess();
    reportiumClient.testStop(testResult);

} catch (Exception e) {
			TestResult testResult = TestResultFactory.createFailure(e);
			reportiumClient.testStop(testResult);
			e.printStackTrace();
}

In our example, the createSuccess method notifies the reporting server that the test resulted in a successful status. The createFailure method notifies the reporting server that the test resulted in an unsuccessful status and supports adding a notification message that is displayed in the test report. Our script also provides a failure reason, but this is optional. To learn more about failure reasons in reporting, see Work with failure reasons.

Last, make sure to close and quit the RemoteWebDriver and retrieve the Smart Reporting URL for the generated test report.

finally {
			driver.close();
			driver.quit();
			// Retrieve the URL to the DigitalZoom Report 
			String reportURL = reportiumClient.getReportUrl();
			System.out.println(reportURL);
        }