[H203] Use assertIs(Not)None to check for None (off by default) Unit
test assertions tend to give better messages for more specific
assertions. As a result, assertIsNone(...) is preferred over
assertEqual(None, ...) and assertIs(None, ...), and assertIsNotNone(...)
is preferred over assertNotEqual(None, ...) and assertIsNot(None,
...). Off by default.

Trivial fix

Change-Id: I5b6ac7d99f0689843eb98cb3e9b9b10531322640

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

Some classes defines __eq__() built-in function, but does
not define __ne__() built-in function, so self.assertEqual works
but self.assertNotEqual does not work at all in this test case in
python2. This patch fixes it.

Change-Id: I3e4f213081268bad44583a63a84795d39094117f
Closes-Bug: #1586268

Replace assertEqual(None, *) with assertIsNone in tests to have more
clear messages in case of failure.

Change-Id: I74452af6d840bcf612fd3bb2521db9134460dd63
Closes-Bug: #1280522

Change-Id: I7e3451feb94b1f25b00c5e7b197bb6b527548306

A bug was reported where a task's revert method was throwing an
'extra args' exception even though it had a **kwargs to slurp up
any extra args.  I added some tests to duplicate the behavior but
the tests all pass.  I'm hoping pushing this up will cause CI to
reproduce the bug so I can diagnose it further.

Change-Id: I9f4d0f065f11370f7981e93349f473df2bb1015d
Closes-Bug: #1589848

Having to update the endpoint count every time  you add a test
class is really obnoxious and leads to a ton of pointless rebasing.
Now we just check that it finds at least the task it knows about
and call that good.

Change-Id: I96b8c6cd6cbc1fdc58dee4b18cab5699e3daa844