Test compositions that use WebUI/Ajax clips that utilize URLs from more than one domain, or that hit URLs requiring persmission, require some additional configuration steps to succeed.
These steps include:
- Selecting a cross-domain option for browser playback in the relevant target(s)
- Ensuring that the SOASTA Conductor in use in the test has multi-window support enabled.
Error reported from Conductor: Name's conductor running Firefox: Coordinator fault: 'Conductor exception: Permission denied to get property Location.href (com.soasta.com.exceptions.Conductor.Exception)' (Conductor fault, operation: "performRemoteAction".)
Ensure Conductor Multi-Window Support Is Enabled
Before making any changes to the composition or its underlying system properties, ensure that each Conductor(s) in use with the composition, or tracks if more than one is defined, has multi-window support enabled.
- Open SOASTA Conductor application > Preferences > and check to ensure that "Multi-window ajax support" is checked.
Enable Cross-Domain Using a System Property Override
- With the composition open in the Composition Editor, click the Properties tab.
- The Properties screen will open showing a tree of the components of the Test Composition.
- Select the clip in the tree. For example, under Track 1, select SOASTA Store WebUI as shown on the right.
- Select the Property Sets tab. This is where you will set Browser Type (via a System Property override).
- In the Property Sets tab, Other Property Sets section, click the green Plus icon.
- A new row is added to the Other Property Sets list and icons appear in the original row. Cick the Path button (...). In the remaining steps we will override the default Conductor value of the given target and repeat that for each clip instance in this test.
- The Path dialog box appears. Select the target (e.g. SOASTA Store UI)
- In the System tab on the right, select the Browser Type system property.
- Click OK to exit the Path dialog box.
- The row is populated with the Browser Type property. Choose a Browser Type override value for this clip. For example, Firefox Cross-Domain or IE Cross Domain.
- Save the composition after making any changes.
Enable Cross-Domain Using the Target Editor
The same steps can be accomplished via the Target Editor rather than through the use of system property overrides as shown above. In some cases, it may be desirable to edit the target itself, rather than using an override. This method is probably just as useful if the settings for the given target will remain the same for every clip that uses that target.
- First, identify the target whose properties you want to change. Select the test clip in the Composition Editor.
- Right-click and then choose Open in New Tab from the context menu.
In Clip Editor, Messages/Actions tab, note the Included Target(s) listed. For each of these targets, cross-domain support must be enabled at the target level. For example, the clip on the right has one target, SOASTA Store UI.
- Once identified, double-click the target in the Included Target list to open it in the Target Editor.
- Click Central > Targets, locate the given target in the list, and double-click to open it.
The target opens in the Target Editor.
- Locate the Target Info, Settings, Browser drop-down and select from among Firefox Cross-Domain (not the standard Firefox option) or IE Cross-Domain (if this test is conducted in Internet Explorer).
- Click the Target item in the properties tree on the left and then select the Browser Type field.
- Click the Browser Type drop-down and select the option for Firefox cross-domain (not the standard Firefox option).
- Save the target after making any changes.