commit | db18c53f47bbe6f36b7c763bfede4bc65884b669 | [log] [tgz] |
---|---|---|
author | Nate Bosch <nbosch@google.com> | Mon Oct 14 15:00:36 2019 -0700 |
committer | GitHub <noreply@github.com> | Mon Oct 14 15:00:36 2019 -0700 |
tree | c64d3dfeefa344c426116108210858c9fc956380 | |
parent | 8e5df436fe65f010b2f67b19cd396465159a0f48 [diff] |
Allow private types in pretty print (#116) Closes #115 The default print of `"?"` for private implementation classes can be confusing, especially cases like `[Uri.parse('')]` which pretty prints as `[?:]`. - Add more types to print like "primitives" where they already include the type name in their default `toString`. - Remove handling of `null`, it is handled already in the calling function. - Add handling for some core types that are backed by private implementation classes. - Remove the unnecessary try/catch and outdated comments.
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.