Ben Nemec 9e46577ab8 Stop testing mock functionality ... There's no particular reason for us to be verifying mock's behavior. They have their own unit tests for doing that. This is specifically a problem right now because mock changed its behavior in 3.0.0 and broke this test: "Issue #36366: Calling stop() on an unstarted or stopped unittest.mock.patch() object will now return None instead of raising RuntimeError, making the method idempotent." Change-Id: I57db9bad15cab343e152615e115e2ba3ac4d87fe Closes-Bug: 1830429 (cherry picked from commit f8f6b14088)		2019-07-24 13:37:23 +00:00
..
__init__.py	move unit tests into the oslotest package	2016-02-18 12:44:16 +00:00
test_base.py	Stop testing mock functionality	2019-07-24 13:37:23 +00:00
test_createfile.py	move unit tests into the oslotest package	2016-02-18 12:44:16 +00:00
test_log.py	move unit tests into the oslotest package	2016-02-18 12:44:16 +00:00
test_mock_fixture.py	mock: Apply autospec to a mock's return_value	2018-03-29 04:57:48 -07:00
test_mockpatch.py	Using fixtures instead of deprecated mockpatch module	2017-07-12 23:47:58 +07:00
test_modules.py	A DisableModules fixture that removes modules from path	2016-07-06 15:48:24 +10:00
test_moxstubout.py	move unit tests into the oslotest package	2016-02-18 12:44:16 +00:00
test_output.py	make the CaptureOutput fixture easier to control	2018-03-19 16:35:17 -04:00
test_timeout.py	Add DEFAULT_TIMEOUT and TIMEOUT_SCALING_FACTOR	2018-09-23 08:29:01 -05:00