Aqua is a dedicated test automation IDE from JetBrains, built exclusively for QA engineers, software developers in test, and anyone whose primary craft is writing, running, and debugging automated test suites at scale. Unlike a general-purpose IDE with testing plugins grafted on as an afterthought, Aqua ships with the entire testing toolchain already integrated — framework detection, intelligent runners, a built-in HTTP client, and browser inspection tools — so the testing workflow is first-class from the moment you open a project.
What is Aqua?
Aqua is JetBrains' purpose-built IDE for test automation, sitting alongside IntelliJ IDEA, WebStorm, and PyCharm in the JetBrains family but laser-focused on the QA engineering discipline rather than general application development.
It runs on the same battle-hardened IntelliJ platform that underpins the rest of the JetBrains lineup, which means the core editing experience — keyboard shortcuts, project indexing, VCS integration — is immediately familiar to anyone who has spent time in Rider or GoLand. The meaningful difference is the opinionated default setup: every panel, run configuration, and smart inspection is oriented around test code from day one. There is no scavenger hunt through a plugin marketplace before you can start writing meaningful assertions.
What does Aqua do best?
Aqua excels at giving test authors an intelligent, polyglot environment that genuinely understands the structure and intent of automated tests — not just the syntax of the language they happen to be written in.
The IDE detects your testing framework — Selenium, Playwright, Cypress, pytest, JUnit, TestNG, and others — directly from project dependencies and configures itself accordingly. You get contextual completions for CSS and XPath locators, smart navigation between page objects and the tests that consume them, and inline failure diagnostics that point straight at the assertion that broke rather than making you parse a wall of stack trace. The built-in HTTP client lets you probe REST and GraphQL endpoints without leaving the IDE, which is enormously practical when building API test layers. I particularly value the live test results panel: it updates as each individual test finishes rather than dumping everything at the end of the run, which changes how quickly you can start triaging a failing suite. Mobile teams are covered too, via first-class Appium support for iOS and Android automation.
How much does Aqua cost?
Aqua is free for personal and non-commercial use — a genuinely generous policy for open-source contributors, students learning test automation, or sole practitioners evaluating the tool before proposing it to a team.
Commercial use requires a paid JetBrains subscription, which follows the same annual, per-seat model as the rest of the JetBrains catalogue. Teams holding an All Products Pack licence get Aqua included. A trial period is available before any commitment, and the free tier does not cripple core features, which keeps the evaluation process honest.
Who should use Aqua?
Aqua is built for SDETs and QA engineers who write automated tests for a living — not developers who test occasionally and want a lightweight plugin on top of their existing setup.
If automated test suites make up the majority of your daily code output, Aqua's opinionated environment pays back the learning investment quickly. The polyglot support — Java, Kotlin, Python, JavaScript, TypeScript, Groovy, and Ruby — means it handles most real-world test technology stacks without forcing you to jump between IDEs across projects. It is considerably less compelling if tests are peripheral to your work; in that case, your existing IntelliJ IDEA or WebStorm installation already covers you adequately.
What are the best Aqua alternatives?
The closest daily-driver alternatives are VS Code with a curated extension stack, IntelliJ IDEA for Java and Kotlin-heavy shops, and WebStorm for JavaScript and TypeScript teams.
VS Code is free and endlessly flexible, but that flexibility has a cost: you will spend real hours assembling the right combination of Playwright Test Runner, REST Client, Selenium tooling, and language-specific test extensions, then maintaining that configuration across every developer's machine. IntelliJ IDEA and WebStorm provide solid test support within their language families and remain the better choice when test code and production code live together in one large codebase. Eclipse with testing plugins is a fourth option, though it feels noticeably older in day-to-day use by comparison. Aqua wins the argument when your test codebase is large, polyglot, and important enough to deserve its own specialised tool rather than a patchwork of plugins.
