Using the Planned Date and Polling
The primary way RemoteLaunch expects tests to be run is using the Planned Date option in SpiraTest together with setting the appropriate Automation Host. In this mode, RemoteLaunch sits in the system tray and is kept running and polling automatically. This gives the widest possible flexibility since it allows SpiraTest to schedule tests on machines anywhere, vs. just having it limited to the one the current user is sitting at, viewing with their browser.
For this more to be used effectively, the Windows desktop needs to be logged in, so we recommend that you add RemoteLaunch to the Windows Startup Program Group so that it always starts on login.
Using the SpiraTest Execute Button
The use of the 'Execute' button in SpiraTest is primarily there to help people get up and running initially with Remotelaunch on their local machine, when they are first using it. For production use, we don't expect people to be using just their local machine.
If you have RemoteLaunch set to poll automatically, it may not let you execute the tests immediately, so if you want to use RemoteLaunch in this mode, we recommend the following steps:
- Make sure RemoteLaunch is not already running
- Click the Execute button on an automated test set
- SpiraTest will try and download a .TST file (this is normal)
- When you click Open, RemoteLaunch will read this file and execute the test
- RemoteLaunch will then exit completely.
If RemoteLaunch is already running, it may not execute this test, since it will be then in "polling" mode, vs. "manual" mode.