JAIPilot/ Docs
Run Java testing workflows in IntelliJ IDEA
Install the plugin, sign in, and choose the testing outcome you need from the Jobs tool window.
Install JAIPilot ↗Prefer the terminal? Install CLI or view the GitHub repository ↗. The CLI uses the same JAIPilot account and credits. For coverage targets, follow the CLI and Maven guide to check JaCoCo locally or generate tests to meet your configured minimum.
Install and connect
Follow these steps in IntelliJ IDEA. JAIPilot handles the testing workflow; project commands and file changes run on your computer.
- 01
Install JAIPilot
Settings → Plugins → MarketplaceSearch for JAIPilot and install the plugin in IntelliJ IDEA.
- 02
Sign in to JAIPilot
Settings → JAIPilotChoose Sign in to JAIPilot to start the trial. No provider CLI, model picker, or separate AI account is required.
- 03
Run a job
Right-click a class, classes, or a directory · Jobs → NewRight-click a class, multiple classes, or a directory to scope the workflow to that selection. Use Jobs → New in the JAIPilot console to run against the entire repository.
- 04
Inspect the result
JAIPilot tool window → JobsRead the build, tests, coverage, and changed files. Git projects also support change review, undo, and redo.
Watch a job
Right-click a class, multiple classes, or a directory to run against that selection, or use Jobs → New in the JAIPilot console to run against the entire repository. Then follow local execution, measured results, change review, and the generated JUnit test.
Workflow reference
Choose a job by what you have now and the result you need.
Generate Tests
Java file or project
New tests, build result, and test totals
Lock Existing Behavior
Java file before a refactor
Characterization tests for current behavior
Fix Tests
Failing project tests
Repairs and a fresh test run
Stabilize Flaky Tests
Intermittently failing tests
Reproduction, fix, and repeated runs
Test Current Changes
Current Git changes
Targeted tests and full-suite result
Improve Coverage
Java file with a coverage report
Measured coverage before and after
Coverage appears only when the project creates a supported report. JAIPilot does not infer a percentage from console text or file names.
Results and history
Jobs keeps commands, checks, and the changed-file list together. Git repositories can open a diff and use Undo or Redo. Non-Git projects can still run jobs and see how to initialize Git for those actions.
Analysis records test totals and measured coverage by repository and branch when a job produces them. A successful job may make no code changes.
Open Analysis →Install JAIPilot
Open the plugin listing in JetBrains Marketplace.