Write test cases for a TP card (UserStory, Bug, or Feature)
write_test_casesFetches a Targetprocess card by ID, analyzes its details, and generates structured test cases covering happy paths, edge cases, boundaries, and errors for test plan creation.
Instructions
Fetches a TP card (UserStory, Bug, or Feature) content by ID. CRITICAL WORKFLOW — after receiving the card content, you MUST: 1) Thoroughly analyze the card name and description to understand the feature or issue being tested 2) Write detailed test cases covering: happy path, edge cases, boundary conditions, and error scenarios 3) For each test case produce: - name: concise action-oriented title - description: HTML with Preconditions and Test Type sections only (no steps here) - steps: ordered array of { description: "", result: "" } 4) Call "create_test_plan" tool passing: resourceId (the card id), resourceType, testPlanTitle (use the card name/title), NOTE: IF test plan already exists - skip this step and proceed to step 5. 5) Call "add_test_cases_to_test_plan" tool passing: testPlanId (the test plan id), and the testCases array with name, description, and steps
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"resourceId": "<resourceId>"
},
"name": "write_test_cases"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| resourceId | Yes | TP card ID (e.g. 145789) | |
| resourceType | No | Type of the TP card — UserStory, Bug, or Feature (default: UserStory) | UserStory |