diff options
| author | David Smith <smithdc@gmail.com> | 2025-07-25 10:24:17 +0100 |
|---|---|---|
| committer | nessita <124304+nessita@users.noreply.github.com> | 2025-08-25 10:51:10 -0300 |
| commit | f81e6e3a53ee36e3f730a71aa55a5744982dd016 (patch) | |
| tree | 44a4fdd64e2d1489d80b1af8bd1ac3c7af3ad0dd /docs/topics/testing/overview.txt | |
| parent | 4286a23df64f6ce3b9b6ed097f4d1aac7d9e0de4 (diff) | |
Refs #36485 -- Rewrapped docs to 79 columns line length.
Lines in the docs files were manually adjusted to conform to the
79 columns limit per line (plus newline), improving readability and
consistency across the content.
Diffstat (limited to 'docs/topics/testing/overview.txt')
| -rw-r--r-- | docs/topics/testing/overview.txt | 19 |
1 files changed, 10 insertions, 9 deletions
diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt index 80e6663f6b..cafd9dd883 100644 --- a/docs/topics/testing/overview.txt +++ b/docs/topics/testing/overview.txt @@ -11,8 +11,8 @@ Writing and running tests reference </topics/testing/tools>`, and the :doc:`advanced testing topics </topics/testing/advanced>`. -This document is split into two primary sections. First, we explain how to write -tests with Django. Then, we explain how to run them. +This document is split into two primary sections. First, we explain how to +write tests with Django. Then, we explain how to run them. Writing tests ============= @@ -187,12 +187,12 @@ test database is created by the user specified by :setting:`USER`, so you'll need to make sure that the given user account has sufficient privileges to create a new database on the system. -For fine-grained control over the character encoding of your test -database, use the :setting:`CHARSET <TEST_CHARSET>` TEST option. If you're using -MySQL, you can also use the :setting:`COLLATION <TEST_COLLATION>` option to -control the particular collation used by the test database. See the -:doc:`settings documentation </ref/settings>` for details of these -and other advanced settings. +For fine-grained control over the character encoding of your test database, use +the :setting:`CHARSET <TEST_CHARSET>` TEST option. If you're using MySQL, you +can also use the :setting:`COLLATION <TEST_COLLATION>` option to control the +particular collation used by the test database. See the :doc:`settings +documentation </ref/settings>` for details of these and other advanced +settings. If using an SQLite in-memory database with SQLite, `shared cache <https://www.sqlite.org/sharedcache.html>`_ is enabled, so you can write tests @@ -212,7 +212,8 @@ with ability to share the database between threads. .. seealso:: - The :ref:`advanced multi-db testing topics <topics-testing-advanced-multidb>`. + The :ref:`advanced multi-db testing topics + <topics-testing-advanced-multidb>`. .. _order-of-tests: |