In our project, we have a process-level cache. On Windows with nose test framework, we can use --process-restartworker to isolate each ScenarioTest in a different process. However, with pytest if multiple ScenarioTests are assigned to the same process, there will be conflicts in the cache.
With pytest, is there an equivalent of --process-restartworker? If --forked doesn't work on Windows, is it possible to just restart the process instead?
Also see:
https://stackoverflow.com/questions/48234032/run-py-test-test-in-different-process
https://stackoverflow.com/questions/45462374/mark-test-to-be-run-in-independent-process
https://stackoverflow.com/questions/51187188/pytest-run-each-test-in-a-separate-process
In our project, we have a process-level cache. On Windows with nose test framework, we can use
--process-restartworkerto isolate eachScenarioTestin a different process. However, with pytest if multipleScenarioTests are assigned to the same process, there will be conflicts in the cache.With pytest, is there an equivalent of
--process-restartworker? If--forkeddoesn't work on Windows, is it possible to just restart the process instead?Also see:
https://stackoverflow.com/questions/48234032/run-py-test-test-in-different-process
https://stackoverflow.com/questions/45462374/mark-test-to-be-run-in-independent-process
https://stackoverflow.com/questions/51187188/pytest-run-each-test-in-a-separate-process