Thanks in advance all.Īs I wrote in the other thread, this is currently not possible.

Would be happy if it only worked on robot side as well. I currently have my launcher.json file configured like so:ĭoes anyone know how I could configure this extension for this scenario like I am for python backend to debug my robot cases/custom keywords? Would be a great bonus if I could step into the robot keywords directly to the implementation in the python backend. Great to step through everything in the back end. At this point the VS code breakpoints will work from the GUI from all of my sub Libraries that are utilized by my test suites. At this point, I go to the VS code debug tab and hit play. I then run my run_tests.py script to start the process, it will hold for the debugger to attach. Unless a host and port are specified, host defaults to 127.0.0.1 #5678 is the default attach port in the VS Code debug configurations. I can currently debug the python backend with the below launcher.json settings and this added in my main file to utilize debugpy. In this run_tests.py, it will configure the robot environment after talking with the device and launch robot to run testing on the device’s GUI/API. I have a module called run_tests.py that I execute from CLI that interfaces with this device. For my testing, I do system testing on a physical device. Everything works great, code completion, lookup/intellisense works after configuring resource/libraries and extension settings, albeit the extension is a bit slow for our larger project to parse everything. I am currently set in my environment to properly use the Robot Code extension. First time posting here, hoping that someone can give me a hand with debugging my robot files for my specific scenario.

Visual studio code python support