| commit | 71eeaee1cb8235a47e47bcad9134f744bb1c594a | [log] [tgz] |
|---|---|---|
| author | Nate Bosch <nbosch@google.com> | Tue Dec 29 13:53:55 2020 -0800 |
| committer | GitHub <noreply@github.com> | Tue Dec 29 13:53:55 2020 -0800 |
| tree | 02076b8dfec0955b69256dc33de9fd501235f1ac | |
| parent | 2071cfd84b3ede7277c57d122ef8c74cf0f3c6f0 [diff] |
Make the item argument to Match dynamic again (#163) This argument had been implicitly dynamic. #162 made it `Object?` which can cause analysis errors that are otherwise hidden due to implicit casts. Any classes which implement `Matcher` and override `match` could omit the argument type, which mean to inherit from the parent. When that became `Object?` the cast to some other type which could have been implicit coming from `dynamic` must now be explicit.
Support for specifying test expectations, such as for unit tests.
The matcher library provides a third-generation assertion mechanism, drawing inspiration from Hamcrest.
For more information, see Unit Testing with Dart.