TestKase

Overview

The TestKase card files bugs into TestKase's own defect tracker — the same DEF-n defects you create by hand in a Test Management project. It works like any external tool: connect with a TestKase personal access token, pick the project, and Report a bug creates a defect there.

Before you start

• A Test Management project with Defects turned on — the project's Settings → Defect integration must have a configured option (Built-in, or any other). Projects without it don't appear in the list.
• A personal access token for the user the defects should be created by.

Get a TestKase access token

1. Click your avatar → Settings → API Keys (or open /api-keys).
2. Click Generate, name it (for example Defect filing), and copy the token. It's shown once.

See API keys for expiry and revocation.

Connect it in TestKase

1. Open Organization → Integrations → Defects and click Connect on the TestKase card (it's the first one).
2. Paste the access token and click Connect.
3. Choose the project the defects should be created in. Only projects in the token owner's organization that have Defects set up are listed.
4. Click Save.

What gets created

A defect DEF-n in that project, created by the token's owner, with the report's title and the pre-filled details as its summary. The screenshot is added to the defect's Attachments tab and counts against the organization's storage like any upload. The dialog links straight to the new defect.

Troubleshooting

▶"No destinations" after connecting

No project has Defects set up.

Fix: Open a project → Settings → Defect integration and configure one.

▶"That TestKase access token is not valid any more"

The token was revoked or expired.

Fix: Generate a new one and ⋮ → Reset, then reconnect.

▶Filed, but the screenshot could not be attached

The organization's storage is full.

Fix: Free space under Organization → Storage; the defect itself was created.