Create test case

Create a test case in the project. It is created in draft and a burn-in run starts automatically.

IMPORTANT: gather context first, or the test will be flaky. This tool records the test exactly as you describe it. It does NOT explore the site to confirm the flow exists, so a vague or unverified goal produces low-value, flaky tests. Before calling, make sure you have:

• Verified the functionality, pages, and UI labels actually exist in the target environment. Do not guess or assume.
• A goal describing a single concrete user flow in plain UI terms, using generic data rather than specific entity names. Specific entities change over time and cause flakiness.
• An expectedResult stating a UI-observable outcome a user can see on screen.
• Prerequisites in place: a login/auth dependency via resumeFromDependencyProjectTestCaseId when the flow needs authentication, plus the right configShortIds.
• Checked existing tests with list_test_cases to avoid duplicates.

If you have not gathered this context, prefer create_chat instead. The QA.tech chat agent crawls the site, grounds the test in what actually exists, sets up login and config dependencies, and verifies the test runs. That is how reliable tests get created. Use this tool directly only when you already know the flow exists and have the details above.

POST /v1/test-cases

Create test case

cURL

curl --request POST \
  --url https://api.qa.tech/v1/test-cases \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "<string>",
  "goal": "<string>",
  "applicationShortId": "<string>",
  "expectedResult": "<string>",
  "resumeFromDependencyProjectTestCaseId": "<string>",
  "waitForDependenciesProjectTestCaseIds": [
    "<string>"
  ],
  "configShortIds": [
    "<string>"
  ],
  "scenarioShortId": "<string>",
  "projectShortId": "<string>"
}
'

200

{
  "success": true,
  "testCase": {
    "id": "<string>",
    "name": "<string>",
    "url": "<string>"
  }
}

Body

application/json

Request body for creating a new test case linked to a project

name · string · required

goal · string · required

Minimum string length: 1

applicationShortId · string · required

Pattern: ^app(-.+_.+|_.+)$

expectedResult · string

resumeFromDependencyProjectTestCaseId · string

waitForDependenciesProjectTestCaseIds · string[]

configShortIds · string[]

Pattern: ^cfg(-.+_.+|_.+)$

scenarioShortId · string

Pattern: ^scenario(-.+_.+|_.+)$

projectShortId · string

Target a specific project by its prefixed short ID (proj-slug_shortId or proj_shortId), as returned by the projects API. Required for organization-scoped API keys; project-scoped keys may only pass their own project's short ID.

Pattern: ^proj(-.+_.+|_.+)$

Response

200 - application/json

The request has succeeded.

success · boolean · required

testCase · object · required

Show child attributes