From be402891cd78f484b7f67e486924975523516ced Mon Sep 17 00:00:00 2001 From: Ahmed Nassar Date: Mon, 14 Apr 2025 14:12:56 -0300 Subject: Fixed #36311 -- Unified spelling of "hardcode" and its variants in docs. Co-authored-by: Natalia <124304+nessita@users.noreply.github.com> --- docs/topics/testing/advanced.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/topics/testing') diff --git a/docs/topics/testing/advanced.txt b/docs/topics/testing/advanced.txt index 79d3f97f48..72373c6107 100644 --- a/docs/topics/testing/advanced.txt +++ b/docs/topics/testing/advanced.txt @@ -357,7 +357,7 @@ Advanced features of ``TransactionTestCase`` self.assertEqual(lion.pk, 1) Unless you are explicitly testing primary keys sequence numbers, it is - recommended that you do not hard code primary key values in tests. + recommended that you do not hardcode primary key values in tests. Using ``reset_sequences = True`` will slow down the test, since the primary key reset is a relatively expensive database operation. -- cgit v1.3