-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support parallel execution of tests #20
Comments
I have a patch that makes this possible. However, it is backwards incompatible because step functions now need to take the context as a parameter. |
Hi siddhi! Can you provide a link to the patch, please? |
Hi jerico, this is the commit that I use - silverstripesoftware@c1df773 |
Hi siddhi! Thanks for that. Roman, now that we have a patch, is this something to be considered for the milestone release? Or will this break backwards compat? |
Indeed it does break backwards compatibility. siddhi, how are you running parallel tests. Is it using nose's nose.plugin.multiprocess plugin? I haven't tried running parallel tests yet, but it seems like if they run in separate processes then the global state in the contexts shouldn't matter. Please correct me if I'm wrong. |
It is currently not possible to run tests in parallel.
scc is a global variable, so each test writes to it and conflicts with other test that are running and might also be using scc.
Instead a new scc object should be created for each test and made available for the steps to use, so that multiple tests running in parallel will be using their own copy of their local context without interference from other tests that are running.
The text was updated successfully, but these errors were encountered: