改KaizenReports
Sign inGet started

Create a project

A project in Kaizen is the home for one repo / one app. All test runs, cases, plans, defects, and dashboards live under a project.

The wizard

From the empty workspace dashboard, click Create project. The four-step wizard walks through:

1. Basics

  • Name — human-readable (e.g. Acme Web)
  • Slug — URL-safe, used by the CLI (--project acme-web)
  • Description — optional one-liner
  • Color & icon — for the project picker

2. Stack

Tell Kaizen what your test stack looks like so we can preconfigure the right adapters and dashboard tiles:

  • Languages — JS, Python, Java, Ruby, .NET, Go (multi-select)
  • Runners — Playwright, Pytest, JUnit, RSpec, etc.
  • CI provider — GitHub Actions, GitLab CI, CircleCI, Buildkite, Jenkins, Azure Pipelines, Bitbucket

This step is purely advisory — you can ingest from anywhere later.

3. Access mode

  • open — anyone in the workspace can read
  • team — read scoped to a chosen team
  • project — explicit per-user invites only

You can change this anytime in Settings → Access.

4. First upload

The wizard ends with three options for getting test data in:

  • Drag a kensho-results/ folder into the browser drop zone
  • Copy the kensho push snippet for your CLI / CI
  • Skip for now — start empty and upload later

After the wizard finishes you land on the project dashboard. It will be empty until your first run lands.

Project dashboard tabs

Once data starts flowing, you'll see the standard tabs:

| Tab | What it shows | |---|---| | Dashboard | High-level metrics — pass rate over time, top failing suites, mean run duration, flake count | | Test Cases | Every case ever seen across runs, filterable by suite/owner/severity/labels | | Runs | Every uploaded run (closed + open). Click in for the embedded Kensho viewer | | Test Plans | Manual + automated plan bundles | | Live Runs | Streaming pipeline output from CI | | Defects | Linked bugs grouped by case | | Flaky | Cases above your flake threshold | | Migration | Manual tests waiting to be matched against automation | | Settings | Members, access mode, integrations, tokens |

Project tokens

To upload from CI without kensho login, mint a project token under Settings → Tokens. Pass it via --token or KENSHO_TOKEN env var:

KENSHO_TOKEN=krt_xxx npx kensho push --workspace acme --project acme-web

Tokens are scoped to one project and one capability (ingest only by default).

Next: upload your first run

See Upload runs for the three supported paths.