Is your feature request related to a problem? Please describe.
There are alternative runner implementations that may need to be supported for older projects. The work required to migrate other test cases to a runner like Kalash might be too much for such projects.
Describe the solution you'd like
The runner could basically encapsulate older test suites and simply hand off the work to a different runner implementation if existing test cases cannot be refactored. The configuration parameters for xenorunners could be included in the config section of the YAML file. This way the invocation of the xenorunner could be performed without substantial changes to the CLI interface of Kalash.
Describe alternatives you've considered
Refactoring the test case in an automated way would be an alternative option. For some projects this will likely be not feasible. Python test cases have inherently too many degrees of freedom to figure out a stable translation tool before the Sun becomes a Red Giant and swallows the Earth whole.
Additional context
Existing test cases are a matter of internal discussions and will never be shared with the public. Any tests done against xenorunners will be based on mocks that emulate some aspects of existing systems that need to be supported.
Is your feature request related to a problem? Please describe. There are alternative runner implementations that may need to be supported for older projects. The work required to migrate other test cases to a runner like Kalash might be too much for such projects.
Describe the solution you'd like The runner could basically encapsulate older test suites and simply hand off the work to a different runner implementation if existing test cases cannot be refactored. The configuration parameters for xenorunners could be included in the
configsection of the YAML file. This way the invocation of the xenorunner could be performed without substantial changes to the CLI interface of Kalash.Describe alternatives you've considered Refactoring the test case in an automated way would be an alternative option. For some projects this will likely be not feasible. Python test cases have inherently too many degrees of freedom to figure out a stable translation tool before the Sun becomes a Red Giant and swallows the Earth whole.
Additional context Existing test cases are a matter of internal discussions and will never be shared with the public. Any tests done against xenorunners will be based on mocks that emulate some aspects of existing systems that need to be supported.