misused asserts in unittests
Bug #1445131 reported by
Elvis Teixeira
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
In Progress
|
Low
|
Kairo Araujo |
Bug Description
In the trove unit tests there are some assertEquals(
python methods assertTrue() and assertFalse() would be used. Change this to be compliant
with the unittest module's idiom and make any reader explicitly know we are checking for a
boolean condition. Maybe writing a hack rule to prevent reintroduction of code like that
would also be fine.
Changed in trove: | |
assignee: | nobody → Elvis Teixeira (elvis-teixeira) |
status: | New → In Progress |
Changed in trove: | |
importance: | Undecided → Low |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/178184
Review: https:/