Testim Documentation

Welcome to the Testim documentation. You'll find comprehensive guides to help you get started quickly, example code snippets, and tips for being more productive. You will also find details about advanced features that allow you to customize Testim to fit your environment or special testing conditions. Don't worry, we'll support you if you get stuck. Let's jump right in!

Guides    Changelog

Dedicated run tunnel

Tunnels let you run your app from an internal server/localhost and view it in external browser (proxy).

In some cases you would want to run tests on your own private or internal servers, using a remote selenium grid server, either supplied by Testim or by an external provider such as SauceLabs.

Prerequisites

  1. Tunnel feature enabled (contact support info@testim.io for more information)
  2. Testim CLI

How to use it

  1. Run your application server
  2. Run Testim CLI with parameter (--tunnel - default application port 80)
  3. If you run your application under different port than port 80, add parameter (--tunnel-port <APP PORT e.g. 80>)

Note that Testim CLI will adjust your application base URL to point to the dedicated tunnel address.

Example using Testim CLI with a tunnel

testim --tunnel --tunnel-port <APP PORT default 80> --label "<YOUR LABEL>" --token "<YOUR ACCESS TOKEN>" --project "<YOUR PROJECT ID>" --grid "<Your grid name>" --report-file test-results/testim-tests-report.xml

Note:

1.You can not use tunnel for https addresses.;
2.For the grid name, read here how to set up your grid.

Updated about a month ago

Dedicated run tunnel


Tunnels let you run your app from an internal server/localhost and view it in external browser (proxy).

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.