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
Matchers should be stricter by default. Unit Tests should make assertions about the exact values a Signal will contain, as non-determinism is not a desirable trait of tests. This may be relevant to async matchers, but synchronous matching is based on the actual Signal having completed before the matcher even returns success or failure.
Closing as I can't see this being that important right now.
In matchers for next values we can fail early
For example with
haveIdenticalValues()
for two signals:1, 2, 3, 4, 5
1, 2, 5, 4, 5
we can fail when the events are known to be non-identical, i.e at index 2 of the values
The text was updated successfully, but these errors were encountered: