Manage remote access and integrations
This topic describes how to connect with remote testing tools and other integration.
Tab: REMOTE ACCESS; mixed access for SRF Administrators and Testers. Testers can view only their own client IDs and secrets.
Use an SRF client ID and secret when:
- Running tests remotely on browsers or devices in the SRF lab.
- Using UFT or LeanFT to record or spy remotely on SRF mobile devices.
For details, see Remote testing.
Generate a new client ID and secret
At the top right, click GENERATE NEW to create a new set of values that you can add to your code.
Enter the details for your new client ID and secret. Provide meaningful values for the NAME and DESCRIPTION, and select a TYPE:
Select execution if you'll be using the client ID and secret without a tunnel.
Select tunnel if you'll be using the client ID and secret in a tunnel. This option is open to SRF Admins only.
For more details, see Manage remote access and integrations.
Click GENERATE. SRF displays your new client ID and secret values for you to copy elsewhere.
Caution: Copy your client secret to a secure location. You can regenerate a new secret, but you will not be able to recall this one.
Tab: INTEGRATIONS; mixed access
Connect to ALM Octane or Altassian JIRA to open defects directly from run results and exploratory sessions.
Toggle on the LIFECYCLE MANAGEMENT option, and select the system you want to connect to. Then, populate the fields as described below:
The Octane settings are read-only for SRF Testers.
SRF Admins: Enter the Octane URL where you want to manage your defects. Make sure that the URL includes the shared space ID and workspace ID.
Click TEST CONNECTION to verify your connection.
Do the following:
Verify that your Octane space is configured to support basic authentication.
If needed, contact your Octane admin to enable the SUPPORTS_BASIC_AUTHENTICATION configuration parameter. For more details, see the Octane Help Center.
SRF admins: In SRF, enter values for the following settings:
The Octane URL where you want to manage your defects.
Make sure that the URL includes the shared space ID and workspace ID.
The name of the tunnel used to connect SRF and Octane.
Tip: For a list of active tunnels, click the TUNNELS tab at the top of the page. For more details, see Manage tunnels.
These settings are read-only for SRF Testers.
SRF Testers: In SRF, enter values for the following settings:
Your Octane username
Your Octane password
Each tester must enter their own Octane access values before opening defects.
- Click TEST CONNECTION to verify your connection.
Enter the details for the JIRA space where you want to manage your defects.
In the URL field, enter the URL for your JIRA space using the following syntax:
For example: https://myjira.atlassian.net
In the EMAIL and API TOKEN fields, enter the email address and API token or password used to access JIRA.
Each tester must enter their own JIRA access values before opening defects.
For details about JIRA API tokens, see the JIRA documentation.
Click TEST CONNECTION to verify your connection.
When you're finished, click Save to save your changes.
For more details, see Create defects.
Connect SRF to an Applitools account to send screenshots and other data to Applitools and trigger Applitools design tests on your app.
Toggle on the APPLITOOLS option.
Enter the Applitools API and view keys used to access your Applitools account and test results.
Caution: Incorrect Applitools keys may cause unexpected errors in your test execution.
For more details, see SRF and Applitools and the following Applitools FAQs:
Tab: INTEGRATIONS; SRF Admins only.
Enable Google Analytics to enable SRF to pull your analytics data and display it on your SRF dashboard.
Generate a Google API credentials JSON file to use when accessing your Google Analytics data.
You must have full Google Analytics permissions to perform these steps.
Do the following:Create a Google API project
If you don't yet have a Google API project, browse to the Google Developers Console to create one.
Create a new Google API project, and give it a meaningful name.
If you already have a Google API project, you can use your existing project for SRF access.
Continue with Enable the Analytics API for your API project.Enable the Analytics API for your API project
Enable the Analytics API to grant your API project with access to your Analytics data.
Create Google API credentials
In your Google API project, browse to Google APIs APIs & services page > Dashboard.
Click ENABLE APIS AND SERVICES to access the API Library.
In the API Library, search for and then click Analytics API.
- On the Analytics API page, click Enable.
- Continue with Create Google API credentials.
Generate a JSON file containing your Google API credentials.
Grant Google Analytics permissions to your service account
Browse to the Google APIs APIs & services page > Credentials.
Click Create credentials, and select Service account key from the menu.
From the Service account menu, select your service account.
If you don't have one yet, select New service account to create a new one.
In the Key type area, ensure that you have JSON selected.
Click Create to create your JSON credentials file.
If the Service account has no role message appears, click CREATE WITHOUT ROLE.
Save the file locally, and open it in a text editor.
- Continue with Grant Google Analytics permissions to your service account.
Grant your Google API credentials access to your Google Analytics data.
From the JSON file opened in a text editor, locate the client_email value.
Add Google Analytics permissions for this client_email email address.
In Google Analytics, browse to the Admin section, and then browse down to your view's User management area.
In the Add Permissions for field, enter your client_email value.
Read & Analyze permissions are sufficient.
Click Add, and then verify that the value was added to the User Email list above.
In the SRF Settings > INTEGRATIONS tab, toggle on the GOOGLE ANALYTICS option.
Copy the entire contents of your Google API credentials JSON file, and paste them into the CREDENTIALS field in SRF.
Click SUBMIT CREDENTIALS to submit them to SRF.
Click TEST CURRENT CREDENTIALS to verify your connection to Google Analytics, based on the submitted JSON code.
For more details, see Determine what to test.