Develop an Addon

TestProject SDK For Addons

TestProject is a Free Test Automation platform for Web, Mobile and API testing. To get familiar with the TestProject, visit our main documentation website.

This document describes the bare minimum steps to start developing addons using the Java SDK.

Addons

Automation building blocks empowering your tests.

An Addon is a collection of actions you can use within any recorded test to extend the recorder’s capabilities. Addons can be element based or non-UI based:

  • Element based Addons provide extended functionalities on customized UI elements.

  • Non-UI based Addons combine steps within your recorded tests, such as: File operations, REST API commands, image comparison, etc.

There are hundreds of Addons to choose from, or you can build your own.

Addons are developed in Java and uploaded to the user’s account in a collaborative library. Once uploaded, all team members in the account can use the Addons as part of their tests.

TestProject’s Agent automatically distributes Addons based on the account member’s usage. You can update new versions for Addons, and add more actions or change their functionality according to your needs (All tests using the newly versioned Addon will be updated as well).

There are two types of Addons:

  1. Community Addons: Community Addons are shared by the entire TestProject community and give you the power to effortlessly extend your tests while saving valuable time.

    • The usage of community addon is identical to account addons: Once the community-based action is selected within the Smart Test Recorder, the Addon is automatically downloaded and installed to the account.

    • Before being shared with the entire community, the TestProject team reviews the code and approves the Addon for public usage.

  2. Account Private Addons: Account Addons are private and only accessible to account team members. These Addons do not need to be approved by TestProject before the upload/usage.

Getting Started

To get started, you need to complete the following prerequisites checklist:

Installation

For a Maven project, add the following to your pom.xml file:

<dependency>
<groupId>io.testprojectgroupId>
<artifactId>java-sdkartifactId>
<version>1.0version>
<systemPath>/path/to/sdk/io.testproject.sdk.java.jarsystemPath>
<scope>systemscope>
dependency>

For a Gradle project, add the following to your build.gradle file:

compile files("/path/to/sdk/io.testproject.sdk.java.jar")

Refer to pom.xml and build.gradle files in the provided examples for more details.

Addon development

An addon is a collection of coded actions you can use within any test. It's all stored in TestProject's collaborative addons library.

Addon Manifest

To start developing an Addon a manifest file is required. The manifest is a descriptor of your Addon, it contains a unique GUID for the addon and a list of required permissions. Create an Addon in the Addons screen and download the generated manifest, placing it in your project resources folder.

Implement the Addon

Lets review a simple Addon with a ClearFields action that clears a form. It can be used on the login form in TestProject Demo website or mobile App.

package io.testproject.examples.sdk.actions;
import io.testproject.java.annotations.v2.Action;
import io.testproject.java.sdk.v2.addons.WebAction;
import io.testproject.java.sdk.v2.addons.helpers.WebAddonHelper;
import io.testproject.java.sdk.v2.drivers.WebDriver;
import io.testproject.java.sdk.v2.enums.ExecutionResult;
import io.testproject.java.sdk.v2.exceptions.FailureException;
import org.openqa.selenium.By;
import org.openqa.selenium.WebElement;
@Action(name = "Clear Fields")
public class ClearFieldsAction implements WebAction {
public ExecutionResult execute(WebAddonHelper helper) throws FailureException {
// Get Driver
WebDriver driver = helper.getDriver();
// Search for Form elements
for (WebElement form : driver.findElements(By.tagName("form"))) {
// Ignore invisible forms
if (!form.isDisplayed()) {
continue;
}
// Clear all inputs
for (WebElement element : form.findElements(By.tagName("input"))) {
element.clear();
}
}
return ExecutionResult.PASSED;
}
}

Below are complete source examples:

There is also a Generic action, representing a dummy scenario that can be automated. It can be used as a reference for real scenarios that automate a non-UI (those hat do not require a Selenium or Appium driver) actions.

Action Class

In order to build an Action that can be executed by TestProject, the class has to implement one of the interfaces that the SDK provides. Action class can also be decorated with the @Action annotation to provide extra information about the action.

Interface implementation requires an implementation of the execute() method, that will be be invoked by the platform to run the Action. The execute() method returns ExecutionResult enum which can be PASSED or FAILED.Web Action

ClearFields class implements the WebAction interface:

@Action(name = "Clear Fields")
public class ClearFields implements WebAction

Action entry point is the execute method:

public ExecutionResult execute(WebAddonHelper helper) throws FailureException

Action code searches for visible Forms and then for contained inputs elements, clearing them one by one:

// Get Driver
WebDriver driver = helper.getDriver();
// Search for Form elements
for (WebElement form : driver.findElements(By.tagName("form"))) {
// Ignore invisible forms
if (!form.isDisplayed()) {
continue;
}
// Clear all inputs
for (WebElement element : form.findElements(By.tagName("input"))) {
element.clear();
}
}

Android Action

ClearFields class implements the AndroidAction interface:

@Action(name = "Clear Fields")
public class ClearFields implements AndroidAction

Action entry point is the execute method:

public ExecutionResult execute(AndroidAddonHelper helper) throws FailureException

Action code searches for EditText elements, clearing them one by one:

for (AndroidElement element : helper.getDriver().findElements(By.className("android.widget.EditText"))) {
element.clear();
}

iOS Action

ClearFields class implements the IOSAction interface:

@Action(name = "Clear Fields")
public class ClearFields implements IOSAction

Action entry point is the execute method:

public ExecutionResult execute(IOSAddonHelper helper) throws FailureException

Action code searches for XCUIElementTypeTextField and XCUIElementTypeSecureTextField elements, clearing them one by one:

for (IOSElement element : helper.getDriver().findElements(By.className("XCUIElementTypeTextField"))) {
element.clear();
}
for (IOSElement element : helper.getDriver().findElements(By.className("XCUIElementTypeSecureTextField"))) {
element.clear();
}

Generic Action

Addition class implements the GenericAction interface:

@Action(name = "Addition", description = "Add {{a}} to {{b}}")
public class Addition implements GenericAction

Action entry point is the execute method:

public ExecutionResult execute(AddonHelper helper) throws FailureException

Action code performs an addition of values in two variables, assigning result to third:

Actions run in context of a test and assume that required UI state is already in place. When the action will be used in a test it will be represented as a single step, usually preceded by other steps. However, when debugging it locally, preparations should be done using the Runner class to start from expected UI state:Web - State Preparation

// Create Action
ClearFields action = new ClearFields();
// Prepare state
WebDriver driver = runner.getDriver();
driver.navigate().to("https://example.testproject.io/web/");
driver.findElement(By.id("name")).sendKeys("John Smith");
driver.findElement(By.id("password")).sendKeys("12345");
// Run action
runner.run(action);

Android - State Preparation

// Create Action
ClearFields action = new ClearFields();
// Prepare state
AndroidDriver driver = runner.getDriver();
driver.findElement(By.id("name")).sendKeys("John Smith");
driver.findElement(By.id("password")).sendKeys("12345");
// Run action
runner.run(action);

iOS - State Preparation

// Create Action
ClearFields action = new ClearFields();
// Prepare state
IOSDriver driver = runner.getDriver();
driver.findElement(By.id("name")).sendKeys("John Smith");
driver.findElement(By.id("password")).sendKeys("12345");
// Run action
runner.run(action);

Action Annotations

TestProject SDK provides annotations to describe the action:

  1. The Action annotation is used to better describe your action and define how it will appear later in TestProject UI:

    • name - The name of the action (if omitted, the name of the class will be used).

    • description - A description of the test which is shown in various places in TestProject platform (reports for example). The description can use placeholders {{propertyName}} do dynamically change the text according to test properties.

    • version - A version string which is used for future reference.

  2. The Parameter annotation is used to better describe your action's inputs and outputs, in the example above there are two parameters - question and answer.

    • description - The description of the parameter

    • direction - Defines the parameter as an input (default if omitted) or an output parameter. An input parameter will able to receive values when it is being executed while the output parameter value will be retrieved at the end of test execution (and can be used in other places later on in the automation scenario).

    • defaultValue - Defines a default value that will be used for the parameter.

Debugging / Running Actions

To debug or run the action locally, you will have to use the Runner class from TestProject SDK.

For example:

package io.testproject.tests.desktop;
import io.testproject.java.enums.AutomatedBrowserType;
import io.testproject.java.sdk.v2.Runner;
import io.testproject.tests.Actions;
import org.junit.jupiter.api.AfterAll;
import org.junit.jupiter.api.BeforeAll;
import org.junit.jupiter.api.Test;
import java.io.IOException;
public class ChromeActions {
private static Runner runner;
@BeforeAll
public static void setup() throws InstantiationException {
runner = Runner.createWeb("{YOUR_DEV_TOKEN}", AutomatedBrowserType.Chrome);
}
@Test
public void runAction() throws Exception {
runner.run(new ClearFields());
}
@AfterAll
public static void tearDown() throws IOException {
runner.close();
}
}

Element Actions

Actions can be element based, when their scope is limited to operations on a specific element and not the whole DOM. This allows creating smart crowd based addons for industry common elements and libraries.

TypeRandomPhone is an example of an Element Action:

This action generates a random phone number based on provided country code and max digits amount, typing it in a text field:

long number = (long) (Math.random() * Math.pow(10, maxDigits));
phone = String.format("+%s%s", countryCode, number);
element.sendKeys(phone);
return ExecutionResult.PASSED;

It also stores the result in an output field (see the annotation and ParameterDirection.OUTPUT configuration) for further use later in test. When the action is debugged using a Runner, via JUnit test, it's important to pass the element search criteria into the action:

runner.run(action, By.id("phone"));

After the Addon is uploaded to TestProject platform this will be done via UI.

Element Type

Element Actions are made to be used on a specific Element Types. Element Types are defined in TestProject using XPath to describe target elements similarities:Web - Element Type

It can be a simple definitions such as:

Or a more complex one, such as:

//div[contains(@class, 'progressbar') and contains(@class, 'widget') and @role = 'progressbar']

Android - Element Type

It can be a simple definitions such as:

Or a more complex one, such as:

//android.support.v7.widget.RecyclerView[contains(@resource-id, 'my_view') and .//android.widget.TextView[not(contains(@resource-id, 'average_value'))]]

iOS - Element Type

It can be a simple definitions such as:

Or a more complex one, such as:

//XCUIElementTypeSearchField[contains(@label = 'Categories')]

It is up to the Action developer how to narrow and limit the list of element types that the action developed will be applicable to.

Packaging

In order to upload your Addons or Tests to TestProject, you have to package it as JAR file. Export your code as an uber JAR file with dependencies, excluding TestProject SDK.

See build.gradle or pom.xml files in code examples for details.

License

TestProject Addons SDK For Java is licensed under the LICENSE file in the root directory of this source tree.