So I was trying to run my test suite using the 'Test Suite Runner'' with the endpoint pointing to BrowserStack. This works when I run the tests from 'Ranorex Studio' but when I open the test from the TestSuite Runner and select the BrowserStack endpoint it runs the tests locally on my machine.
Ranorex version: 7.2
Windows 7
Endpoint not changing when using Test Suite Runner
Re: Endpoint not changing when using Test Suite Runner
Hi Brian,
Since there is currently no way to select an endpoint in the Test Suite Runner, your test will always be executed locally.
If you want to run your test on an endpoint, you will have to execute it out of Ranorex Studio.
regards,
qwertzu
Since there is currently no way to select an endpoint in the Test Suite Runner, your test will always be executed locally.
If you want to run your test on an endpoint, you will have to execute it out of Ranorex Studio.
regards,
qwertzu
Re: Endpoint not changing when using Test Suite Runner
Hey,
In settings -> general tab -> endpoints I can change the endpoint in the test suite runner, also the run button updates to show an endpoint has been selected.
In settings -> general tab -> endpoints I can change the endpoint in the test suite runner, also the run button updates to show an endpoint has been selected.
Re: Endpoint not changing when using Test Suite Runner
Hi Brian,
Thanks! I haven´t seen this setting yet
However, as a workaround you could try to run the shortcut in your bin/debug folder that runs the test on your endpoint:
This should work perfectly fine.
regards,
qwertzu
Thanks! I haven´t seen this setting yet

However, as a workaround you could try to run the shortcut in your bin/debug folder that runs the test on your endpoint:
This should work perfectly fine.
regards,
qwertzu
- Support Team
- Site Admin
- Posts: 12167
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Graz, Austria
Re: Endpoint not changing when using Test Suite Runner
Hello Brian,
Thank you for reporting this issue.
We were able to reproduce it on one of our machines and forwarded it to our development team.
As qwertzu already suggested, you could try executing the shortcut that points on your specific endpoint.
This should be a proper workaround.
regards,
Stephan
Thank you for reporting this issue.
We were able to reproduce it on one of our machines and forwarded it to our development team.
As qwertzu already suggested, you could try executing the shortcut that points on your specific endpoint.
This should be a proper workaround.
regards,
Stephan