Merge pull request #3135 from brianmaissy/doc/clarify_pytest_fixture_setup_with_fixture_that_returns_None
Clarify a possible confusion when using pytest_fixture_setup with fixture functions that return None
This commit is contained in:
		
						commit
						0d96a5bf90
					
				|  | @ -373,7 +373,15 @@ def pytest_runtest_logreport(report): | |||
| def pytest_fixture_setup(fixturedef, request): | ||||
|     """ performs fixture setup execution. | ||||
| 
 | ||||
|     Stops at first non-None result, see :ref:`firstresult` """ | ||||
|     :return: The return value of the call to the fixture function | ||||
| 
 | ||||
|     Stops at first non-None result, see :ref:`firstresult` | ||||
| 
 | ||||
|     .. note:: | ||||
|         If the fixture function returns None, other implementations of | ||||
|         this hook function will continue to be called, according to the | ||||
|         behavior of the :ref:`firstresult` option. | ||||
|     """ | ||||
| 
 | ||||
| 
 | ||||
| def pytest_fixture_post_finalizer(fixturedef, request): | ||||
|  |  | |||
|  | @ -0,0 +1 @@ | |||
| Clarify a possible confusion when using pytest_fixture_setup with fixture functions that return None. | ||||
		Loading…
	
		Reference in New Issue