Automated test not starting when executing

 Hello -

You say you are 'executing' it from SpiraTest - how are you doing this? RemoteLaunch uses the scheduled date and time to launch tests from. If you need to execute one right away, you will have to download the generated *.tst file and run that using RemoteLaunch.

How do you download the generated *.tst file? Before, when I pushed execute in Spiratest I was asked to save a tst file, but now after installing RemoteLaunch I am not asked for anything. Nothing happens.

 Ok, now when I execute the test set I am asked to save the tst file, but when I try to run it i get the message

"The server could not be contacted to retrieve test information. Please go into the settings and verify the server and user information, then runt test file again"

I have checked the connection details and tested the connection and have gotten confirmation that its successfully connected to spiratest, but still I'm getting this error message

I'm using firefox with selenium IDE. RemoteLaunch polling doesn't work either. I guess since it says its not connected in the status tab, but then again when i test the connection in the client setup tab it says its connected. When I try force execute I get the status Application is Paused. Any thoughts, ideas what might be wrong and what I can try to do?

You need to set the Automation Host on the Test Set.

Make sure the Token field of the Automation Host matches the token configured in RemoteLaunch. Then both ways of starting test (clicking Execute or using the Planned Date/Time) will work.

Hi Rosemary

Could you start a new thread on this because your situation might be different. Could you provide more information, such as what error messages appear in the Event Log on the computer that has RemoteLaunch installed.

Thanks

Hello

If the troubleshooting steps do not resolve the problem, consider contacting the support teams of Spiratest, RemoteLaunch, or Selenium for further assistance. Community forums or discussion boards can also be helpful for seeking guidance from other users.

Thank you. 

When an automated test does not start executing, it could be due to several reasons. Here are some possible causes and troubleshooting steps you can try:

1. Check the test configuration: Ensure that the test is configured correctly with the appropriate test runner or test framework. Make sure that all the necessary dependencies and configurations are in place.

2. Review the test code: Double-check your test code for any errors or issues that might prevent it from executing. Check for syntax errors, missing imports, or incorrect method invocations.

3. Verify the test environment: Ensure that the test environment is properly set up and meets the requirements of the test. Check if the necessary software, libraries, or services are installed and running correctly.

4. Examine the test execution command: Review the command or script used to execute the automated test. Ensure that the command is correctly specified, including any parameters or arguments required.

5. Check for conflicting processes or resources: Make sure there are no other processes or resources that might be conflicting with the test execution. For example, if the test requires exclusive access to a database, hydraulic steering system ensure that no other process is currently using it.