- Feb 19, 2015
-
-
Natalie Weizenbaum authored
This preserves the shape of the previous API, but stubs out the functionality. This is a temporary measure designed to make it easier for users to try the runner out on their existing tests. R=kevmoo@google.com Closes #2 Review URL: https://codereview.chromium.org//934413002
-
Natalie Weizenbaum authored
This ensures that console_reporter_test isn't run on browsers, and improves the path detection for test/io.dart. R=kevmoo@google.com Review URL: https://codereview.chromium.org//944553002
-
Natalie Weizenbaum authored
This is still extremely bare-bones and won't work with tests that actually import "package:unittest/unittest.dart", but it's something. R=kevmoo@google.com See #2 Review URL: https://codereview.chromium.org//933083002
-
- Feb 18, 2015
-
-
Natalie Weizenbaum authored
R=kevmoo@google.com Review URL: https://codereview.chromium.org//936693002
-
- Feb 17, 2015
-
-
Kevin Moore authored
R=nweiz@google.com Review URL: https://codereview.chromium.org//926063003
-
- Feb 13, 2015
-
-
Natalie Weizenbaum authored
Remove the "build/" prefix from a bunch of status lines, add a missing import to test/io.dart, and use SkipByDesign everywhere. R=kevmoo@google.com Review URL: https://codereview.chromium.org//923803002
-
- Feb 12, 2015
-
-
Natalie Weizenbaum authored
Run tests from test/ rather than build/test so that their assumptions about paths hold true, fix a typo in the vm_listener_test line, and mark prints_matcher_test failing on Safari. R=kevmoo@google.com TBR See #4 Review URL: https://codereview.chromium.org//917353003
-
Natalie Weizenbaum authored
This fixes tests that don't require dart:io and marks those that do dart:io as Skip. R=kevmoo@google.com Review URL: https://codereview.chromium.org//918853005
-
Natalie Weizenbaum authored
R=kevmoo@google.com See #2 Review URL: https://codereview.chromium.org//920703006
-
Natalie Weizenbaum authored
This also adds LiveTest.close, which releases resources associated with a LiveTest. R=kevmoo@google.com See #2 Review URL: https://codereview.chromium.org//914963003
-
- Feb 11, 2015
-
-
Natalie Weizenbaum authored
No tests yet; since this uses stdout, I'm planning to wait until we have a runner executable and test that. R=kevmoo@google.com See #2 Review URL: https://codereview.chromium.org//913123006
-
Natalie Weizenbaum authored
R=kevmoo@google.com See #2 Review URL: https://codereview.chromium.org//891493004
-
Natalie Weizenbaum authored
These provide the core test-declaration API. R=kevmoo@google.com See #2 Review URL: https://codereview.chromium.org//917783003
-
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
-