#32409: TestCase async tests are not transaction-aware
-------------------------------------+-------------------------------------
Reporter: David | Owner: nobody
Type: New feature | Status: closed
Component: Testing framework | Version: 3.1
Severity: Normal | Resolution: needsinfo
Keywords: TestCase, async, | Triage Stage: Accepted
transaction |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by David):
Replying to [comment:15 Mariusz Felisiak]:
> Closing as "needsinfo", since we don't have a reproducible scenario.
Hi Mariusz, sorry to not have replied earlier but I had provided a
complete test scenario in this repository: https://github.com/sevdog/test-
websocker-user-lock
Replying to [comment:8 David]:
> Here is a demo project with the use-case I described before:
https://github.com/sevdog/test-websocker-user-lock.
> I have setup both **py-test** (however something is still missing here,
since they work if run one-by-one but fails when run in sequence, I should
learn more about this library) and **django testcase**.
--
Ticket URL: <https://code.djangoproject.com/ticket/32409#comment:16>
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/064.4ad8b5fba39da0d310342569bc6b0d38%40djangoproject.com.
