unittest package has been renamed
test. It will export
API through the
0.12.x branch, but it is deprecated and
test should be used
If a future matched against the
completion() matcher throws
an error, that error is printed directly rather than being wrapped in a
string. This allows such errors to be captured using the Zone API and improves
Improve support for Polymer tests. This fixes a flaky time-out error and adds
In order to be more extensible, all exception handling within tests now uses the Zone API.
Add a heartbeat to reset a test's timeout whenever the test interacts with the test infrastructure.
expectAsyncUntil() throw more useful errors
if called outside a test body.
can be disabled with the new
Improve the browser test suite timeout logic to avoid timeouts when running many browser suites at once.
--verbose-traceflag to include core library frames in stack traces.
0.12.0 adds support for a test runner, which can be run via
pub run test in Dart 1.10). By default it runs all files
recursively in the
test/ directory that end in
_test.dart and aren't in a
The test runner supports running tests on the Dart VM and many different
browsers. Test files can use the
@TestOn annotation to declare which platforms
they support. For more information on this and many more new features, see the
As part of moving to a runner-based model, most test configuration is moving out
of the test file and into the runner. As such, many ancillary APIs have been
removed. These APIs include
all its subclasses,
getOrCreateExpectFailureHandler which used to be exported from the
package have also been removed. They existed to enable integration between
matcher that has been streamlined.
A number of APIs from
matcher have been into
Throws, and all of the
throws methods. Some of these have changed slightly:
expect no longer has a named
expect added an optional
id renamed to
reasonnamed argument to
expectAsyncUntil, which has the same definition as
guardAsync- no longer needed
protectAsync2- no longer needed
mirror_matchers.darthave been removed. They are now in the
mock.darthas been removed. It is now in the
mirror_matchers.dartare now in the
mock.dartis now in the
equalsnow allows a nested matcher as an expected list element or map value when doing deep matching.
expectAsyncUntilnow support up to 6 positional arguments and correctly handle functions with optional positional arguments with default values.
Zone. This ensures that any exceptions that occur is async operations are reported back to the source test case.
Zoneaddresses the need for these methods.
expectAsyncreplaces the now deprecated
expectAsyncUntilreplaces the now deprecated
enabledis now get-only
interactive_html_config.darthas been removed.
solo_groupnow throw a
StateErrorif called while tests are running.
rerunTestshas been removed.
Add this to your package's pubspec.yaml file:
dependencies: unittest: "^0.12.4+1"
You can install packages from the command line:
$ pub get
Alternatively, your editor might support
Check the docs for your editor to learn more.
Now in your Dart code, you can use:
|0.12.4+1||Dec 14, 2015|
|0.12.4||Aug 11, 2015|
|0.12.3||Jun 3, 2015|
|0.12.2||May 22, 2015|
|0.12.0||Apr 30, 2015|
|0.11.7||Jan 9, 2017|
|0.11.6+4||Apr 11, 2016|
|0.11.6+3||Mar 28, 2016|
|0.11.6+2||Mar 24, 2016|
|0.11.6+1||May 21, 2015|
We analyzed this package, and provided a score, details, and suggestions below.
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
Detected platforms: unsure
Error(s) prevent platform classification.
Fix dependencies in
pub upgradefailed with the following output:
ERR: Package test has no versions that match >=0.12.4 <0.12.5 derived from: - unittest depends on version >=0.12.4 <0.12.5
Fix platform conflicts.
Make sure none of the libraries use mutually exclusive dependendencies.
Fix issues reported by
dartanalyzerreported 1 error(s) and 0 warning(s).
The description is too short.
Add more detail about the package, what it does and what is its target use case. Try to write at least 60 characters.
Package is pre-v1 release.
While there is nothing inherently wrong with versions of
0.*.*, it usually means that the author is still experimenting with the general direction API.
Maintain an example.
Create a short demo in the
example/directory to show how to use this package. Common file name patterns include:
example.dartor you could also use