targetprocess-mcp-server 2.0.2 → 2.0.4

package/README.md

@@ -60,8 +60,8 @@ Cards — Write
 - `add_test_cases` — Create a test plan and add generated test cases to it in one call (resourceId, testPlanTitle, testCases array of {name, description}, optional resourceType)
 
 Test Case Workflows
-- `write_test_cases` — Fetch a card (UserStory, Bug, or Feature) by ID and trigger the full test case writing workflow: Claude analyzes the card, generates detailed HTML-formatted test cases covering happy path, edge cases, and error scenarios, creates a linked test plan, then calls `add_test_cases_to_test_plan` (resourceId, optional resourceType)
-- `add_test_cases_to_test_plan` — Add an array of pre-generated test cases to an existing test plan by its ID (testPlanId, testCases array of {name, description})
+- `write_test_cases` — Fetch a card (UserStory, Bug, or Feature) by ID and trigger the full test case writing workflow: Claude analyzes the card, generates detailed test cases covering happy path, edge cases, and error scenarios, creates a linked test plan via `create_test_plan`, then calls `add_test_cases_to_test_plan`. Each test case description contains Preconditions and Test Type as HTML; steps are passed as a structured array (resourceId, optional resourceType)
+- `add_test_cases_to_test_plan` — Add pre-generated test cases to an existing test plan. Each test case has a `name`, an HTML `description` (Preconditions and Test Type only), and a `steps` array of `{ description, result }` objects — steps are created via the TP test step API rather than embedded in the description (testPlanId, testCases array of {name, description, steps})
 
 Projects
 - `get_projects` — Get all Targetprocess projects (no params needed)

package/build/index.js

@@ -597,8 +597,8 @@ server.registerTool('create_bug_based_on_card', {
       CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 
         1) IF you already have user story or bug card content, proceed to step 3 skipping step 2;
         2) ELSE call "get_user_story_content" tool or "get_bug_content" tool to get user story or bug card content;
-        3) format the new bug inside html <div> tags with Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior;
-        4) add a comment to the card with bug Id provided in the first step and Title`,
+        3) format the new bug inside html <div> tags with Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior sections (note: section titles should be wrapped in <h3> tags, e.g. <h3>Issue Description</h3>);
+        4) add a comment to the card with created bug Id and its Title`,
     inputSchema: {
         title: z.string()
             .describe('Bug card title that summarizes the problem in concise, descriptive, and actionable manner, enabling a developer to understand the issue without opening the report'),
@@ -652,7 +652,7 @@ server.registerTool('create_bug', {
     description: `Create a new bug card that summarizes the problem in concise, descriptive manner answering questions "What? Where? When?" and content explaining what happened in detail.
       NOTE: this tool does not require a user story or bug card referenced.
       CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps:
-        1) format the new bug inside html <div> tags with Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior;
+        1) format the new bug inside html <div> tags with Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior sections (note: section titles should be wrapped in <h3> tags, e.g. <h3>Issue Description</h3>);
         2) add a comment to the newly created bug with its Id and Title`,
     inputSchema: {
         title: z.string()
@@ -952,15 +952,12 @@ server.registerTool('write_test_cases', {
       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) Format each test case description inside an html <div> element structured as:
-            <div>
-              <p><strong>Preconditions:</strong> ...</p>
-              <p><strong>Test Steps:</strong><ol><li>...</li></ol></p>
-              <p><strong>Expected Result:</strong> ...</p>
-              <p><strong>Test Type:</strong> ...</p>
-            </div>
-        4) Call "create_test_plan" tool passing: resourceId (the card id), resourceType, testPlanTitle (use the card name prefixed with "Test Plan: "), and the testCases array
-        5) Call "add_test_case_to_test_plan" tool passing: testPlanId (the test plan id), and the testCases array`,
+        3) For each test case produce:
+            - name: concise action-oriented title
+            - description: HTML <div> with Preconditions and Test Type sections only (no steps here)
+            - steps: ordered array of { description: "<step action>", result: "<expected result>" }
+        4) Call "create_test_plan" tool passing: resourceId (the card id), resourceType, testPlanTitle (use the card name/title)
+        5) Call "add_test_cases_to_test_plan" tool passing: testPlanId (the test plan id), and the testCases array with name, description, and steps`,
     inputSchema: {
         resourceId: z.string()
             .min(5)
@@ -1018,35 +1015,50 @@ server.registerTool('add_test_cases_to_test_plan', {
         testPlanId: z.string()
             .min(5)
             .max(6)
-            .describe('TP card ID to link the test plan to (e.g. 145789)'),
+            .describe('Test plan ID to add test cases to (e.g. 145789)'),
         testCases: z.array(z.object({
             name: z.string()
                 .describe('Test case title (concise, action-oriented)'),
             description: z.string()
-                .describe('Test case steps and expected results formatted as HTML'),
+                .describe('Test case context formatted as HTML — include Preconditions and Test Type sections, but NOT test steps (those go in the steps field)'),
+            steps: z.array(z.object({
+                description: z.string()
+                    .describe('Step action text'),
+                result: z.string()
+                    .describe('Expected result for this step'),
+            }))
+                .min(1)
+                .describe('Ordered list of test steps with their expected results'),
         }))
             .min(1)
-            .describe('Array of test cases to create in the new test plan'),
+            .describe('Array of test cases to create in the test plan'),
     },
 }, async ({ testPlanId, testCases }) => {
     const created = [];
     const failed = [];
     for (const tc of testCases) {
-        const result = await tp.createTestCase(tc.name, tc.description, String(testPlanId));
-        if (result) {
-            created.push({ id: result.Id, name: result.Name });
-        }
-        else {
+        const testCase = await tp.createTestCase(tc.name, tc.description, String(testPlanId));
+        if (!testCase) {
             failed.push(tc.name);
+            continue;
+        }
+        let stepsAdded = 0;
+        let stepsFailed = 0;
+        for (const step of tc.steps) {
+            const stepResult = await tp.addTestStep(String(testCase.Id), step);
+            if (stepResult) {
+                stepsAdded++;
+            }
+            else {
+                stepsFailed++;
+            }
         }
+        created.push({ id: testCase.Id, name: testCase.Name, stepsAdded, stepsFailed });
     }
     return {
         content: [{
                 type: 'text',
-                text: JSON.stringify({
-                    created,
-                    failed,
-                })
+                text: JSON.stringify({ created, failed })
             }]
     };
 });

package/build/tp.js

@@ -192,7 +192,7 @@ export class TpClient {
     }
     async createTestPlan(title, resourceId, resourceType = 'UserStory', options) {
         const testPlan = {
-            "Name": title,
+            "Name": `Test Plan: ${title}`,
             "Project": {
                 "Id": config.tp.projectId
             },
@@ -242,6 +242,17 @@ export class TpClient {
             param: { "format": "json" },
         }, commentData);
     }
+    async addTestStep(testCaseId, testStep) {
+        const testStepData = {
+            "Description": testStep.description,
+            "Result": testStep.result,
+            "TestCase": { "Id": testCaseId },
+        };
+        return this.post({
+            pathParam: { "testSteps": '' },
+            param: { "format": "json" },
+        }, testStepData);
+    }
     async getBugComments(bugId, results = 25) {
         const response = await this.get({
             pathParam: {

package/package.json

@@ -25,7 +25,7 @@
   "engines": {
     "node": ">=20.x"
   },
-  "version": "2.0.2",
+  "version": "2.0.4",
   "description": "MCP server for Tartget Process",
   "main": "build/index.js",
   "keywords": [