- Feb 11, 2015
-
-
Natalie Weizenbaum authored
R=kevmoo@google.com See #2 Review URL: https://codereview.chromium.org//916533003
-
Kevin Moore authored
R=nweiz@google.com Review URL: https://codereview.chromium.org//916653002
-
Kevin Moore authored
R=nweiz@google.com Review URL: https://codereview.chromium.org//917503002
-
- Feb 10, 2015
-
-
Kevin Moore authored
R=nweiz@google.com Review URL: https://codereview.chromium.org//909323002
-
Kevin Moore authored
R=nweiz@google.com Review URL: https://codereview.chromium.org//916523002
-
- Feb 09, 2015
-
-
Kevin Moore authored
Review URL: https://codereview.chromium.org//910943002
-
- Feb 05, 2015
-
-
Natalie Weizenbaum authored
So far these interfaces don't really do anything, so there aren't any tests. Future commits will use these as a foundation. R=kevmoo@google.com See #2 Review URL: https://codereview.chromium.org//877553009
-
- Jan 28, 2015
-
-
Natalie Weizenbaum authored
-
Natalie Weizenbaum authored
This gets rid of all uses of part, adds documentation where it was missing, and fixes a number of style issues. It's a backwards-compatible change designed to make the package more clear and comprehensible in preparation for larger changes to come. R=kevmoo@google.com Review URL: https://codereview.chromium.org//869043002
-
- Jan 27, 2015
-
-
Kevin Moore authored
R=nweiz@google.com Review URL: https://codereview.chromium.org//882843003
-
Kevin Moore authored
R=nweiz@google.com Review URL: https://codereview.chromium.org//873473004
-
Kevin Moore authored
R=nweiz@google.com Review URL: https://codereview.chromium.org//876343003
-
Kevin Moore authored
R=nweiz@google.com Review URL: https://codereview.chromium.org//869053002
-
- Jan 13, 2015
-
-
Kevin Moore authored
also removed unused fields and variables R=nweiz@google.com Review URL: https://codereview.chromium.org//845153003
-
Kevin Moore authored
R=nweiz@google.com Review URL: https://codereview.chromium.org//850603002
-
Kevin Moore authored
also updated codereview url R=nweiz@google.com Review URL: https://codereview.chromium.org//846143003
-
- Dec 19, 2014
-
-
Natalie Weizenbaum authored
-
Natalie Weizenbaum authored
-
- Dec 18, 2014
-
-
Natalie Weizenbaum authored
-
Natalie Weizenbaum authored
-
- Dec 11, 2014
-
-
nweiz@google.com authored
R=rnystrom@google.com Review URL: https://codereview.chromium.org//791213002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@42272 260f80e4-7a28-3924-810f-c04153c831b5
-
- Dec 09, 2014
-
-
nweiz@google.com authored
This avoids a versioning issue where an exported dependency adds a feature and the exporting package's users' version constraints become invalidated. For example, suppose unittest 1.0.0 and matcher 1.0.0 exist. unittest has the constraint "matcher: '>=1.0.0 <2.0.0'" and exports matcher. Then matcher 1.1.0 is released with a new feature, and a user writes a new package, mypkg, which uses that feature. As per common practice, this package has the version constraint "unittest: '>=1.0.0 <2.0.0'" and no constraint on matcher. This constraint allows matcher 1.0.0, which doesn't support the new feature; this is a problem. Under the new scheme, unittest would have the constraint "matcher: '>=1.0.0 <1.1.0'". Then when matcher 1.1.0 is released, unittest 1.1.0 would be released as well with the constraint "marcher: '>=1.1.0 <1.2.0'". The tight lower bound ensures that the constraint "unittest: '>=1.1.0 <2.0.0'" properly selects only versions of matcher that have features available in the version the user is testing against. The tight upper bound ensures that new features in a new version of matcher won't become available in unittest without a version upgrade. R=jmesserly@google.com, rnystrom@google.com Review URL: https://codereview.chromium.org//775413002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@42223 260f80e4-7a28-3924-810f-c04153c831b5
-
- Dec 08, 2014
-
-
kevmoo@google.com authored
TBR Review URL: https://codereview.chromium.org//750543004 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@42195 260f80e4-7a28-3924-810f-c04153c831b5
-
nivco@google.com authored
Instead of Throwing an error when setting the unittest config if it has already been set we'll just display a warning. https://codereview.chromium.org/772463003/ git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@42187 260f80e4-7a28-3924-810f-c04153c831b5
-
- Nov 20, 2014
-
-
wibling@google.com authored
BUG= R=kustermann@google.com, sgjesse@google.com Review URL: https://codereview.chromium.org//740323002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@41850 260f80e4-7a28-3924-810f-c04153c831b5
-
- Nov 18, 2014
-
-
wibling@google.com authored
BUG= R=kustermann@google.com, sgjesse@google.com Review URL: https://codereview.chromium.org//734343002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@41798 260f80e4-7a28-3924-810f-c04153c831b5
-
- Nov 17, 2014
-
-
wibling@google.com authored
BUG= R=kustermann@google.com, sgjesse@google.com Review URL: https://codereview.chromium.org//734023002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@41774 260f80e4-7a28-3924-810f-c04153c831b5
-
- Nov 14, 2014
-
-
wibling@google.com authored
I am creating e2e tests for dart on App Engine and want to avoid redeploying the app each time I need to run a specific set of tests. Instead I have enhanced the unittest library with a method which creates a new "global" test environment which can be used for this specific run of tests. Before I had to redeploy the app each time (takes ~2-4mins) to get a fresh test environment. BUG= R=kevmoo@google.com, kustermann@google.com Review URL: https://codereview.chromium.org//709903004 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@41741 260f80e4-7a28-3924-810f-c04153c831b5
-
- Oct 07, 2014
-
-
srawlins@google.com authored
BUG= https://code.google.com/p/dart/issues/detail?id=21239 R=rnystrom@google.com Review URL: https://codereview.chromium.org//627403002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@40968 260f80e4-7a28-3924-810f-c04153c831b5
-
srawlins@google.com authored
BUG= https://code.google.com/p/dart/issues/detail?id=13105 R=rnystrom@google.com Review URL: https://codereview.chromium.org//638433003 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@40967 260f80e4-7a28-3924-810f-c04153c831b5
-
- Sep 18, 2014
-
-
kevmoo@google.com authored
R=nweiz@google.com Review URL: https://codereview.chromium.org//524153002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@40475 260f80e4-7a28-3924-810f-c04153c831b5
-
- Aug 20, 2014
-
-
dgrove@google.com authored
closure of each test after it runs. R=rnystrom@google.com Review URL: https://codereview.chromium.org//495813002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@39438 260f80e4-7a28-3924-810f-c04153c831b5
-
- Aug 07, 2014
-
-
paulberry@google.com authored
Previously, if a unit test returned a future, then while the unit test framework was awaiting that future, asynchronous failures occurring during callback functions would not abort the test. In addition to fixing the bug, fix a flaw in the _defer() function which prevented async_exception_test from actually testing asynchronous exceptions. BUG= http://dartbug.com/20153 R=kevmoo@google.com Review URL: https://codereview.chromium.org//416133002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@39013 260f80e4-7a28-3924-810f-c04153c831b5
-
- Jul 23, 2014
-
-
kevmoo@google.com authored
Updated homepage url R=rnystrom@google.com Review URL: https://codereview.chromium.org//412483005 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@38485 260f80e4-7a28-3924-810f-c04153c831b5
-
- Jun 09, 2014
-
-
kevmoo@google.com authored
R=sigmund@google.com Review URL: https://codereview.chromium.org//319983005 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@37147 260f80e4-7a28-3924-810f-c04153c831b5
-
- Jun 02, 2014
-
-
nweiz@google.com authored
R=kevmoo@google.com, rnystrom@google.com Review URL: https://codereview.chromium.org//308763003 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@36891 260f80e4-7a28-3924-810f-c04153c831b5
-
- May 12, 2014
-
-
kevmoo@google.com authored
BUG= https://code.google.com/p/dart/issues/detail?id=9780 R=sigmund@google.com Review URL: https://codereview.chromium.org//283573004 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@36047 260f80e4-7a28-3924-810f-c04153c831b5
-
- May 09, 2014
-
-
kevmoo@google.com authored
TBR Review URL: https://codereview.chromium.org//275013002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@35957 260f80e4-7a28-3924-810f-c04153c831b5
-
kevmoo@google.com authored
R=sigmund@google.com Review URL: https://codereview.chromium.org//270943002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@35954 260f80e4-7a28-3924-810f-c04153c831b5
-
- Apr 03, 2014
-
-
sigmund@google.com authored
R=blois@google.com Review URL: https://codereview.chromium.org//224663002 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart/pkg/unittest@34722 260f80e4-7a28-3924-810f-c04153c831b5
-