mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-04-14 20:34:36 +00:00
Code Issues 32 Releases Wiki Activity

Removed obsolete test_get_or_create_raises_IntegrityError_plus_traceback() test.

Browse Source 
This test was added in 31b1cbc623c246570e7301c0334df938d840638f, but is
no longer needed, as the fix was reverted in
746caf3ef821dbf7588797cb2600fa81b9df9d1d without any consequences, so
it now tests Python behavior rather than Django. Moreover, traceback
introspection is problematic for .pyc-only installations.
This commit is contained in:
Mariusz Felisiak 2024-02-21 11:50:22 +01:00 committed by GitHub
parent abe6c1f93e
commit a269d8d1d8
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 0 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
tests/get_or_create/tests.py
View File

@ -227,19 +227,6 @@ class GetOrCreateTestsWithManualPKs(TestCase):
ManualPrimaryKeyTest.objects.get_or_create(id=1, data="Different")
self.assertEqual(ManualPrimaryKeyTest.objects.get(id=1).data, "Original")
def test_get_or_create_raises_IntegrityError_plus_traceback(self):
"""
get_or_create should raise IntegrityErrors with the full traceback.
This is tested by checking that a known method call is in the traceback.
We cannot use assertRaises here because we need to inspect
the actual traceback. Refs #16340.
"""
try:
ManualPrimaryKeyTest.objects.get_or_create(id=1, data="Different")
except IntegrityError:
formatted_traceback = traceback.format_exc()
self.assertIn("obj.save", formatted_traceback)
def test_savepoint_rollback(self):
"""
The database connection is still usable after a DatabaseError in