| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
This has enough users around OpenStack to justify adding it to
'fixtures' proper. It's intentionally dumb, since the main purpose of
this is to avoid people calling `resetwarnings` in their variant of the
fixture, as that clears *all* filters including those we don't control.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
|
| |
|
|
| |
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
|
| |
|
|
| |
CompoundFixture combines multiple fixtures into one.
|
| |
|
|
|
|
|
|
| |
Fixture.setUp should no longer be overridden in subclasses. Instead
override _setUp. This permits the Fixture base class to detect failures
during _setUp and trigger any registered cleanups, attach any details
to the failure exception and propogate that to callers.
(Robert Collins, #1456361, #1456353)
|
| |
|
|
|
| |
This fixture provides an easy usage for mock (unittest.mock in
Python 3).
|
| |
|
|
|
|
|
|
|
|
| |
Capturing the warnings module output (which is typically used
for deprecating code or functions or modules) is quite useful and
is a frequent operation that can be required to perform. So provide
a fixture that is similar (but not the same) as the warnings
``catch_warnings`` context manager that can be used to gather all
warnings emitted and allows people to later analyze them to ensure
they are as they expect.
|
| | |
|
| | |
|
| | |
|
|
|
No functional changes.
|
