-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
Parallel test execution #225
Comments
Tavern should work fine with pytest-xdist (I used to use it in the past, and just tried it now and it works fine with the integration tests), have you run into any problems with it? eg:
|
Thanks for your reply great to hear from you. There is no documentation about parallel test execution through tavern. I can use all of the functionality available in pytest-xdist library .Could you please confirm. |
There isn't anything in Tavern that should break pytest-xdist, so you should be able to use it just fine. If you do run into any problems with it, feel free to make an issue about it. |
@michaelboulton in if I want to run two tavern tests in parallel (gaurantee that my server gets two tests at the same time), how can I achieve this in the tavern yaml? |
im gonna make my own issue |
Is there any possibility to run test tests in parallel using tavern. Consider a scenario , through pytest parser utility functions receiving the input from command line and have to use it in our tests. For example, have command line flag as --user a b (input is in list). By using this test i have to cover the test scenarios for both users in parallel. Through pytest we can use pytest-xdist and parameterize option to do it. Refer the below links ,
https://stackoverflow.com/questions/49699477/is-it-possible-to-execute-the-same-test-in-parallel-in-pytest
https://stackoverflow.com/questions/47439103/how-to-execute-tests-in-a-test-suite-in-parallel
https://github.com/pytest-dev/pytest-xdist
Requirement would be like test scripts should be reusable and based upon the user type test scenarios has to be validated and reported in parallel. Right now fixture don't have support for parameterization support to do this like in Pytest.
The text was updated successfully, but these errors were encountered: