Runs the .http files you author in GoLand as CI tests — no JDK to install and no JVM to babysit. Verified conformant against JetBrains' own ijhttp.
Why httpsuite?
You already author .http files in GoLand or IntelliJ. They live next to the code they test, they are reviewed in the same pull request, and they work. The problem starts at the pipeline: running them in CI has meant provisioning a JDK and keeping a JVM patched, purely to execute a handful of HTTP requests.
httpsuite runs the same files as a single static binary. No JDK to install, no runtime to keep patched, no daemon. It runs wherever your CI already runs — macOS, Windows, and any Linux, down to Alpine/musl, distroless, and FROM scratch images.
What it does
It executes your requests and their pre-request and response-handler JavaScript, evaluates client.test and declarative # @expect checks, propagates variables across requests, and reports pass/fail for a terminal or for CI.
JetBrains-compatible scripting
Pre-request < {% %} and response > {% %} handlers, client.test, client.global, the response DOM and jsonPath — executed by the pure-Go goja engine (ES2015+). Your existing JetBrains environment files work unchanged.
Verified against ijhttp
A conformance harness runs the same .http files through both httpsuite and JetBrains' own CLI, then diffs their JUnit reports test by test. On the shared API surface, they agree — which is a claim you can check rather than take on trust.
Declarative assertions
If you would rather not write JavaScript, attach # @expect comments instead. Status, headers, JSON body paths, types, dates and duration are all covered, with no scripting required.
Learn More
For full documentation, installation options and the conformance results, visit httpsuite.dev.