Viktor Varga 2cb74b1b84 Replaced assertTrue(False, msg) with fail(msg) ...

In some unit tests instead of self.fail(msg) statements
self.assertTrue(False, msg) were used, which might be ambiguous.

Using assertTrue(False, msg) 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 : msg

'False is not true' message implies that unit test failed (as the
result is False while we asserted True).

Replaced with self.fail(msg) is less ambiguous and more readable.

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

TrivialFix

Change-Id: Ib56a0ed8549fd7af2724eb59222106888781e9c8

2017-06-21 12:16:33 +02:00

..

functional

Open-code eventlet.listen()

2017-05-11 01:39:14 -06:00

probe

Merge "Cleanup db replicator probetest"

2017-06-12 21:13:15 +00:00

unit

Replaced assertTrue(False, msg) with fail(msg)

2017-06-21 12:16:33 +02:00

__init__.py

Open-code eventlet.listen()

2017-05-11 01:39:14 -06:00

sample.conf

[Trivial]Fix some type errors in ../sample.conf

2017-02-12 01:30:34 -08:00