Skip to content

chore(deps): update dependency test to ^1.33.0 - #2951

Draft
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/test
Draft

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/test

Conversation

@renovate

@renovate renovate Bot commented May 12, 2025 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
test (source) dev_dependencies minor ^1.25.15 → ^1.33.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

dart-lang/test (test)

v1.33.0

Compare Source

  • Replace the Safari launch mechanism to use safaridriver.
  • Fix a hang when the runner is interrupted at the moment a test suite starts
    loading.
  • Fix a LiveTest.run() may not be called for a closed test error when the
    runner is interrupted at the moment a test suite is about to start loading.
  • Create all temporary directories used by the test runner, including browser
    profiles and compiler output, under a single dart_test. directory which is
    deleted when the run finishes.
  • Delete the temporary directory when the test runner is interrupted with
    Control-C twice.
  • Bundle skipped tests into a single group at the end of the GitHub reporter
    output instead of interrupting passing test groups.
  • Delete the kernel file compiled for a test suite once that suite has finished
    running, and delete the snapshot or bundle compiled with the exe and cli
    compilers once the test process has exited, instead of retaining every
    compiled artifact until the end of the run.
  • Fail to load a test suite compiled with the exe or cli compiler if the
    test process exits before connecting to the runner, instead of hanging.
  • Wait longer for Chrome to open the test page when running with --debug or
    --coverage, and list the open tabs if the page is never found.
  • Fail a test suite running in an isolate if the isolate exits, instead of
    hanging. The suite fails to load if the isolate exits while loading, and any
    tests that haven't finished fail if it exits while they run.
  • Include Chrome's stderr, which has its logging, in the browser output when
    running with --debug or --coverage. Previously it was missing from the
    error when Chrome failed or a suite timed out while loading.
  • Let Chrome choose its own remote debugging port when running with --debug
    or --coverage, instead of picking a port that another process could take
    before Chrome binds it.
  • Add flag --shard-by-suite to control sharding strategy.

v1.32.0

Compare Source

  • Precompiled browser tests: stop serving files from outside the precompiled
    root directory. The static handler no longer sets serveFilesOutsidePath,
    restoring path-containment parity with the dart2js and dart2wasm compilers.
  • Export TestFailure from package:test/scaffolding.dart.
  • Support --compiler cli with the vm-asan, vm-msan, and vm-tsan
    runtimes.
  • Add support for DART_TEST_REPORTER environment variable in test runner and
    when tests are run directly on platforms which support dart:io. The
    environment variable takes precedence over configuration in dart_test.yaml
    but is overridden by the --reporter flag when passed to the test runner.
  • Suppress dart2js compiler output for successful compiles.
  • Include output from passing tests messages within the Passing tests group
    in GithubReporter.
  • Only include VM debugger in output when using interactive debugging, suppress
    it when only using coverage.
  • Use a redirect html file for browser tests to avoid leaking websocket details
    through process starting arguments.
  • Migrate out of process VM tests communication channel from TCP sockets to Unix
    domain sockets inside a restricted temporary directory.
  • Pass Node.js test process connection configuration and secret token via a
    restricted temporary authentication file to prevent secret leakage in command
    line process arguments.
  • Enable asserts in the exe compiler.
  • Keep the CHROME_EXECUTABLE, MS_EDGE_EXECUTABLE, FIREFOX_EXECUTABLE, and
    SAFARI_EXECUTABLE overrides working when the browser is also configured
    through override_platforms or define_platforms. Any setting on those
    platforms used to drop the variable.
  • Fix race conditions in Chrome coverage collection where tests could finish
    before DevTools connection and coverage profiling were initialized.
  • Fix deadlock that may occur running tests with the exe compiler.

v1.31.2

Compare Source

  • Add support for running tests as native CLI bundles (vm platform only).
    • You can run tests this way with --compiler cli.
  • Impacts Configuration Support using the OS platform selector to configure
    browser tests.
    Previously tests loaded for the browser would have an operating system of
    "none", now they will have an operating system matching the system the browser
    is running on. This allows more specific configuration, such as skipping a
    particular browser test on a particular platform. This may impact existing
    configuration which relied on the configuration for browser tests being
    independent from any OS specific configuration. For instance a wide skip of
    all tests with OS 'windows' would previously still run browser tests on
    windows, but will now skip all tests including browser tests.
  • Use a DevTools URL instead of a defunct observatory URL.
  • Disable throttling in chrome launch arguments.
  • Allow package_config 3.x.x.
  • Require analyzer: '>=13.0.0 <15.0.0'
  • Use the compact or failures-only reporters by default for tests run directly
    instead of through the test runner.

v1.31.1

Compare Source

  • Ignore an error locating the SDK directory on platforms where the
    resolvedExecutable is unexpectedly null.
  • Fix a bug where -c exe tests would hang on exit on windows.
  • Fix a bug where the web test runner would not find custom HTML files when
    using the dart2wasm compiler.
  • GithubReporter:
    • Group contiguous passing and skipped tests into collapsible groups to
      reduce log noise in GitHub Actions.
    • Updated skipped icon to ⏭️.
  • Increase SDK constraint to ^3.10.0.
  • Allow analyzer version 13.x.x.

v1.31.0

Compare Source

  • Print a summary of failed tests at the end of the expanded reporter output.
  • Add vm-asan, vm-msan, and vm-tsan runtimes to run tests on the standalone
    Dart VM under Address Sanitizer, Memory Sanitizer or Thread Sanitizer. This is
    useful for finding issues when using foreign libraries through dart:ffi, such
    as use-after-free, use of initialized memory and data races, or for detecting
    data races in Dart code using shared fields.
  • Change return type on the body callback argument to group to void from
    dynamic. This may surface cases where the group callback was erroneously
    returning an ignored value.
  • Fix a hang when a test run with --compiler exe crashes.
  • Require analyzer: '>=8.0.0 <13.0.0'

v1.30.0

Compare Source

  • Add a --suite-load-timeout argument to allow configuring a timeout for
    compiling and loading individual test suites.
  • Remove the default 12 minute timeout to compile and load test suites.
  • Bump test_core to 0.6.16
  • Add comments to the top-level libraries in the package.
  • Bump test_api to 0.7.10 to fix missing locations on tests skipped due to
    the use of solo.

v1.29.0

Compare Source

  • Add --coverage-package flag, which filters the coverage report to specific
    packages using RegExps.
  • Require a function definition named main directly in a test suite and
    provide a more direct error message than a failing compiler output.
  • Suppress skip reason messages in the compact and failures-only reporters.
  • Allow analyzer major version 10.

v1.28.0

Compare Source

  • Add isSorted and related matchers for iterables.
  • Consider NaN to be equal to itself in equals.
  • Bump test_core to 0.6.14
  • Removed unused js dependency

v1.27.0

Compare Source

  • Add --coverage-path and --branch-coverage options to dart test.
  • Serve dart2wasm source map files.
  • Fix Node.js dart2wasm tests on windows.
  • Doc edit: clarify in README that a platform selector includes the compiler.
  • Allow analyzer major version 9.
  • Require Dart 3.7

v1.26.3

Compare Source

  • Expand pub constraint to allow the latest analyzer.

v1.26.2

Compare Source

  • Graduate native assets from experiment to preview.

v1.26.1

Compare Source

  • Set a debug name for test isolates.
  • Fix an assertion failure when using setUpAll or tearDownAll and running
    with asserts enabled.

v1.26.0

Compare Source

  • test() and group() functions now take an optional TestLocation that will
    be used as the location of the test in JSON reporters instead of being parsed
    from the call stack.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/test branch from 2a40098 to 9bbbbf5 Compare May 19, 2025 18:31
@provokateurin
provokateurin marked this pull request as draft May 19, 2025 18:36
@renovate
renovate Bot force-pushed the renovate/test branch from 9bbbbf5 to 18a2dea Compare May 21, 2025 14:28
@renovate
renovate Bot force-pushed the renovate/test branch from 18a2dea to c426ef6 Compare June 22, 2025 18:19
@renovate
renovate Bot force-pushed the renovate/test branch 2 times, most recently from d8ebdc7 to 20aaf68 Compare July 22, 2025 03:24
@renovate
renovate Bot force-pushed the renovate/test branch 2 times, most recently from 39dd282 to 1d7eb95 Compare November 21, 2025 04:23
@renovate
renovate Bot force-pushed the renovate/test branch 3 times, most recently from 655b2bf to b804f6d Compare March 24, 2026 13:32
@renovate
renovate Bot force-pushed the renovate/test branch from b804f6d to a89fdd8 Compare April 8, 2026 15:05
@renovate renovate Bot changed the title chore(deps): update test chore(deps): update dependency test to ^1.31.0 Apr 8, 2026
@renovate
renovate Bot force-pushed the renovate/test branch from a89fdd8 to c889c16 Compare April 8, 2026 17:19
@renovate
renovate Bot force-pushed the renovate/test branch from c889c16 to 409f239 Compare April 28, 2026 00:39
@renovate renovate Bot changed the title chore(deps): update dependency test to ^1.31.0 chore(deps): update dependency test to ^1.31.1 Apr 28, 2026
@renovate
renovate Bot force-pushed the renovate/test branch from 409f239 to 542556c Compare May 21, 2026 08:01
@renovate renovate Bot changed the title chore(deps): update dependency test to ^1.31.1 chore(deps): update test to ^1.31.1 Jun 2, 2026
@renovate renovate Bot changed the title chore(deps): update test to ^1.31.1 chore(deps): update test Jun 22, 2026
@renovate
renovate Bot force-pushed the renovate/test branch from 542556c to 38b97f4 Compare June 25, 2026 13:04
@renovate renovate Bot changed the title chore(deps): update test chore(deps): update dependency test to ^1.31.1 Jun 25, 2026
@renovate
renovate Bot force-pushed the renovate/test branch from 38b97f4 to f4b561d Compare June 27, 2026 04:27
@renovate renovate Bot changed the title chore(deps): update dependency test to ^1.31.1 chore(deps): update dependency test to ^1.31.2 Jun 27, 2026
@renovate renovate Bot changed the title chore(deps): update dependency test to ^1.31.2 chore(deps): update dependency test to ^1.32.0 Sep 3, 2026
@renovate renovate Bot changed the title chore(deps): update dependency test to ^1.32.0 chore(deps): update dependency test to ^1.33.0 Oct 8, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants