Difference between EasyMock.createStrictMock(class<T> x) and EasyMock.createNiceMock(class<T> x)
easymock, java
Solution
If you tell a mock to expect a call to `foo()`, then to expect a call to `bar()`, and the actual calls are `bar()` then `foo()`, a strict mock will complain but a nice mock won't. That's what order checking means.
Problem
In the API doc it is mentioned that in the strictmock order checking is enabled by default while in case of nice mock it is not . I did not get what exactly they meant by "order checking".