Lots of tests mix local and instance variables
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
Low
|
Brandon Palm |
Bug Description
A lot of tempest tests use instance variables for no reason when they're being treated as a local. This causes problems down the road because following the code is difficult to trace trough and there are unexpected results from multiple tests being run in the same class. We should only use instance variables when something truly needs to be used between 2 classes, like a resource tracking list.
An example of this is:
http://
look at the use of self.router
For some reason neutron tests and scenario tests in particular seem to be the worst offenders for doing this. But they are not alone. We really need some one to go through and clean these all up.
Changed in tempest: | |
assignee: | nobody → Brandon Palm (bapalm) |
Changed in tempest: | |
status: | Fix Released → In Progress |
Changed in tempest: | |
status: | In Progress → Fix Released |
Fix proposed to branch: master /review. openstack. org/211138
Review: https:/