I was using pytest-xdist to run tests in parallel, but my suite setup is very huge and bulky, which I want to avoid running multiple times in each tests execution.
While I was using pytest-xdist to run all the tests in parallel, I came across the problem where my suite setup (fixtures) are running before every test execution which increases the execution time of all the test cases.
Is there any way to avoid the fixture execution before every test execution in pytest parallel execution?
How to run setup (fixture) once and then tests in parallel
3.3k Views Asked by Subodh Agnihotri At
1
There are 1 best solutions below
Related Questions in PYTHON
- new thread blocks main thread
- Extracting viewCount & SubscriberCount from YouTube API V3 for a given channel, where channelID does not equal userID
- Display images on Django Template Site
- Difference between list() and dict() with generators
- How can I serialize a numpy array while preserving matrix dimensions?
- Protractor did not run properly when using browser.wait, msg: "Wait timed out after XXXms"
- Why is my program adding int as string (4+7 = 47)?
- store numpy array in mysql
- how to omit the less frequent words from a dictionary in python?
- Update a text file with ( new words+ \n ) after the words is appended into a list
- python how to write list of lists to file
- Removing URL features from tokens in NLTK
- Optimizing for Social Leaderboards
- Python : Get size of string in bytes
- What is the code of the sorted function?
Related Questions in PYTEST
- Anyway to specify the type of report on .coveragerc?
- Cleanest method for creating a pytest test fixture that takes in dynamic text data
- How to instantiate an object once
- pytest (py.test) very slow startup in cygwin
- Can't connect to MySQL server on ********* '1040, u'Too many connections' only from certain directory
- Concatenate a list of series into a uid
- Monkey patch python with statement
- how to prevent py.test run new webdriver each time when start new method
- pytest modules using os.environ - How do I test it correctly?
- How can I show verbose py.test diffs without verbose test progress?
- Py.Test getting remaining test case count
- How to mock HTTP authentication in Flask for testing?
- Include package in Spark local mode
- How to override pytest.ini when running tests from the command line?
- Django/Selenium : request contains Anonymous user after successfully login
Related Questions in PYTEST-XDIST
- Why does pytest + xdist not capture output?
- pytest-parallel not honouring module-scope fixtures
- Pytest-xdist cannot run after being packaged with pyinstaller
- examples are not appearing in the feature object and scenario object of pytest-bdd
- Is there a downside to using too many threads with pytest-xdist?
- Pytest-xdist 3.40 and higher not honoring --exitfirst
- Set tests order while running tests in parallel
- Pytest parallel can I run test after all parallel finished?
- Can we run multiple marker in parallel?
- Running tests on remote machine and capture output using pytest
- Why some testcases fail in Pytest even after their dependencies have run successfully before them?
- pytest-xdist generate random & uniqe ports for each test
- Pytest Xdist parallel execution, prevent recreating the database
- How can I adjust the number of threads with pytest + xdist?
- pytest issues with a session scoped fixture and asyncio
Related Questions in PYTEST-PARALLEL
- pytest-parallel not honouring module-scope fixtures
- Pytest-parallel executing test case twice
- Py.Test Can't find pytest-parallel when invoked programmatically
- How to run setup (fixture) once and then tests in parallel
- Pytest-parallel lib. How to get worker id like in pytest-xdist?
- Runtime statistics for parallel test function calls (with pytest-benchmark or some other plugin)
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Specifying a session scope for your fixtures would usually be the way to go, if you were not using pytest-xdist. Fixtures with session scope won't work as expected when you're using pytest-xdist, because the tests are being executed in separate processes.
It is a known limitation of pytest-xdist: https://pytest-xdist.readthedocs.io/en/stable/how-to.html#making-session-scoped-fixtures-execute-only-once
If it's data that you can store in a file, for example, there is a suggested workaround in the documentation. If it's a process that you need to run first, then I'm afraid you may have to move this outside of your tests.
There are open issues on their GitHub repo concerning this issue, such as this one: https://github.com/pytest-dev/pytest-xdist/issues/271