Creating Cross-Platform Web Tests

Before you start creating cross-platform tests:

1. Enable the cross-platform web test support in TestComplete. See below.

2. Choose one of the supported web browsers in which you want to record tests. The browser you use for recording does not matter. You can choose any browser you are comfortable with. The resulting test will be compatible with multiple web browsers, including those supported by TestComplete and those that are not supported directly (for example, Safari, or mobile browsers).

3. Prepare the selected browser for test recording as described in Preparing Web Browsers.

To be able to create tests compatible not only with local browsers but also with various remote browsers, a special mode has been introduced in TestComplete. To record a cross-platform test, enable this mode:

Enable the mode before you start recording the test.

When creating new projects

In existing projects

To create a test, you can record your user actions in a web browser or you can create a test from scratch. The easiest way to create a cross-platform web test is to record it:

1. Start recording.

2. Launch your web browser.

3. Interact with your tested application or web page as an end-user would: navigate through pages, click the links, input data into forms, and so on.

4. Stop the test recording.

TestComplete will process the performed actions and generate the test. The images below show an example of a recorded cross-platform test:

A keyword test Click the image to enlarge it.

A script test Click the image to enlarge it.

A test consists of the sequence of operations that define various interactions with objects in a web browser.

The recorded test does not use mapped web objects. Instead, the recorded test uses the FindElement method to search for tested web elements by their CSS or XPath. To learn more, see Addressing Objects in Cross-Platform Web Tests.

You can modify and enhance the recorded test in a number of ways to make it more flexible and efficient. For example:

• Add new operations, reorder operations and modify their parameters.

• Delete or disable unneeded operations (for example, superfluous recorded operations).

• Insert checkpoints for verifying objects and values in the tested application.

• Create data-driven tests that run multiple test iterations using different sets of data.

You can debug your test by running it on your local computer to make sure that it works as expected. To learn more about test debugging, see Debugging Tests.

A recorded cross-platform test can run on your local computer as is. However, before you can run it in remote test environments, you need to modify it:

1. Remove (or disable) all test commands that interact with local browsers. For instance, in scripts, remove or comment out all script lines that use the Browsers.Item property:

   

   Click the image to enlarge it.

   In keyword tests, remove or disable the Run Browser operation:

   

   Click the image to enlarge it.

2. Add test instructions that will connect to your platform provider and run the browser there.

   If you use CrossBrowserTesting

   If you use any other Selenium Grid provider

   If you use CrossBrowserTesting

   In a keyword test, add the Run Remote Browser operation to your test. The operation allows connecting to Selenium Grid managed by CrossBrowserTesting and launching a needed mobile or desktop web browser:

   

   Click the image to enlarge it.

   In a script test, you can generate the code to run your target web browser by using the Generate run code for CrossBrowserTesting dialog:

   1. Click on the Code Editor toolbar.

   2. In the resulting dialog, log in to CrossBrowserTesting (if you have not logged in yet). If you still do not have a CrossBrowserTesting account, you can sign up for a free trial directly from the dialog.

   3. Select the web browser and the platform where you want to run the test.

   4. Copy the code that the dialog generates and insert it into the needed place in your script test.

   

   Click the image to enlarge it.

   If you use any other Selenium Grid provider

   Write script code that will connect to your Selenium Grid, access a remote environment (node), and run the browser there. To do this, use the Browsers.RemoteItem(HubUrl, Capabilities).Run method.

   Here, the HubURL parameter specifies the URL of your Selenium Grid. The Capabilities parameter is an object that describes the remote environment where you want to run the test: platform, web browser type and version. To learn which capabilities you should use, please see the documentation of your Selenium Grid provider.

3. All the test commands that follow the Browsers.RemoteItem.Run method and that work with the Browser object will run in the remote environment.

   Call your recorded test right after the code that calls the Browsers.RemoteItem.Run method. If your recorded cross-platform test is a script test, call it as you usually call any routine. If your recorded cross-platform test is a keyword test, call it by using the KeywordTests.Test_Name.Run method:

   JavaScript, JScript

   Python

   VBScript

   DelphiScript

   C++Script, C#Script

   JavaScript, JScript

   function Connect()
   {
     …
     Browsers.RemoteItem(server, JSON.stringify(capabilities)).Run(url);
     KeywordTests.Test1.Run();
   
   }

   Python

   def Connect():
     …
     Browsers.RemoteItem[server, capabilities].Run(url)
     KeywordTests.Test1.Run()

   VBScript

   Sub Connect
     …
     Call Browsers.RemoteItem(server, capabilities).Run(url)
   
     KeywordTests.Test1.Run()
   End Sub

   DelphiScript

   procedure Connect();
   var capabilities, url, server;
   begin
     …
     Browsers.RemoteItem(server, capabilities).Run(url);
     KeywordTests.Test1.Run();
   end;

   C++Script, C#Script

   function Connect()
   {
     …
     Browsers["RemoteItem"](server, JSON["stringify"](capabilities))["Run"](url);
     KeywordTests["Test1"]["Run"]();
   
   }

Run the resulting code.

To run your test in several remote environments in a sequence, see Iterate Through Remote Testing Environments.