[Django] #33325: When running full test suite Django test fails, but when running TestCase classes individually works just fine
Django
classes individually works just fine
---------------------------------------------+------------------------
Reporter: DexiongYung | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 3.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------------+------------------------
So when running the full test suite as in `python manage.py test` my
HomeTests fail, but when running individually all my TestCase pass. Also I
added a need TestCase called `ExploreFeedTests` and when I comment that
out my test suite succeeds. Keep in my individually my TestCases pass.
Apparently this is an issue that has existed in Django for quite some time
now.
https://stackoverflow.com/questions/70105907/django-full-test-suite-
failing-when-adding-a-testcase-but-full-test-suite-
pas?noredirect=1#comment123974351_70105907
https://stackoverflow.com/questions/29792439/why-would-a-django-test-fail-
only-when-the-full-test-suite-is-run
https://groups.google.com/g/django-users/c/OedhPc5bXYE/m/7C-
1r3LkUesJ?pli=1
--
Ticket URL: <https://code.djangoproject.com/ticket/33325>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
classes individually works just fine
Reporter: DexiongYung | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 3.2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Description changed by DexiongYung:
Old description:
> So when running the full test suite as in `python manage.py test` my
> HomeTests fail, but when running individually all my TestCase pass. Also
> I added a need TestCase called `ExploreFeedTests` and when I comment that
> out my test suite succeeds. Keep in my individually my TestCases pass.
> Apparently this is an issue that has existed in Django for quite some
> time now.
>
> https://stackoverflow.com/questions/70105907/django-full-test-suite-
> failing-when-adding-a-testcase-but-full-test-suite-
> pas?noredirect=1#comment123974351_70105907
>
> https://stackoverflow.com/questions/29792439/why-would-a-django-test-
> fail-only-when-the-full-test-suite-is-run
>
> https://groups.google.com/g/django-users/c/OedhPc5bXYE/m/7C-
> 1r3LkUesJ?pli=1
New description:
So when running the full test suite as in `python manage.py test` my
HomeTests fail, but when running individually all my TestCase pass. Also I
added a need TestCase called `ExploreFeedTests` and when I comment that
out my test suite succeeds. Keep in my individually my TestCases pass.
Apparently this is an issue that has existed in Django for quite some time
now. I'm running Django 3.2.9
https://stackoverflow.com/questions/70105907/django-full-test-suite-
failing-when-adding-a-testcase-but-full-test-suite-
pas?noredirect=1#comment123974351_70105907
https://stackoverflow.com/questions/29792439/why-would-a-django-test-fail-
only-when-the-full-test-suite-is-run
https://groups.google.com/g/django-users/c/OedhPc5bXYE/m/7C-
1r3LkUesJ?pli=1
--
--
Ticket URL: <https://code.djangoproject.com/ticket/33325#comment:1>
Django
classes individually works just fine
Reporter: Dylan Yung | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: 3.2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Claude Paroz):
* status: new => closed
* resolution: => invalid
Comment:
This is a typical case where some of your test has side effects that
affect other tests when run in combination. But you didn't demonstrate how
Django would be faulty at this regard. So please try to
[wiki:TicketClosingReasons/UseSupportChannels get help], and reopen with
more details if you can show a problem in Django itself.
--
Ticket URL: <https://code.djangoproject.com/ticket/33325#comment:2>