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: Automatically enforces this threshold during test 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.

Fixed #

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

Added #

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

Fixed #

• update buy me coffee button URL

Fixed #

• change the button size of buy me coffee button

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)

Fixed #

• fix logs printed during run

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

Added #

• logo for the test_rocket tool

Fixed #

• formatting of the readme file

Added #

• logo for the test_rocket tool

Fixed #

• run command which using dart test instead of flutter test

Changed #

• the clause in the test_rocket license

Added #

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

Fixed #

• pub analysis issues