Open DanielPenning opened 1 month ago
How is this noticeable? When I press the Run button, a new terminal opens, if one is not already open, and it starts within 1 second. Where are the 3 seconds lost? And how do you measure that? What is the start and what is the end point? Maybe you record a short video clip to show it?
You have to bear in mind that it can't be quite as fast as on the console, as VSCode also has to connect to the test run, a new terminal may be opened, etc.
any news about this?
https://github.com/user-attachments/assets/1be263a1-0dfb-488a-b27f-6d4ba767240b
Sorry for the late response. I created a short video. I measured this in a simple way: Manually with a stop watch.
The video shows about 2.5-3s delay - so this is a bit better than originally written above. The video was made with a bit more recent versions (VS Code 1.92.2, RobotCode v0.87.0).
@d-biehl Is this helpful for you to reproduce?
Describe the bug Starting a test within RobotCode adds around 3s overhead compared to running the same .robot file from the CLI with
robot
. For short development loops this overhead is disturbing.To Reproduce Steps to reproduce the behavior:
empty.robot
in an otherwise empty directory.Expected behavior The command should execute the tests with almost the same speed than running the CLI. But:
robot empty.robot
takes around 500msDesktop (please complete the following information):