SOASTA Conductor Capabilities

Document created by Chris Sommerstad Employee on Jul 20, 2017Last modified by Jijius Jabez on Aug 11, 2017
Version 2Show Document
  • View in full screen mode

TIP: Chrome Extension for recording is recommended over Conductor.

SOASTA Conductor Capabilities

Settings in the Conductor Capabilities section allow you to enable or disable specific capabilities and express options relating to port and other settings.

The Conductor Setup screen is divided into General, Proxy Configuration, Conductor Capabilities, and Advanced sections. When a Conductor option is disabled for recording, for WebUI/Ajax testing, for monitoring, and for external data source monitoring, it is no longer listed in the corresponding CloudTest screen.

Enable/Disable Recording

  • Allow HTTP/HTTPS Recording

The Allow HTTP/HTTPS Recording box, which is enabled by default, allows you to allow/disallow HTTP (Packet-level) and HTTPS recording. This Conductor will not appear in the Recording Editor list of Available Conductors whenever disabled.

When Allow recording is unchecked, that Conductor will not appear in the Recording Editor > Available Conductors panel shown below.

Note: Windows Conductor users should also note that WinPcap installation is required. A prompt will appear when enabling "Allow recording" if WinPcap is not installed.

  • HTTPS recording port

An associated edit box allows you to control the HTTPS recording proxy port. Because HTTPS traffic is encrypted, HTTPS recording uses a proxy. During HTTPS recording, your browser is automatically set to direct its traffic to this proxy, which records the traffic and then forwards the traffic on to the intended destination. In order to talk to this proxy, the browser and proxy must agree on a port number. The default setting should work fine. However, if this port number is already in use for some reason it is possible the port number will need to be changed.


  • Use WebSockets Proxy

Check this box to enable WebSocket Recording. Refer to WebSocket Recording for additional details about capture and playback for testing of the WebSocket protocol.

Enable/Disable WebUI/Ajax

  • Allow Web UI/Ajax testing

When Allow Web UI/Ajax testing is unchecked, that Conductor will not appear in the list of Available Targets for a given WebUI/Ajax target (shown right).

Note: This setting is also found in the Composition Editor target-level properties for a given WebUI composition (whenever a clip using that WebUI target is included in the composition).

The browser list displays the supported browsers for "browser driving" in your environment (in this example, a Mac with the OSX system). Click the Edit Browser properties button to configure additional browsers for use when driving WebUI/Ajax tests. Refer to the WebUI Test Tutorial for a complete overview of WebUI/Ajax functional testing using CloudTest.

Enable/Disable Monitoring

When Allow Monitoring is unchecked, that Conductor will not appear in the Connection Method list of Conductors in the Monitoring Server Groups wizard, System Resource Type and Authentication step.

The Multi-Window Ajax Support checkbox is unchecked by default and controls the type of window in which browser actions are run. By default, browser actions run in an embedded iframe. Checking this box runs browser actions without using an embedded iframe.

Enable/Disable External Data Connectivity

When Allow External Data Connectivity is unchecked, that Conductor will not appear in the Connection Method list of Conductors in the External Data Source Editor.


Automatically Configure Proxies setting

This setting is checked by default and can be disabled in cases where the otherwise automatic configuration of proxies on Mac OS X clients is not desired, such as on OS X Mavericks, where users have encountered issues while attempting to use HTTP(s) recording.

Using Firefox Profiles

SOASTA Conductor supports Firefox profiles and their special configurations. For example, the use of Firefox extensions (Firebug, etc.) per Firefox profile. Firefox profiles provide increased control over browser driving WebUI compositions. By using Firefox profiles, it is possible to customize the browser instance running a WebUI composition.

If the user opts out of auto-configuration by unchecking this box, manual configuration of web and HTTPS proxy becomes necessary. If auto-configuration is unchecked, then in order for HTTP(S) recording to succeed, users must first set up a proxy to localhost:4440 manually using the following steps.

  1. Open OS X System Preferences.
  2. Click Network Preferences. Then Network Preferences display.
  3. Select the network interface that is in use (i.e. Wi-Fi or Ethernet, etc.).
  4. Click the Advanced button.
  5. Click the Proxies tab.

  1. Check the Web Proxy (HTTP) box and define a Web Proxy Server using localhost and port 4440.
  2. Check the Secure Web Proxy (HTTPS) box and define a Secure Web Proxy Server using localhost and port 4440.

To specify a Firefox profile during Conductor installation:

  1. On the SOASTA Conductor Capabilities screen, ensure that Allow WebUI/Ajax testing is checked
  2. With Allow WebUI/Ajax testing checked, select Firefox in the browser list (if there is more than one Firefox listed ensure that you select the one that contains the profile you want to use).
  3. Click the Edit Browser Properties button. The Edit Browser Location screen appears.

  1. Check the Use a specified Firefox profile box and then select the Firefox profile from the Select Firefox Profile drop-down.