Affected

A JetBrains IDE plugin that finds affected projects and runs only their tests and build checks.

Install · Support matrix · Releases · Roadmap · Report a problem

Built for multi-module projects and monorepos across 28 supported build ecosystems and 11 JetBrains products. See the support matrix for languages, test runners, selection units and evidence.

A change in one package no longer starts checks for every unrelated package.

What you get

• Less waiting. Run checks for affected parts of the repository.
• One action. Cover supported ecosystems together.
• One Run session per affected plan. Build-system roots keep their own structured sections inside it.
• Smaller test runs. Narrow to the smallest unit whose relationship can be proven by the native build system or test runner.
• Consumer checks. Optionally compile direct dependents after a public API change, or run the tests of every module that depends on a changed one.
• Commit and push checks. Optionally run the plan before a commit or push, including the tests of modules that depend on the change.
• Says what happened. A short summary after each run, and Affected > Diagnose explains what was detected and why nothing ran.
• Regression or already failing. After a failed check, Check on base branch reruns only the failed Gradle, Maven, Go and Cargo task groups in a private checkout of the comparison base and tells whether your change broke them.
• One settings page. Settings | Tools | Affected holds the base branch and every switch; the toolbar menu keeps the same toggles.
• Local by design. No account, server, telemetry or project-specific config file.
• Optional MCP tools. The same analysis snapshot and run actions when the JetBrains MCP Server plugin is installed. Affected > Set up for coding agents opens the MCP Server settings to connect your agent and adds ready-made instructions to AGENTS.md so the agent verifies its own edits.

Get started

1. Install Affected.
2. Open a supported project and make a change.
3. Choose Run affected tests or press Ctrl+Alt+Shift+T.

The first successful compatible run may test a full module once while Affected learns its exact test relationships.

How it works · Privacy · Security · Code of Conduct · Contributing · Changelog · MIT License