system tests execution will result in an error when executed in a forked version of the repository

[christophkloeffel]

several factors like:

lobster/tests-system/testrunner.py

Line 81 in 5fe5aab

if root.name != "lobster":

-> the local repository folder has to be named "lobster", otherwise you will get an error

lobster/tests-system/lobster-online-report/rbt-valid-flow/valid-scenario/expected-output/expected-output.lobster

Line 14 in 5fe5aab

"gh_root": "https://github.com/bmw-software-engineering/lobster",

-> you need to adapt the expected output when working from a fork since the URL will be different

I had to adapt those in my forked lobster repository to be able to execute make system-tests successfully

Consider changing those factors of the system tests to improve the ease of contributing from a forked repo

[phiwuu]

Thanks for your feedback!

lobster/tests-system/testrunner.py

Line 81 in 5fe5aab

if root.name != "lobster":

is a sanity check. If testrunner.py is moved to a different folder (for whatever refactoring reason), then I wanted to make sure that the runner either finds the root directory, or fails for sure. I wanted to prevent a situation where the runner thinks there a no tests to execute, and the CI reports a "green" status. We could remove the line to fix your issue.