There are now a collection of actions that change how seriously HMock takes certain classes of errors:
setAmbiguityCheck :: MonadIO m => Severity -> MockT m ()
setUninterestingActionCheck :: MonadIO m => Severity -> MockT m ()
setUnexpectedActionCheck :: MonadIO m => Severity -> MockT m ()
setUnmetExpectationCheck :: MonadIO m => Severity -> MockT m ()
The behavior of these should be explained clearly in a section of the README file. In particular, the distinction between "unexpected" and "uninteresting" is a common pitfall in gMock where I took the idea from, and it should be articulated. (See http://google.github.io/googletest/gmock_cook_book.html#uninteresting-vs-unexpected for gMock's explanation.)
There are now a collection of actions that change how seriously HMock takes certain classes of errors:
setAmbiguityCheck :: MonadIO m => Severity -> MockT m ()setUninterestingActionCheck :: MonadIO m => Severity -> MockT m ()setUnexpectedActionCheck :: MonadIO m => Severity -> MockT m ()setUnmetExpectationCheck :: MonadIO m => Severity -> MockT m ()The behavior of these should be explained clearly in a section of the README file. In particular, the distinction between "unexpected" and "uninteresting" is a common pitfall in gMock where I took the idea from, and it should be articulated. (See http://google.github.io/googletest/gmock_cook_book.html#uninteresting-vs-unexpected for gMock's explanation.)