Jukka Rauhala

Nice feature request and I would be more than happy to see this in Robot. Any chance to get priority for this one? In our project we have lot of...

No tasks. Everything is test cases. It just keeps loading. See number 2 from the picture below. If you take a look number 1 from the picture it somehow sees...

Plugin started successfully.  Seems that there's lock. I saw another bug report for RobotCode related to lock, is this something similar? 

Yes and that seems to solve the issue. However the lock warning still occurs.  However I need to add exact path to make it work. E.g.: C:\folder\folder..  Is...

I opened the VS Code again and parsing tests based on the paths in settings.json still takes 5mins or so but eventually it finds tests from my project. Lock warning...

"If you dont set the robotcode.robot.paths then robotcode looks in the current workspace path, also you can use relative paths here. So normally you don't need the this setting." That's...

Seems that it finds tests cases without `robotcode.robot.paths`. However, it takes looong time...

It takes time when it goes through the folders and when plugin goes through a robot file which contains resource file import where this resource file is not there. Same...

In other words... We have test files which takes a resource file information based on the --variable argument provided to Robot. All tests are using same variable name, see from...

Sorry late reply. Yes this can be closed. This issue was mainly when we do importing libraries using variables and variable value can be different based on what tests running...