Fixed #29804 -- Added 'did you mean' suggestions for unsupported lookup error.

1 files changed, 16 insertions, 1 deletions

diff --git a/tests/lookup/tests.py b/tests/lookup/tests.py
index 45360963b2..d759bbadff 100644
--- a/tests/lookup/tests.py
+++ b/tests/lookup/tests.py
@@ -569,13 +569,28 @@ class LookupTests(TestCase):
         ):
             Article.objects.filter(pub_date_year='2005').count()
 
+    def test_unsupported_lookups(self):
         with self.assertRaisesMessage(
             FieldError,
             "Unsupported lookup 'starts' for CharField or join on the field "
-            "not permitted."
+            "not permitted, perhaps you meant startswith or istartswith?"
         ):
             Article.objects.filter(headline__starts='Article')
 
+        with self.assertRaisesMessage(
+            FieldError,
+            "Unsupported lookup 'is_null' for DateTimeField or join on the field "
+            "not permitted, perhaps you meant isnull?"
+        ):
+            Article.objects.filter(pub_date__is_null=True)
+
+        with self.assertRaisesMessage(
+            FieldError,
+            "Unsupported lookup 'gobbledygook' for DateTimeField or join on the field "
+            "not permitted."
+        ):
+            Article.objects.filter(pub_date__gobbledygook='blahblah')
+
     def test_relation_nested_lookup_error(self):
         # An invalid nested lookup on a related field raises a useful error.
         msg = 'Related Field got invalid lookup: editor'