neutron/neutron/tests/unit/tests
Viktor Varga c4d65601ed Replaced assertTrue(False) with fail()
In some unit and functional tests self.assertTrue(False) was used
instead of self.fail(), which might be against readability.

Using assertTrue(False) gives the following message on fail:

  File "C:\Python361\lib\unittest\case.py", line 678, in assertTrue
    raise self.failureException(msg)
    AssertionError: False is not true

After replacing assertTrue(False) with fail():

  File "C:\Python361\lib\unittest\case.py", line 666, in fail
    raise self.failureException(msg)
    AssertionError: None

Although the results are the same (both tests failed), the
message 'False is not true' is unnecessary, and can be omitted
from the log by using fail().

Change-Id: I81e21040fd6a2f9713889912fafd2b19bd056b5a
2017-06-22 19:31:00 +02:00
..
common Mock call to sysctl for test_get_free_namespace_port 2016-08-31 14:53:55 -05:00
example Remove recursion from import_modules_recursively 2016-09-30 21:48:50 +00:00
__init__.py Reorganize unit test tree 2015-04-06 23:28:31 +00:00
test_base.py Remove deprecated eventlet TimeoutError exception 2017-05-05 16:49:58 +07:00
test_post_mortem_debug.py Replaced assertTrue(False) with fail() 2017-06-22 19:31:00 +02:00