Skip to content

Releases: dart-lang/test

0.12.24+4

12 Sep 22:10
Compare
Choose a tag to compare
  • Drain browser process stdout and stdin. This resolves test flakiness, especially in Travis
    with the Precise image.

0.12.24+3

11 Sep 21:02
Compare
Choose a tag to compare
  • Extend deserializeTimeout.

0.12.24+2

04 Aug 17:45
Compare
Choose a tag to compare
  • Only force exit if FORCE_TEST_EXIT is set in the environment.

0.12.23+1

26 Jun 17:28
Compare
Choose a tag to compare
  • Remove unused imports.

0.12.23

23 Jun 17:35
Compare
Choose a tag to compare
  • Add a fold_stack_frames field for dart_test.yaml. This will
    allow users to customize which packages' frames are folded.

0.12.22+2

23 Jun 16:03
Compare
Choose a tag to compare
  • Properly allocate ports when debugging Chrome and Dartium in an IPv6-only
    environment.

0.12.22

13 Jun 00:22
Compare
Choose a tag to compare
  • Add a retry option to test() and group() functions, as well
    as @Retry() annotation for test files and a retry
    configuration field for dart_test.yaml. A test with reties
    enabled will be re-run if it fails for a reason other than a
    TestFailure.

  • Add a --no-retry runner flag that disables retries of failing tests.

  • Fix a "concurrent modification during iteration" error when calling
    addTearDown() from within a tear down.

0.12.21

05 Jun 19:34
Compare
Choose a tag to compare
  • Add a doesNotComplete matcher that asserts that a Future never completes.

  • throwsA() and all related matchers will now match functions that return
    Futures that emit exceptions.

  • Respect onPlatform for groups.

  • Only print browser load errors once per browser.

  • Gracefully time out when attempting to deserialize a test suite.

0.12.20+13

05 May 20:44
Compare
Choose a tag to compare
  • Upgrade to package:matcher 0.12.1

0.12.20+12

04 May 17:38
Compare
Choose a tag to compare
  • Now support v0.30.0 of pkg/analyzer

  • The test executable now does a "hard exit" when complete to ensure lingering isolates or async code don't block completion. This may affect users trying to use the Dart service protocol or observatory.