test_rocket 0.10.0

A command line tool to execute your dart tests at lightning fast speed. Experience ~80% reduction in runtime.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

0.10.0 - 2026-10-18

Added

• Rich Test Failure Cards: Structured, easy-to-read failure reporting in testRocket run:
  • De-bundled source locations resolving the exact file path and line number in user test code (e.g. test/features/auth/login_test.dart:42).
  • Cleaned test descriptions stripping the internal bundle prefix (tests <path.dart>).
  • Clear assertion diffs (Expected: vs Actual:) and formatted failure reasons displayed directly in the summary dashboard.
  • Direct, copy-pasteable single-test re-run commands (flutter test <file>).
• testRocket run --failed: Re-run only the test files that failed in the previous run. Failure paths are recorded in .testRocket/failed_tests.json and automatically cleared upon a successful test run.
• Automatic .gitignore Management: Automatically ensures .testRocket/failed_tests.json is added to .gitignore when running testRocket run or testRocket bundle.

Fixed

• Fixed testRocket run unexpectedly collecting and displaying coverage when min_coverage was configured in pubspec.yaml. Coverage is now only evaluated when explicitly requested via --coverage, --min-coverage, or --fail-on-drop.
• Fixed working directory and relative path resolution when invoking bundled test subprocesses in sub-packages or example projects.
• Fixed unawaited shard processes when running with --faster.

0.9.0 - 2026-09-19

Added

• pubspec.yaml Configuration: You can now configure testRocket settings directly in your project's pubspec.yaml:

  test_rocket:
    min_coverage: 80 # Sets the minimum/target coverage percentage (e.g. 80 or 80.0)
  

  • testRocket run --coverage: Automatically enforces this threshold during coverage runs without needing CLI flags, failing with exit code 1 if coverage drops below it (can still be overridden via --min-coverage).
  • testRocket trends: Uses this value to render the target green dashed line in the interactive HTML dashboard.
• testRocket trends command to visualize historical test suite metrics and code coverage trends:
  • Interactive HTML Dashboard (.testRocket/trends.html): Automatically generated and opened in your browser. Features coverage & duration charts, KPI summary cards, time range filters (Last 20, 50, 100, All defaulting to Last 100), author filtering dropdowns to inspect individual or team trends, zoom/pan controls, and a searchable, paginated run history table with latest runs first. Includes --no-open and --no-html flags for CI environments.
  • Terminal Preview: Fast Unicode block chart, sparklines ( ▃▅█), and summary stats for quick checks right in the console.
• Git Rebase & Merge Conflict Resolution: Automated union merge driver (.testRocket/report.csv merge=union) configured via .gitattributes to automatically resolve pull/rebase conflicts across multiple contributors.
• Pre-commit Hook Support: Guide and workflow for automatically running tests and tracking metrics on every commit.
• --min-coverage <percent> flag for testRocket run to enforce a minimum line coverage threshold and fail the build if unreached.
• --fail-on-drop flag for testRocket run to prevent coverage regressions by failing if coverage drops compared to the previous run.
• Experimental | testRocket doctor command to diagnose test isolation issues by bisecting failing test bundles and suggesting fixes for shared state leaks. Writes .testRocket/doctor.md (and .testRocket/doctor.json with --json).

Changed

• Reports are now generated automatically by default. testRocket run logs test metrics to .testRocket/report.csv on every run without needing the --report flag. The --report flag is deprecated.
• Coverage is optional. Running testRocket run logs test counts, durations, and pass/fail statuses. Adding --coverage captures code coverage into the report.
• Sorted test bundle imports. Test bundles now import test files in stable alphabetical order rather than filesystem-walk order, preventing flaky test order differences across machines.

0.3.1 - 2025-04-15

Fixed

• Fixed coverage value being reported incorrectly in the report.csv

0.3.0 - 2025-04-14

Added

• --report flag to run command to generate test run reports in .testRocket directory
• documentation for Test Reporting in Readme.md

0.2.6 - 2025-03-15

Fixed

• update buy me coffee button URL

0.2.5 - 2025-02-28

Fixed

• change the button size of buy me coffee button

0.2.2 - 2025-02-28

Added

• add buy me a coffee button in readme
• add activate command to activate license keys (experimental)
• generate code coverage with --coverage flag on run command (experimental)

0.2.1 - 2024-05-19

Fixed

• fix logs printed during run

0.2.0 - 2024-05-19

Added

• print more readable logs for the run command
• --faster flag now shows experimental warning.

Fixed

• run --faster command now informs when test suite execution completes

0.1.1 - 2024-05-05

Added

• logo for the test_rocket tool

Fixed

• formatting of the readme file

0.1.0 - 2024-05-05

Added

• logo for the test_rocket tool

0.0.12 - 2024-05-05

Fixed

• run command which using dart test instead of flutter test

Changed

• the clause in the test_rocket license

0.0.11 - 2024-05-05

Added

• basic testRocket commands like bundle run
• faster flag for run command to executes tests in parallel

Fixed

• pub analysis issues