You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 7, 2018. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: