| commit | af4fe7daf8e94a46981e4f072872be550a6969e9 | [log] [tgz] |
|---|---|---|
| author | Nate Bosch <nbosch1@gmail.com> | Wed Mar 11 10:14:56 2020 -0700 |
| committer | GitHub <noreply@github.com> | Wed Mar 11 10:14:56 2020 -0700 |
| tree | 4edf3ec57b0abba5d5b4227b5a49123ac9d459eb | |
| parent | 4b01524f59f3f9f89284f994c44340d41da4d9ab [diff] |
Deprecate the mirror matchers library (#131) I cannot find usage. Asserting that an object has a property with a known name can be accomplished by casting to `dynamic` and attempting to read from that property. Asserting that an object has a property with a name that is unknown at compile time has no known use case, if it comes up it would re rare enough that the code for using mirrors to solve it can be put into the test.
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.