RobotCode - whole project marked as test suite

Hi Daniel

First of all, thank you for your comprehensive answer.
I could not find any documentation for __init__.robot - could you provide a link, please?

I’ll try to describe our project structure so that it’s less of a black box to you.

I understand that you can have a project/directory, with tests folder which contains several suites of suites, and see it as the robotcode.robot.paths, but it is not the only way of structuring the project.

To run the tests from the root directory - I can still be in the root directory and run only a single suite deep in my structure without having the suite explicitly linked to all the levels above, which makes the HTML report unnecessarily deep (even in your tutorial you have to go through two more levels to check a single screenshot - what benefits does it bring?), and that’s what I expect from the Play button.


My issue would be solved if I could set the robotcode.robot.paths as ${fileDirname}.

To the Sikuli and libraries stuff - I am not complaining about my Sikuli not working, I expect it not to work. What I don’t get is why the RobotCode even touches it when I am trying to run a test case from a test suite that does not even mention the library :man_shrugging: