Install jikken with Homebrew, Nix

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• jk

Project history

The project describes its origin as a tool built to validate complex data APIs used by analytics dashboards while fitting into source control and CI/CD workflows. Its first public release, v0.1.0, shipped at the end of 2022 with basic YAML/JSON test definitions, request execution, response comparisons, tags, variables, extraction, dependencies, and iteration support.

Through 2023 and 2024, Jikken evolved from a simple runner into a broader API-testing toolkit. The changelog shows the move to command-oriented usage with `jk run` and `jk dryrun`, support for staged tests and setup/cleanup, a user-path configuration file, JUnit output, OpenAPI-based test generation, a VSCode extension, secrets, body schemas, generated test data, and formatting and validation commands.

Adoption history

Jikken's distribution history is tied to Rust and cross-platform package channels. The project publishes to crates.io and documents installation through Cargo, Homebrew/Linuxbrew, Chocolatey, prebuilt GitHub release binaries, and source builds, which made it practical for mixed macOS, Linux, and Windows teams to add the same API-test runner to developer machines and CI agents.

How it is used

Jikken is used by writing `.jkt` files that define requests and validations, then running `jk run`, `jk dryrun`, `jk list`, `jk format`, or `jk validate`. The documented examples emphasize status-code checks, multi-stage flows, token extraction from one response into later requests, body comparison between API versions, ignored response fields, tag filtering, and recursive discovery.

Why package nerds care

For package collectors, Jikken is a small example of the post-Postman CLI testing niche: API tests stored as plain files, versioned with application code, runnable without a GUI, and packaged through Rust's cargo ecosystem as well as desktop package managers. Its history also shows a common modern path for CLI tools: start with a narrow runner, then add OpenAPI generation, JUnit output, editor support, secrets, and platform binaries as automation use grows.

Timeline

• 2022: v0.1.0 introduced the Jikken CLI, YAML/JSON test definitions, variables, comparisons, tags, and ordered test dependencies.
• 2023: v0.4.0 moved execution into explicit commands such as `jk run` and `jk dryrun`; v0.5.0 added optional telemetry and user-path configuration.
• 2024: v0.7.0 added JUnit output, OpenAPI test generation, `jk list`, and a VSCode extension for JKT files.
• 2024: v0.8.0 added secrets, body schemas, generated data for fuzz-style validation, `jk format`, and `jk validate`.
• 2026: v0.8.4 added numeric array indexing for variable extraction from root-level JSON arrays.

Related projects

• Jikken sits near GUI API clients and test tools such as Postman, Insomnia, Newman, HTTPie, and curl, but its package-manager identity is closer to Rust CLI tools that expect plain files, CI execution, and reproducible installation. Its OpenAPI generation connects it to schema-first API workflows.

Sources

• https://api.github.com/repos/jikkenio/jikken/releases?per_page=100
• https://crates.io/api/v1/crates/jikken
• https://crates.io/crates/jikken
• https://github.com/jikkenio/jikken
• https://jikken.io/docs/
• https://raw.githubusercontent.com/jikkenio/jikken/main/CHANGELOG.md