Changelog

We’ve consolidated the Smarter Testing CLI experience under the CircleCI CLI. Please apply these changes by September 14, 2026.

Installation

The testsuite is now managed as a CircleCI CLI extension. Remove the standalone tap and install via the CLI:

$ brew uninstall circleci/tap/circleci-testsuite
$ circleci extension install testsuite

Install the CLI here: https://cli.circleci.com/

Command changes

testsuite is now a top-level command with dedicated subcommands:

• circleci run testsuite → circleci testsuite run
• circleci testsuite "ci tests" → circleci testsuite run "ci tests"
• circleci testsuite "ci tests" --doctor → circleci testsuite doctor "ci tests"
• circleci testsuite "ci tests" --lists-tests-only → circleci testsuite list-tests "ci tests"

Flag changes

Test impact analysis flags have been renamed for consistency:

• --test-selection / --select-tests → --run-tests
• --test-analysis → --analyze-tests

Plugins now on public registries

Smarter Testing plugins have moved to a monorepo (circleci-public/smarter-testing-plugins) and are published to their respective package registries:

• npm: @circleci/jest-circleci-coverage, @circleci/cypress-circleci-coverage, @circleci/mocha-circleci-coverage, @circleci/vitest-circleci-coverage, @circleci/v8-coverage-collector
• PyPI: pytest-circleci-coverage
• RubyGems: rspec-circleci-coverage

We will be removing the upstream_concurrency_map and upstream_job_ids fields from the v1 API. This change will take effect starting April 13th.

If you have integrations that consume v1 API responses, please ensure they do not depend on the upstream_concurrency_map or upstream_job_ids fields. No other fields in the v1 API are affected. The v2 API is unaffected by this change.

If you have any questions or concerns, please reach out to CircleCI Support.