diff options
| author | Josef Angstenberger <code@jtxa.de> | 2021-05-06 19:24:28 (GMT) |
|---|---|---|
| committer | Josef Angstenberger <code@jtxa.de> | 2021-05-07 15:00:17 (GMT) |
| commit | 7072d837720d25bcd1906764e3eb23b940e4e4a4 (patch) | |
| tree | 9993842ff4bc18c617f343e2eeae28ebaa767e39 /Help/prop_test | |
| parent | 03b1140ddc6341aec37f55437cdabba8fcdfe906 (diff) | |
| download | CMake-7072d837720d25bcd1906764e3eb23b940e4e4a4.zip CMake-7072d837720d25bcd1906764e3eb23b940e4e4a4.tar.gz CMake-7072d837720d25bcd1906764e3eb23b940e4e4a4.tar.bz2 | |
Help: Fix typos and spelling in documentation
Diffstat (limited to 'Help/prop_test')
| -rw-r--r-- | Help/prop_test/FIXTURES_REQUIRED.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Help/prop_test/FIXTURES_REQUIRED.rst b/Help/prop_test/FIXTURES_REQUIRED.rst index d92808a..f850830 100644 --- a/Help/prop_test/FIXTURES_REQUIRED.rst +++ b/Help/prop_test/FIXTURES_REQUIRED.rst @@ -35,9 +35,9 @@ The concept of a fixture is different to that of a resource specified by set of tests which share setup and cleanup requirements, whereas a resource lock has the effect of ensuring a particular set of tests do not run in parallel. Some situations may need both, such as setting up a database, -serialising test access to that database and deleting the database again at the +serializing test access to that database and deleting the database again at the end. For such cases, tests would populate both ``FIXTURES_REQUIRED`` and -:prop_test:`RESOURCE_LOCK` to combine the two behaviours. Names used for +:prop_test:`RESOURCE_LOCK` to combine the two behaviors. Names used for :prop_test:`RESOURCE_LOCK` have no relationship with names of fixtures, so note that a resource lock does not imply a fixture and vice versa. |