Use assertIsNone(...) instead of assertEqual(None, ...).
Ref£º http://docs.openstack.org/developer/hacking/#real-world-import-order-examples [H203] Use assertIs(Not)None to check for None (off by default) Unit test assertions tend to give better messages for more specific assertions. As a result, assertIsNone(...) is preferred over assertEqual(None, ...) and assertIs(None, ...), and assertIsNotNone(...) is preferred over assertNotEqual(None, ...) and assertIsNot(None, ...). Change-Id: I84b3304cae4284bdbad7d093cb6fa1d3d303ee52
This commit is contained in:
parent
a799fd8721
commit
c2dc8fbe1c
|
@ -59,7 +59,7 @@ class ServerWrapperTests(test.TestCase):
|
||||||
self.mox.ReplayAll()
|
self.mox.ReplayAll()
|
||||||
|
|
||||||
server = api.nova.Server(server, self.request)
|
server = api.nova.Server(server, self.request)
|
||||||
self.assertEqual(None, server.image_name)
|
self.assertIsNone(server.image_name)
|
||||||
|
|
||||||
|
|
||||||
class ComputeApiTests(test.APITestCase):
|
class ComputeApiTests(test.APITestCase):
|
||||||
|
|
Loading…
Reference in New Issue