[unittest] unable to assert on deprecation warnings
Bug #1449009 reported by
Pavel Boldin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Rally |
Fix Released
|
Low
|
Pavel Boldin | ||
Bug Description
The unittests are unable to assert on the presence of a deprecation warning in the logs.
Add an appropriate context manager that will allow to catch logs and assert on their contents as well as retrieve them.
| Changed in rally: | |
| assignee: | nobody → Pavel Boldin (pboldin) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to rally (master) | #1 |
| Changed in rally: | |
| status: | In Progress → Fix Committed |
| Changed in rally: | |
| milestone: | none → 0.0.4 |
| Changed in rally: | |
| importance: | Undecided → Low |
| Changed in rally: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2538a2cf5a10818
Author: Pavel Boldin <email address hidden>
Date: Thu Apr 16 19:10:46 2015 +0300
Add `LogCatcher' context manager
Add `LogCatcher' context manager that records all the log messages
issued by the code inside the context. User can then check if there
is a message with the particular content or simply retrieve all
messages.
Change-Id: If0bb5f3e8f4d8a
Closes-Bug: #1449009