JAIPilot is an IntelliJ plugin and open-source CLI that automatically generates robust, high-coverage Java unit tests. It understands method logic, handles mocking, and self-corrects errors so you don’t have to write tests manually.
Yes. The open-source jaipilot-cli works with Codex for repo-native Java unit test generation workflows.
JAIPilot is ideal for Java developers who want to avoid repetitive boilerplate test code and achieve high test coverage quickly. It’s especially useful if you want reliable tests without switching context or writing prompts manually.
No, JAIPilot does not store your code or use it for training. Your class data is processed securely from your machine. Logs (if any) are deleted within 30 days. We do not use or retain user data for any model improvement or analytics.
Reach out to us via the JetBrains marketplace page, the open-source jaipilot-cli repository, or email us at support@jaipilot.com. We’re here to help.
Start with either: JetBrains IntelliJ Plugin or jaipilot-cli on GitHub. The CLI is open source and works with Codex.
Use the open-source jaipilot-cli repository for terminal-native workflows. It is designed to work well with Codex when you want JAIPilot inside a repo-driven coding loop.
After installation, sign up for a JAIPilot account. You can top up anytime with usage based credits billing by buying request attempts.
In IntelliJ, right-click any Java class and choose "JAIPilot" -> "Generate Tests". For terminal workflows, use the open-source jaipilot-cli inside your repository. JAIPilot handles context extraction, generation, and verification.
JAIPilot generates standard Java unit tests that can be checked into your repository and run through your existing CI pipeline.
JAIPilot extracts the class under test, identifies dependencies, builds a clean context, generates the JUnit test class, and compiles the result. If errors occur, it fixes and retries until the output is valid.
JAIPilot produces full JUnit test classes, with mock setup using Mockito, and multiple test methods that match your method logic, branches, and edge cases.
JAIPilot detects compilation issues or test failures, captures the error, and automatically retries until the test class is fixed.
JAIPilot collects the source of the class under test, public method signatures, and all nested POJO types used as inputs or return values to give full context before generating tests.