Introduction
Testkit local proxy
With local proxies, you can make your local development environment accessible by the Testkit Cloud. That way, you can run your Cypress tests in the cloud without pushing your code first.
Installation
If you haven't already, make sure you have the latest version of the Testkit CLI installed:
npm install --global @testkit-labs/cli@latest
Create a proxy secret
Start by logging in to the Testkit dashboard and clicking on proxies in the navigation, or just click here to get to the proxies list directly. Then, click on "Create Proxy" in the top right and give it a name. After that, you should see the newly created proxy in the list. Click on the "Secret" column of the newly created proxy to copy the secret.
Starting a proxy
to start the proxy, run the following command:
testkit proxy --org <YOUR ORGANIZATION ID> --proxySecret <YOUR PROXY SECRET>
This will give you an IP address, which you can set as the baseUrl (with ports, if applicable) for your tests. When you do that and run your tests, the browsers used will be in the cloud and results will be in the Testkit dashboard, but the tests are run against the state of the application on your local machine.
The --org and --proxySecret are mandatory. You can get the proxy secret from the previous step, and you will find the organization id here or in the Testkit dashboard in the bottom left ("Quick Start")
Flags
-o, --org=<value>- (required) Organization ID-s, --proxySecret=<value>- (required) Proxy Secret-p, --port=<value>- Port on which the proxy server runs on your local machine (This should not be the same port as your development server), default is 1080
Additional note
The Testkit local proxy is still in beta and will have some substantial changes in the future, especially for security. If you need more information, have feedback or encounter a problem, please contact us at support@testkit.app