#33356: "python manage.py test" fails, but running the individual TestCase pass
-------------------------------+--------------------------------------
Reporter: Dylan Yung | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 3.2
Severity: Normal | Resolution:
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 Dylan Yung:
Old description:
> There's some weird internal Django bug with views that use
> "transaction.atomic()" if you ping that view with multiple TestCase a
> weird bug will happen where there's a DB check at the end of tests after
> the DB has been torn down. I made 2 StackOverflow posts regarding this
> issue and found the fix as well. Hopefully there'll be an internal fix.
>
> https://stackoverflow.com/questions/70105907/django-full-test-suite-
> failing-when-adding-a-testcase-but-full-test-suite-pas/70312267#70312267
> https://stackoverflow.com/questions/70166752/django-serializer-throwing-
> invalid-pk-object-does-not-exist-when-setting-m
New description:
There's some weird internal Django bug with views that use
"transaction.atomic()" if you ping that view with multiple TestCase a
weird bug will happen where there's a DB check at the end of tests after
the DB has been torn down. I made 2 StackOverflow posts regarding this
issue and found the fix as well. Hopefully there'll be an internal fix.
Because Django tests the db transaction processing mechanism, the real
test part is finish and success, and then it will rollback the data（data
flush),so some db level check is no use and misleading.
so we need modify the foreign key check defer to make it get right result.
https://stackoverflow.com/questions/70105907/django-full-test-suite-
failing-when-adding-a-testcase-but-full-test-suite-pas/70312267#70312267
https://stackoverflow.com/questions/70166752/django-serializer-throwing-
invalid-pk-object-does-not-exist-when-setting-m
--
--
Ticket URL: <https://code.djangoproject.com/ticket/33356#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.f2929eb33f14680539fff73e3b8a9a8a%40djangoproject.com.
