Currently RobotFramework Core runs all .robot files in the same process.
This strategy makes that data is inherited implicitly from previous executions into the current test execution. Use of implicitly inherited data can cause problems when it creates a dependency between .robot files in the test case execution. Especially in large test suites this can create big problems.
In order to have good code, the inheritance of data has to be done by means of syntax elements or keywords instead.
Goal of this task is to create a prototype which runs each .robot file in a separate process (similar TML does) and provide for each .robot file new, clean environment.
Currently RobotFramework Core runs all .robot files in the same process. This strategy makes that data is inherited implicitly from previous executions into the current test execution. Use of implicitly inherited data can cause problems when it creates a dependency between .robot files in the test case execution. Especially in large test suites this can create big problems. In order to have good code, the inheritance of data has to be done by means of syntax elements or keywords instead.
Goal of this task is to create a prototype which runs each .robot file in a separate process (similar TML does) and provide for each .robot file new, clean environment.
This is also a preparation for threading.