tree 531e2801964b8e443c575321cea4a29cf12e1ad8
parent a24497bc4018a36fc94ae72cb9ad792228476750
author Alphan Ulusoy <alphan@google.com> 1586890058 -0400
committer Garret Kelly <Garret.Kelly@gmail.com> 1587734538 -0400

Use StrictMock in MmioTest

There are three types of mock objects in googlemock: nice, naggy, and
strict. The difference between them is the way they handle
_uninteresting_ mock method calls. Uninteresting calls are calls to mock
methods that don't have any `EXPECT_CALL` specifications. `NiceMock`
silently ignores such calls, `NaggyMock` prints warnings while
`StrictMock` makes all uninteresting calls failures.

A mock object is currently naggy by default, which can potentially hide
some issues in DIF libraries because MMIO accesses without
corresponding `EXPECT_CALL`s do not cause tests to fail. This change
makes the mock object in `MmioTest` a `StrictMock` so that such accesses
will cause tests to fail.

Signed-off-by: Alphan Ulusoy <alphan@google.com>