Session scoped fixtures for avoiding recreation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, python
- Domain
- documentation, testing
Research direction
Start by checking the existing pytest-celery documentation and the test-cluster lifecycle, then compare the requested session-scoped behavior with the pytest-docker-tools setup mentioned in the issue. Done means documenting whether cluster reuse is supported and explaining the configuration or limitation clearly.
Written by the indexing model from the issue text.
Description
Checklist
- I have checked the issues list
for similar or identical bug reports. - I have checked the pull requests list
for existing proposed fixes. - I have checked the commit log
to find out if the bug was already fixed in the main branch. - I have included all related issues and possible duplicate issues in this issue
(If there are none, check this box anyway).
Related Issues and Possible Duplicates
Related Issues
- None
Possible Duplicates
- None
Description
I am a new user of the package and I really like it, but I am not able to figure out a fundamental question through the documentation. How can I prevent the test cluster from getting recreated between test runs in the same session.
To be fair, I don't see any part of documentation that claims that this is possible. I just thought, when reading the docs and writing my tests, that session based setup is possible, because otherwise would be a bit too slow.
Can you please confirm if this is indeed not possible with pytest-celery? And if so, should I just implement my own test setup using pytest-docker-tools? I think I could also write my test cases in one test function, but I would like to avoid it.
Suggestions
- Dominant language
- Python
- Stars
- 83
- Forks
- 18
- Avg merge
- 4h 13m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from celery/pytest-celery
-
ModuleNotFoundError: No module named 'pkg_resources' in worker defaults on Python 3.13+Possibly taken @auvipy claimed this 12 days ago. Openbug
celery/pytest-celery#587 · 1 assignee ·
-
feature
Difficulty 3/5 1-2 days Newbie friendliness 45/100
celery/pytest-celery#463 · 1 comment ·
-
`celery_worker` fixture name colides with `celery_worker` fixture from `celery.contrib.pytest`May be free again @Nusnus claimed this 645 days ago, and no pull request is open. Openbug
celery/pytest-celery#442 · 7 comments · 5 reactions · 1 assignee ·
-
Missing documentation on how to include source codeMay be free again @Nusnus claimed this 328 days ago, and no pull request is open. Opendocumentation
celery/pytest-celery#439 · 1 assignee ·
All issues in celery/pytest-celery
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
AI bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AUTO-MAS-Project/AUTO-MAS#1960 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
btclib-org/btclib-wallet#872 ·
Maintainers usually reply within 1 day
-
[Bug]: Scheduled returns scan all accepted minion keys causing extreme loadPossibly taken A pull request linked to this issue is open or already merged. Openbug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
saltstack/salt#70789 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
btclib-org/btclib#3093 ·
Maintainers usually reply within 1 day