diff options
| author | Ahmed Nassar <a.moh.nassar00@gmail.com> | 2025-04-14 14:12:56 -0300 |
|---|---|---|
| committer | nessita <124304+nessita@users.noreply.github.com> | 2025-04-15 14:48:55 -0300 |
| commit | be402891cd78f484b7f67e486924975523516ced (patch) | |
| tree | d52b96b0b48d1b15dcc1182af0218b1efcfc87a6 /docs/topics/testing | |
| parent | abbcef52801f920caf72f4e2016c4999ea8b98ec (diff) | |
Fixed #36311 -- Unified spelling of "hardcode" and its variants in docs.
Co-authored-by: Natalia <124304+nessita@users.noreply.github.com>
Diffstat (limited to 'docs/topics/testing')
| -rw-r--r-- | docs/topics/testing/advanced.txt | 2 |
1 files changed, 1 insertions, 1 deletions
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. |