In controller.py, line 70, there are assertions which assume robot code completes in a certain time duration. This is generally ok, but isn't a true assumption if the user is debugging a test and has a breakpoint in init. This also causes the test environment to continue on (launching another robot thread), which also get stuck at the same breakpoint.
Ideally, if a debugger is detected to be attached, the test suite should not fail and exit on timeout.
Problem description
In
controller.py
, line 70, there are assertions which assume robot code completes in a certain time duration. This is generally ok, but isn't a true assumption if the user is debugging a test and has a breakpoint in init. This also causes the test environment to continue on (launching another robot thread), which also get stuck at the same breakpoint.Ideally, if a debugger is detected to be attached, the test suite should not fail and exit on timeout.
Operating System
Windows
Installed Python Packages
Reproducible example code