-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request: matchers specifically for streams #134
Comments
From @lrhn on March 4, 2013 13:33 Removed Type-Defect label. |
From @DartBot on March 4, 2013 17:34 This comment was originally written by @seaneagan For starters could make most Iterable Matchers also work for Streams, since the API is so similar: isEmpty |
From @DartBot on March 4, 2013 19:35 This comment was originally written by @seaneagan I think to help with implementing these sorts of Matchers, it would probably be useful if Matcher.matches were allowed to return a Future<bool> instead of just a bool. |
From @DartBot on March 4, 2013 21:5 This comment was originally written by @seaneagan And actually it would probably work better as a rich MatchResult object instead of a plain bool, so it can store data about why it didn't match, to be used in "describe": class Matcher { class MatchResult { |
From @gramster on April 24, 2013 20:21 Regarding the mismatch state, we already have a mechanism for that (MatchState). |
From @DartBot on April 24, 2013 21:10 This comment was originally written by @seaneagan returning Future<bool> from Matcher.matches is filed as issue #10188 |
Added Pkg-Unittest label. |
Removed Area-UnitTest label. |
Removed Pkg-Unittest label. |
From @nex3 on June 4, 2015 23:41 This is still planned, although it'll be in |
Duplicate of #25. |
From @DartBot on March 4, 2013 4:40
This issue was originally filed by @sethladd
I'd love to see some matchers specifically for testing streams. The matchers package has a few matchers for handling Future (like completes).
Copied from original issue: dart-lang/sdk#8899
The text was updated successfully, but these errors were encountered: