Correct usage of assertEqual for boolean values

Correct usage of assertEqual for boolean values

There are several cases where unit tests are calling
assertEqual([True|False]) instead of the corresponding
assertTrue|assertFalse.

Pretty minor thing, but this patch corrects them to the
more correct calls.

Could add hacking check, but that seems overkill for
something like this.

Change-Id: I1de629ed9e9770157be47f4b1b0ada8388029072