Frequently asked questions

This topic defines commonly used terms and clarifies issues for new SRF users.

Glossary of terms

New functional testers may find the following definitions helpful when using SRF.

Mobile Apps test

A test type for testing mobile apps.

Web test

A test type for testing websites on a desktop or mobile browser.

Application modules

The elements in your application that are tested during an exploratory (manual) testing session.

Example: The Login page or the Dashboard.


Relevant for exploratory (manual) testing sessions.

"A statement of test objectives, and possibly test ideas about how to test."
(ISTQB glossary)


"Make sure that the overall look and feel of the application behaves according to spec."


Relevant for exploratory (manual) testing sessions.

"An uninterrupted period of time spent in executing tests. In exploratory testing, each test session is focused on a charter, but testers can also explore new opportunities or issues during a session. The tester creates and executes on the fly and records their progress." (ISTQB glossary)

Back to top

Viewing the remote access window

The following URLs must be accessible through your browsers when working with SRF:

Required for all SRF functionality

https://* Required for mobile device testing
wss://* Required for testing on private mobile devices

AMS: wss://

EMEA: wss://

Required to support secure tunnels to access apps behind a firewall.

For more details, see Tunneling.

If you are having issues viewing the remote access window inside SRF, ensure that these URLs are accessible through your browsers.

Back to top

Recording on private iOS devices

If you are unable to start recording on iOS private devices, check whether you have an untrusted certificate for a newly installed app.

If this is the case, you'll see an Untrusted Enterprise Developer message when opening the app while recording.

Trust the certificate in the SettingsGeneralDevice Management device settings, and start again.

Back to top

Frozen browsers on touch screens

If you are testing a touch screen device in a recording or exploratory session, and are unable to type in your browser, or if your browser window seems frozen, disable touch flags in Chrome.

Disable your Chrome touch flags:

  1. On your device, open Chrome and browse to chrome://flags/.
  2. Set the Touch Events API to Disabled.
  3. In the prompt at the bottom of the page, click RELAUNCH NOW to relaunch Chrome with your changes.

Back to top

See also: