RemoteLaunch

Articles
Running Selenium WebDriver Scripts using RemoteLaunch and NUnit
This article explains the process for running Selenium WebDriver test scripts written in C# using NUnit, RemoteLaunch and SpiraTest.
How to enable assembly bind failure logging (Fusion) in .NET
Sometimes when using RemoteLaunch with a specific plugin (e.g. Selenium), you may get an error such as:

Could not load file or assembly 'WebDriver, Version=2.44.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

The way to debug this kind of error message is to enable Microsoft .NET Fusion Logging to get more information as to which dependency could not be loaded. This article explains how to turn this on.
Running Selenium WebDriver Scripts using RemoteLaunch and TestNG
This article explains the process for running Selenium WebDriver test scripts written in Java using TestNG, RemoteLaunch and SpiraTest.
Integrating SpiraTest and RemoteLaunch with Cucumber

Cucumber is a software tool that computer programmers use for testing other software. It runs automated acceptance tests written in a behavior-driven development (BDD) style. Cucumber is written in the Ruby programming language. This articles explains how you can use SpiraTest and RemoteLaunch to integrate with Cucumber.

Running Selenium WebDriver Scripts using RemoteLaunch and JUnit
This article explains the process for running Selenium WebDriver test scripts written in Java using JUnit, RemoteLaunch and SpiraTest.
Running Selenium IDE Scripts using RemoteLaunch
When you use RemoteLaunch with SpiraTest / SpiraTeam, you have the ability to run Selenium IDE scripts written in the Selenese format as well as WebDriver scripts run using specific language bindings. However the RemoteLaunch Selenium2 plugin only handles the Selenium IDE commands that have a corresponding Selenium WebDriver equivalent or ones that RemoteLaunch can handle natively (e.g. pause).
Running VBScript automated test scripts using RemoteLaunch
With RemoteLaunch you can execute test scripts written in a variety of languages on your test computers and have them scheduled and managed by SpiraTest. This article explains the process.
Running TestExecute/TestComplete tests under Windows 8/10 throws an error

Sometimes when running RemoteLaunch and either TestExecute or TestComplete (from SmartBear) on Windows 8 and Windows 10 will result in an error message being displayed due to the security permissions in Windows 8 and 10:

HRESULT: 0x800702E4 (Requires Elevation)

A DLL required for this install to complete could not be run

If you run one of our installation packages (.msi) and receive the following message:

A DLL required for this install to complete could not be run

Issues when running QTP/UFT tests with UFT 11.5
There are some common issues that can occur when running tests written for HP QuickTestPro (QTP) or HP Unified Functional Testing (UFT) that happen because of some known bugs within UFT 11.5. Although these bugs are actually defects in UFT rather than Remotelaunch, we have included them here to provide some suggestions to our customers who may encounter them. For more advanced troubleshooting we recommend contacting HP Support.
Data at the root level is invalid error when running JMeter tests
When running a JMeter test script through RemoteLaunch, you may get the following error:

Exception:
Data at the root level is invalid. Line 1, position 1.

Stack Trace:
 at Inflectra.RemoteLaunch.Engines.JMeter2AutomationEngine.JMeterAutomationEngine.StartExecution
(AutomatedTestRun automatedTestRun)
 at Inflectra.RemoteLaunch.Business.RunTestThread.Execute()


Connecting RemoteLaunch to SpiraTest through a proxy server
When connecting RemoteLaunch to an instance of SpiraTest or SpiraTeam that is externally hosted you may have an issue where RemoteLaunch does not know to use a local proxy server. This articles describes an easy solution to modify RemoteLaunch to use your current Internet Explorer (IE) proxy settings.