pytest-concurrent
pytest-concurrent copied to clipboard
reverbc
concurrently execute test cases with multi-thread, multi-process and gevent
When i try to run pytest i got this error: command: ``` python3 -m pytest --durations=0 --tb=short -n 8 -s ``` output: ``` Traceback (most recent call last): File "/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/runpy.py",...
Weird behavior faced when module / session scope fixture contains requests lib calls inside 1) Without: conftest.py: ``` @pytest.fixture(scope="module") def verify(): print("--> verify fixture setup called") yield print("teardown") ``` test_one.py:...
python 3.7.4 pytest 5.2.0 pytest-concurrent 0.2.2 gevent 1.4.0 Here is my test case, the expected result is: module_env_fixture runs once, global_env_fixture runs once, and all cases passed. Run the command...
Installed this package in a fresh virtual environment and tried to run a simple test file and got error message saying `No module named 'gevent'` ``` INTERNALERROR> Traceback (most recent...
On 469eebcdb728e2e32f7a9b4eb91bd044ebc90be1 (0.2.2) ``` ============================= test session starts ============================== platform linux -- Python 3.8.1, pytest-5.3.5, py-1.8.1, pluggy-0.13.1 -- /usr/bin/python cachedir: .pytest_cache rootdir: /build/python-pytest-concurrent/src/pytest-concurrent-469eebcdb728e2e32f7a9b4eb91bd044ebc90be1, inifile: setup.cfg plugins: concurrent-0.2.2 collecting ... collected...
It seems that you have been releasing to pypi without creating git tags, could you do that please?
The exit code is 0 when running in `concmode=mproc` and having a test that fails. When using `concmode=mthread` or not using pytest-concurrent exit code is 1 when test fails.
When running pytest 4.6.3 and pytest-concurrent 0.2.2 in `mproc` mode and using the argument ` --junitxml` I get the error ``` Traceback (most recent call last): File "/usr/lib/python3.6/multiprocessing/process.py", line 258,...
For some use cases, there might be some test cases that we want to run in sequential. We should have a decorator-like mechanism to support that. I propose to have...
