qinchunhua e68032929c Using assertIsNone() instead of assertIs(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: I52ecf3f4945c4cb99f6350afca1c51d88b16bb8d

2016-10-10 08:50:21 +00:00

..

__init__.py

Move parts of action engine tests to a subdirectory

2014-09-04 18:14:11 -07:00

test_builder.py

Add some basic/initial engine statistics

2016-02-01 17:37:49 -08:00

test_compile.py

Using assertIsNone() instead of assertIs(None, ..)

2016-10-10 08:50:21 +00:00

test_creation.py

Instead of a multiprocessing queue use sockets via asyncore

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

test_process_executor.py

Instead of a multiprocessing queue use sockets via asyncore

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

test_scoping.py

Fix order of assertEqual for unit.action_engine

2015-10-17 01:03:22 -07:00