Skip to main content

Quickstart

This quickstart gets a new team from an empty account to a product that can accept requirements, tests, branches, and telemetry.

1. Create or join an organization

  1. Open https://app.tiden.ai.
  2. Sign up or log in.
  3. Create an organization, or accept an invite from an existing organization.
  4. Create a workspace if your organization does not have one yet.

2. Create a product

  1. Open a workspace.
  2. Select New product.
  3. Enter a product name and optional description.
  4. Choose or accept the generated product code.

The product code is used in display IDs for requirements and tests.

3. Install and authorize the CLI

Install tiden:

curl -fsSL https://tiden.ai/install.sh | bash

On macOS with Homebrew:

brew install --cask qase-tms/tap/tiden

On Windows PowerShell:

irm https://tiden.ai/install.ps1 | iex

Authorize the CLI:

tiden setup

The setup command opens a browser approval flow, stores an API token in ~/.tiden/config.json, lets you select a workspace, and can bind your current repository to a product.

Validate the setup:

tiden config verify
tiden workspace list --format text

4. Add first requirements

You can create requirements in the web UI or with the CLI:

tiden requirement create \
--product-id <product-id> \
--title "User can reset a password" \
--content "The user receives a reset link and can set a new password."

For longer Markdown, use a file:

tiden requirement create \
--product-id <product-id> \
--title "Checkout supports card payments" \
--content-file ./requirements/checkout.md

Create a test case:

tiden test create \
--product-id <product-id> \
--kind case \
--title "Reset password with a valid link" \
--priority High \
--type Functional

Link the test to a requirement:

tiden test link-requirement <test-id> --requirement-id <requirement-id>

6. Review traceability

Open the product and select Traceability. Requirements are grouped by component and show whether each requirement is verified, not run, or missing test coverage.

7. Connect error tracking

  1. Open Issues in the product.
  2. Select setup.
  3. Create or copy a DSN.
  4. Install the SDK for your runtime.
  5. Send a test exception.

Start with Connect error tracking.

8. Prepare a release and quality gate

Create a release from CI or the CLI:

tiden release create \
--product-id <product-id> \
--version my-app@1.2.3 \
--environment production

Then check the gate:

tiden gate check --product-id <product-id> --release <release-id>