9e46577ab8
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
|
||
---|---|---|
doc/source | ||
oslotest | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
lower-constraints.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
oslotest -- OpenStack Testing Framework and Utilities
The Oslo Test framework provides common fixtures, support for debugging, and better support for mocking results.
- Free software: Apache license
- Documentation: https://docs.openstack.org/oslotest/latest/
- Source: https://git.openstack.org/cgit/openstack/oslotest
- Bugs: https://bugs.launchpad.net/oslotest
- Release notes: https://docs.openstack.org/releasenotes/oslotest