Fix Android build breakage with new extension tests

Fix Android build breakage with new extension tests

The tests use EXPECT_EQ with a constant variable equal to false,
that tricks GCC 4.7+ into beliving the variable should be compatible to null
pointers in some internal macro. This CL workarounds that by
using EXPECT_TRUE(a == b) instead.

BUG=https://code.google.com/p/googletest/issues/detail?id=458
TBR=mek
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=271136

[trchen, 2014-05-16 23:43:40]

The CQ bit was checked by trchen@chromium.org

[commit-bot: I haz the power, 2014-05-16 23:45:24]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/trchen@chromium.org/290723002/1

[commit-bot: I haz the power, 2014-05-17 01:14:23]

Change committed as 271136