lingyongxu ee9458a250 Using assertIsNone() instead of assertEqual(None) ... 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: If4db8872c4f5705c1fff017c4891626e9ce4d1e4		2017-06-07 14:05:53 +08:00
..
account	Make timestamp setting to be consistent in test loop	2017-01-12 17:44:10 -08:00
cli	Merge "Add Composite Ring Functionality"	2017-05-18 10:18:31 +00:00
common	Using assertIsNone() instead of assertEqual(None)	2017-06-07 14:05:53 +08:00
container	Using assertIsNone() instead of assertEqual(None)	2017-06-07 14:05:53 +08:00
obj	Using assertIsNone() instead of assertEqual(None)	2017-06-07 14:05:53 +08:00
proxy	Merge "Follow-up for per-policy proxy configs"	2017-06-05 08:50:45 +00:00
test_locale	monkeypatch thread for keystoneclient	2015-11-03 16:36:19 +01:00
__init__.py	Merge "Clean up how PatchPolicies works"	2017-05-25 09:20:52 +00:00
helpers.py	Open-code eventlet.listen()	2017-05-11 01:39:14 -06:00