Testing Robot license is not compatible with Remote Debugging

Feedback Test Cloud
1

image

It is unfortunate that the “Testing Robot” license does not support remote debugging.
This means that when developing test automation projects, the developer cannot test the written test in a remote server (simulating future runtime enviornment)

Remote Debugging issues an error that only Unattended and Non-Production license are supported with remote debugging.

image

I believe test automation / testing robot should also be included. We understand that the workaround is to use a non-production license on the machine. But we dont see any reason to not include “Testing Robot” license in remote debugging.

This creates additional overheads for the test developers both during development and before deployment.

1 Like
3

We have a Testing license and our team shook our heads when we realized that the Testing license couldn’t be used for Remote Debugging to TEST workflows on VMs before deployment.

1 Like
4

Hi Jeevith,

thx a lot for the feedback. We have logged a feature request for enabling remote debugging on Test Robots.

BR
Thomas

1 Like
5

Hi everyone,

after discussion with the core team we figured out that remote debugging with test robots is possible by choosing unattended robot and running it on a machine that has testing runtimes assigned to it.

image
image1129×1016 126 KB

the missing test robot label might have lead to the confusion, if necessary we might change this.

1 Like
7

Hi @ThomasStocker,

That was great to know. I can confirm this is now working with the workaround you mentioned. Closing this thread.

image

Studio version
image

Orchestrator version
image

8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.