You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on a project comprising three modules: Module A, Module B, and Module C.
Each module has its own set of functionalities and endpoints. Within the project structure, I've established a common module (module-common) housing a test suite and a template for tests. The template for tests within this common module is designed to be used across all three modules.
My objective is to run these tests in parallel across modules, leveraging the xdist plugin, while ensuring that within each module, the tests execute sequentially. This is crucial to prevent conflicts arising from simultaneous access to the same endpoint within a module.
Requirements: Utilize the xdist plugin to enable parallel execution of tests. Ensure sequential execution of tests within each individual module to prevent endpoint conflicts. Current Setup: Project Structure: Module A
Conftest generating tests from Module-Common template Module B
Conftest generating tests from Module-Common template Module-Common
Test suite
Test template
Conftest generating tests from Module-Common template Desired Outcome:
Tests across Module A, Module B, and Module-Common run in parallel.
Tests within each module execute sequentially to avoid endpoint conflicts. Questions:
How can I configure xdist to enable parallel test execution? What adjustments should be made to ensure sequential execution within each module? Are there any best practices or recommended approaches for achieving this setup?
In addition, there are tests within the 'common' module that do not require endpoints and can be executed concurrently with other tests.
Any insights or guidance on this matter would be greatly appreciated!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm currently working on a project comprising three modules: Module A, Module B, and Module C.
Each module has its own set of functionalities and endpoints. Within the project structure, I've established a common module (module-common) housing a test suite and a template for tests. The template for tests within this common module is designed to be used across all three modules.
My objective is to run these tests in parallel across modules, leveraging the xdist plugin, while ensuring that within each module, the tests execute sequentially. This is crucial to prevent conflicts arising from simultaneous access to the same endpoint within a module.
Requirements: Utilize the xdist plugin to enable parallel execution of tests. Ensure sequential execution of tests within each individual module to prevent endpoint conflicts.
Current Setup:
Project Structure:
Module A
Conftest generating tests from Module-Common template
Module B
Conftest generating tests from Module-Common template
Module-Common
Test suite
Test template
Conftest generating tests from Module-Common template
Desired Outcome:
Tests across Module A, Module B, and Module-Common run in parallel.
Tests within each module execute sequentially to avoid endpoint conflicts.
Questions:
How can I configure xdist to enable parallel test execution? What adjustments should be made to ensure sequential execution within each module? Are there any best practices or recommended approaches for achieving this setup?
In addition, there are tests within the 'common' module that do not require endpoints and can be executed concurrently with other tests.
Any insights or guidance on this matter would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions