From ebbd602687c46e34089963e4a06183e5f9774db0 Mon Sep 17 00:00:00 2001 From: jfs Date: Mon, 9 Dec 2024 13:47:13 +0300 Subject: [PATCH] docs: describe when UsageError is raised for loop_scope="class" marker before that: docs claimed (erroneously) the opposite of the actual (and intended) behavior. --- docs/reference/markers/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/markers/index.rst b/docs/reference/markers/index.rst index 6e9be1ca..cb86cf42 100644 --- a/docs/reference/markers/index.rst +++ b/docs/reference/markers/index.rst @@ -25,7 +25,7 @@ The following code example provides a shared event loop for all tests in `TestCl .. include:: class_scoped_loop_strict_mode_example.py :code: python -Requesting class scope with the test being part of a class will give a *UsageError*. +If you request class scope for a test that is not part of a class, it will result in a *UsageError*. Similar to class-scoped event loops, a module-scoped loop is provided when setting mark's scope to *module:* .. include:: module_scoped_loop_strict_mode_example.py