FAQ

Is Tiden only a test management system?

No. Test management is one part of Tiden. The product also manages requirements, branches, agent-driven automation, runtime issues, releases, environments, traceability, and quality gates.

What is the difference between a workspace and a product?

A workspace groups products and workspace-level credentials. A product is the quality repository for one application or service.

Why does Tiden have branches?

Branches let you review proposed changes before they become product truth. They are especially useful for AI-generated requirements and tests.

Can agents write directly to main?

No. Agents should produce generated branches. A human reviews and merges those branches.

Are API tokens the same as DSN keys?

No. API tokens call the public REST API. DSN keys only send error events to a product ingest endpoint.

Where do I create an API token?

Open profile settings and create an API token. The token is shown once. Store it in a secret manager or let tiden setup write it to ~/.tiden/config.json.

Why do source map uploads need an API token?

Source maps contain source code and are uploaded from CI. The upload API uses a real API token, while runtime events use only a DSN key.

What release value should I use?

Use one stable string across CI, telemetry SDK initialization, source map upload, and tiden release create. For example: my-app@1.2.3.

What if a release appears in staging and production?

Create separate release records by version plus environment. The same version can exist in multiple environments.

Can I call every web API endpoint with an API token?

No. API tokens are intentionally limited to the public API package. Web-only admin endpoints require a browser session.

What should I document in requirement sources?

Attach source links or file locations that explain why the requirement exists: customer notes, specs, repository files, agent artifacts, or design documents.