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
..
__init__.py	Initial commit of Swift code	2010-07-12 17:03:45 -05:00
test_auditor.py	Added unit test cases for container/auditor.py	2015-11-20 16:07:17 +00:00
test_backend.py	Fix using filter() to meet python2,3	2016-09-22 07:32:38 +07:00
test_reconciler.py	Using assertIsNone() instead of assertEqual(None)	2017-06-07 14:05:53 +08:00
test_replicator.py	Update container on fast-POST	2016-03-03 14:25:10 +00:00
test_server.py	Using assertIsNone() instead of assertEqual(None)	2017-06-07 14:05:53 +08:00
test_sync_store.py	Fixing typo in unit test	2016-02-03 08:59:53 +02:00
test_sync.py	Using assertIsNone() instead of assertEqual(None)	2017-06-07 14:05:53 +08:00
test_updater.py	Open-code eventlet.listen()	2017-05-11 01:39:14 -06:00