| commit | 3dcbdafdf97f3d8034703f91c640e8510f28071f | [log] [tgz] |
|---|---|---|
| author | howardlee <lihongweibj@inspur.com> | Wed Nov 16 14:51:24 2016 +0800 |
| committer | howardlee <lihongweibj@inspur.com> | Wed Nov 16 14:51:24 2016 +0800 |
| tree | 79830f8ca1f18c358761e6241ac68b85e149a772 | |
| parent | 1c82f7ebbe7a402581ba1c541858f944013346fb [diff] |
Use assertIs(Not)None to check for None [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, ...). Off by default. More information, see: http://docs.openstack.org/developer/hacking/#unit-tests-and-assertraises Change-Id: I73a9ed3e145b8f36c110725d148baf1fb0aef957