luqitao 9c60f85ff8 Using assertIsNone() instead of assertEqual(None) ...

TrivilalFix

Following OpenStack Style Guidelines:
[1] http://docs.openstack.org/developer/hacking/#unit-tests-and-assertraises
[H203] Unit test assertions tend to give better messages for more
specific assertions. As a result, assertIsNone(...) is preferred over
assertEqual(None, ...) and assertIs(..., None)

Change-Id: Ifcac62f400ec15017a1db06ba889ed5e2d6a07f0

2017-03-21 22:19:04 -04:00

..

api

Clean up API

2016-05-23 13:25:04 -05:00

cli

Include OSC additions

2017-01-04 11:54:23 -06:00

command

Backport --os-beta-command

2016-06-08 10:17:14 -05:00

__init__.py

Begin moving bits to osc_lib

2016-05-12 16:07:24 -05:00

fakes.py

Calls to federated service providers using Keystone-to-Keystone

2016-12-21 11:43:17 -05:00

test_clientmanager.py

Calls to federated service providers using Keystone-to-Keystone

2016-12-21 11:43:17 -05:00

test_logs.py

Begin moving bits to osc_lib

2016-05-12 16:07:24 -05:00

test_shell.py

Decode argv to Unicode on py2

2016-08-05 14:43:08 -05:00

test_utils.py

Using assertIsNone() instead of assertEqual(None)

2017-03-21 22:19:04 -04:00

utils.py

Allow shell class to be overridden in test subclass

2016-07-25 14:19:51 -05:00