In the documentation of the tests the usage of fixture.expectEventsMatching() is very detailed. This can lead to excessive usage of matchers instead of the simpler fixture.expectEvents().
In many cases fixture.expectEvents() would be simpler and is sutable. But the ID-Field often is not known in the test (or not of interest) and this leads to the usage of the matcher version. So a short documentation of fixture.expectEvents() in combination with registerIgnoredField() would help to choose the right expect method.
In the documentation of the tests the usage of
fixture.expectEventsMatching()is very detailed. This can lead to excessive usage of matchers instead of the simplerfixture.expectEvents().In many cases
fixture.expectEvents()would be simpler and is sutable. But the ID-Field often is not known in the test (or not of interest) and this leads to the usage of the matcher version. So a short documentation offixture.expectEvents()in combination withregisterIgnoredField()would help to choose the right expect method.