FAQ

#What is Kensa, in one sentence?

A desktop IDE for QA test cases that stores them as plain Markdown files in your git repository, with a built-in terminal for running your own AI coding agents against them.

#Is it a cloud service?

No. Kensa is a local desktop app. There is no Kensa server, no account, and no cloud sync. It works fully offline and never sends your data anywhere.

#Where are my test cases stored?

As .md files inside a project folder you choose. Suites are folders; each case is one Markdown file with YAML frontmatter. You put the folder under git like any code repo. See data-format.md.

#Do I need an AI subscription to use Kensa?

No. The AI features work by giving you a terminal where you run a CLI agent you already have (Claude Code, Codex, Aider, …). Kensa never asks for an API key and doesn't bundle a model. You can use Kensa as a pure file-based TMS with no AI at all.

#Which AI agents are supported?

Any CLI agent runs in the terminal. Kensa has first-class one-click plugin setup for Claude Code and Codex, which teaches the agent the Kensa case format, conventions, and CLI. See ai-integration.md.

#Can I read and edit cases without Kensa?

Yes - they're plain Markdown. Any editor, script, grep, or AI agent can work with them. Kensa is a nicer way to do it, not a requirement.

#How do I migrate from TestRail / Qase / Allure?

Use the import wizard: pick the source, upload the export (CSV/JSON) or connect to the REST API, preview, and import. You can also export back out to the same formats. See features/import.md and features/export.md.

#Does it work on Windows / macOS / Linux?

Yes - all three. Windows 10/11, macOS 12+ (Intel and Apple Silicon), and Linux (Ubuntu 22.04+/Fedora 38+, best-effort).

#How do test cases get reviewed by my team?

Through git. Because cases are files, changes show up in pull requests with normal diffs - your team reviews test cases the same way they review code.

#Can two people edit the same project?

You collaborate through git (branches, PRs, merges), not real-time co-editing. Case IDs are allocated to avoid collisions, and Kensa reconciles the ID counter against what's actually on disk.

#Is there a command-line tool?

Yes - kensa, a 30-command CLI that ships with the app and is also installable standalone. It's built for both humans and AI agents. See cli.md.

#Can I customize the fields on a test case?

Yes. The case structure is a versioned schema you edit in a split-screen designer - add custom fields, retype or reorder system fields, set defaults and constraints, and preview the impact live before applying. Migrations are non-destructive and back affected cases up to trash first. See features/schema-and-fields.md.

#What happens when I delete a case?

It moves to .tms/trash/ and can be restored. The only hard delete is an explicit "empty trash".

#Does it auto-update?

Yes, by default (built on Tauri's updater). You can opt out in settings.

#What does "Kensa" mean?

検査 - Japanese for inspection / testing / quality check. Pronounced "ken-sa".