@smartbear/mcp 0.11.0 → 0.12.1

package/dist/qmetry/client/tools/testsuite-tools.js

@@ -1,5 +1,5 @@
 import { QMetryToolsHandlers } from "../../config/constants.js";
-import { CreateTestSuiteArgsSchema, ExecutionsByTestSuiteArgsSchema, LinkPlatformsToTestSuiteArgsSchema, LinkTestCasesToTestSuiteArgsSchema, RequirementsLinkedTestCasesToTestSuiteArgsSchema, TestCaseRunsByTestSuiteRunArgsSchema, TestCasesByTestSuiteArgsSchema, TestSuiteListArgsSchema, TestSuitesForTestCaseArgsSchema, UpdateTestSuiteArgsSchema, } from "../../types/common.js";
+import { BulkUpdateExecutionStatusArgsSchema, CreateTestSuiteArgsSchema, ExecutionsByTestSuiteArgsSchema, LinkPlatformsToTestSuiteArgsSchema, LinkTestCasesToTestSuiteArgsSchema, RequirementsLinkedTestCasesToTestSuiteArgsSchema, TestCaseRunsByTestSuiteRunArgsSchema, TestCasesByTestSuiteArgsSchema, TestSuiteListArgsSchema, TestSuitesForTestCaseArgsSchema, UpdateTestSuiteArgsSchema, } from "../../types/common.js";
 export const TESTSUITE_TOOLS = [
     {
         title: "Create Test Suite",
@@ -167,17 +167,17 @@ export const TESTSUITE_TOOLS = [
             },
             {
                 description: "Get test suites with manual viewId (skip auto-resolution)",
-                parameters: { projectKey: "MAC", viewId: 103097, folderPath: "" },
-                expectedOutput: "Test suites using manually specified viewId 103097",
+                parameters: { projectKey: "MAC", viewId: 103097, folderPath: "" }, // This is an example viewId, must be resolved per project TS viewId
+                expectedOutput: "Test suites using manually specified viewId 103097", // This is an example viewId, must be resolved per project TS viewId
             },
             {
                 description: "List test suites from specific project (ex: project key can be anything (VT, UT, PROJ1, TEST9)",
                 parameters: {
                     projectKey: "use specific given project key",
-                    viewId: "fetch specific project given projectKey Test Suite ViewId",
+                    viewId: "fetch specific project given projectKey Test Suite ViewId", // auto-resolved
                     folderPath: "",
                 },
-                expectedOutput: "Test suites using manually specified viewId 103097 or projectKey",
+                expectedOutput: "Test suites using manually specified viewId 103097 or projectKey", // This is an example viewId, must be resolved per project TS viewId
             },
             {
                 description: "Get test suites by release/cycle filter",
@@ -274,7 +274,7 @@ export const TESTSUITE_TOOLS = [
             },
             {
                 description: "Get test suites with custom pagination and auto-resolved viewId",
-                parameters: { tsFolderID: 113557, page: 1, limit: 20 },
+                parameters: { tsFolderID: 113557, page: 1, limit: 25 },
                 expectedOutput: "Paginated list of test suites with 20 items per page",
             },
             {
@@ -316,7 +316,7 @@ export const TESTSUITE_TOOLS = [
             },
             {
                 description: "Search test suites from specific sub-folder with manual viewId",
-                parameters: { tsFolderID: 42, viewId: 104316 },
+                parameters: { tsFolderID: 42, viewId: 104316 }, // This is an example viewId, must be resolved per project TS viewId
                 expectedOutput: "Test suites available in specific folder ID 42 for test case linking",
             },
         ],
@@ -331,7 +331,7 @@ export const TESTSUITE_TOOLS = [
             "VIEWID AUTO-RESOLUTION:",
             "1. System automatically fetches project info using the projectKey",
             "2. Extracts latestViews.TSFS.viewId automatically",
-            "3. Example: latestViews.TSFS.viewId = 104316 (MAC project TSFS view)",
+            "3. Example: latestViews.TSFS.viewId = 104316 (MAC project TSFS view)", // This is an example viewId, must be resolved per project TSFS viewId
             "4. Manual viewId only needed if you want to override the automatic resolution",
             "WORKFLOW: System automatically handles project info if tsFolderID or viewId is not provided",
             "PROJECT INFO STRUCTURE: clientData.rootFolders.TS.id contains the root test suite folder ID",
@@ -544,7 +544,7 @@ export const TESTSUITE_TOOLS = [
             },
             {
                 description: "Get linked test cases with custom pagination",
-                parameters: { tsID: 1497291, getLinked: true, page: 1, limit: 50 },
+                parameters: { tsID: 1497291, getLinked: true, page: 1, limit: 25 },
                 expectedOutput: "Paginated list of linked test cases with 50 items per page",
             },
             {
@@ -624,7 +624,7 @@ export const TESTSUITE_TOOLS = [
                 parameters: {
                     tsID: 194955,
                     tsFolderID: 126554,
-                    viewId: 41799,
+                    viewId: 41799, // This is an example viewId, must be resolved per project TEL viewId
                 },
                 expectedOutput: "Executions filtered by test suite folder and specific view configuration",
             },
@@ -664,6 +664,20 @@ export const TESTSUITE_TOOLS = [
             },
         ],
         hints: [
+            "!MOST IMPORTANT HOW TO GET viewId:",
+            "CRITICAL: Always resolve and use the correct test execution viewId for the current project when calling this tool.",
+            "The viewId parameter must be fetched from the active project's info (latestViews.TEL.viewId).",
+            "Each QMetry project may have a different test execution list viewId, so using a stale or incorrect viewId will result in incomplete or invalid executions list data by test suite id.",
+            "Usage workflow:",
+            "1. Fetch project info for the current project (Admin/Get info Service).",
+            "2. Extract latestViews.TEL.viewId from the response.",
+            "3. Use this viewId in the Fetch Test Case Runs by Test Suite Run API call.",
+            "Example:",
+            "   {",
+            "     tsID: 1533730,",
+            "     viewId: 94194,", // This is an example viewId, must be resolved per project TEL viewId
+            "     gridName: 'TESTEXECUTIONLIST'",
+            "   }",
             "CRITICAL: tsID parameter is REQUIRED - this is the Test Suite numeric ID",
             "HOW TO GET tsID:",
             "1. Call API 'Testsuite/Fetch Testsuite' to get available test suites",
@@ -716,14 +730,14 @@ export const TESTSUITE_TOOLS = [
         examples: [
             {
                 description: "Get all test case runs for test suite run ID '107021'",
-                parameters: { tsrunID: "107021", viewId: 6887 },
+                parameters: { tsrunID: "107021", viewId: 6887 }, // This is an example viewId, must be resolved per project TE viewId
                 expectedOutput: "List of test case runs with execution details, status, and metadata",
             },
             {
                 description: "Get test case runs with linked defects",
                 parameters: {
                     tsrunID: "107021",
-                    viewId: 6887,
+                    viewId: 6887, // This is an example viewId, must be resolved per project TE viewId
                     page: 1,
                     limit: 25,
                 },
@@ -733,32 +747,106 @@ export const TESTSUITE_TOOLS = [
                 description: "Get test case runs for test suite run ID '2362144'",
                 parameters: {
                     tsrunID: "2362144",
-                    viewId: 104123,
+                    viewId: 104123, // This is an example viewId, must be resolved per project TE viewId
                     start: 0,
                     page: 1,
-                    limit: 10,
+                    limit: 25,
                 },
                 expectedOutput: "Test case runs from the specified test suite run execution",
             },
         ],
         hints: [
+            "CRITICAL WORKFLOW FOR FETCHING ALL EXECUTIONS OF A TEST SUITE:",
+            "When user asks to:",
+            "  - 'fetch all executions'",
+            "  - 'get all test runs'",
+            "  - 'fetch all tcRunIDs for test suite X'",
+            "  - 'update status for all executions of test suite X'",
+            "STEP 1: First call FETCH_EXECUTIONS_BY_TESTSUITE tool with the test suite ID (tsID, not entityKey)",
+            "  - This returns ALL execution records for that test suite (could be 3, 5, 9, or any number)",
+            "  - Extract ALL tsRunID values from the response data array",
+            "  - Example response: data: [{tsRunID: '2739237', ...}, {tsRunID: '2739236', ...}, {tsRunID: '2739235', ...}]",
+            "STEP 2: For EACH tsRunID from Step 1, call this tool (FETCH_TEST_CASE_RUNS_BY_TESTSUITE_RUN)",
+            "  - This returns all test case runs (tcRunID values) for that specific execution",
+            "  - Repeat for ALL tsRunID values discovered in Step 1",
+            "STEP 3: Collect all tcRunID values from all executions",
+            "  - Now you have the complete list of test case runs across ALL executions",
+            "  - Use these for bulk status updates or other operations",
+            "CRITICAL ERROR TO AVOID:",
+            "- NEVER assume or hard-code only 2-3 execution IDs",
+            "- NEVER skip Step 1 - always discover ALL executions first",
+            "- NEVER fetch tcRunIDs for only some executions - get ALL of them",
+            "- If there are 9 executions, you must fetch tcRunIDs for all 9, not just 2",
+            "EXAMPLE WORKFLOW:",
+            "User: 'Fetch all test case runs for test suite VKMCP-TS-21'",
+            "Step 1: Call FETCH_EXECUTIONS_BY_TESTSUITE with tsID (resolved from VKMCP-TS-21)",
+            "  Result: Found 9 executions with tsRunIDs: 2739237, 2739236, 2739235, 2739234, 2739233, 2739232, 2739231, 2739230, 2739229",
+            "Step 2: Call this tool 9 times (once for each tsRunID)",
+            "  Call 1: tsrunID='2739237' -> returns 54 tcRunIDs",
+            "  Call 2: tsrunID='2739236' -> returns 54 tcRunIDs",
+            "  ... (repeat for all 9)",
+            "Step 3: Total collected: 9 executions × 54 test cases = 486 total tcRunIDs",
+            "",
+            "PERFORMANCE CONSIDERATIONS FOR LARGE TEST RUNS:",
+            "When dealing with large numbers of test case runs (500+, 1000+), follow these guidelines:",
+            "1. ALWAYS inform the user about the scale BEFORE starting operations:",
+            "   Example: 'Found 9 executions with approximately 486 test case runs. This will require fetching data from all 9 executions and may take a moment.'",
+            "2. For bulk status updates on 1000+ test case runs:",
+            "   - NEVER attempt to update all 1000+ in a single operation",
+            "   - Break into smaller batches of 10-20 test case runs per update",
+            "   - Inform user: 'Found 1000 test case runs. Will process in batches of 20 to ensure reliability and performance.'",
+            "   - Show progress: 'Processing batch 1/50 (20 test runs)...', 'Batch 2/50...'",
+            "3. Recommended batch sizes:",
+            "   - For status updates: 10-20 test case runs per batch",
+            "   - For fetching data: Can handle larger batches (50-100)",
+            "   - Adjust based on API response times and timeout limits",
+            "4. Always provide progress updates for long-running operations:",
+            "   - Before: 'Processing 1000 test runs in 50 batches of 20...'",
+            "   - During: 'Completed 200/1000 test runs (10 batches)...'",
+            "   - After: 'Successfully updated all 1000 test case runs.'",
+            "5. Error handling for batch operations:",
+            "   - If a batch fails, report which batch and continue with remaining",
+            "   - Provide summary at the end: 'Completed 48/50 batches. 2 batches failed (batch 23, 45).'",
+            "   - Allow user to retry failed batches specifically",
+            "EXAMPLE LARGE-SCALE WORKFLOW:",
+            "User: 'Update status to Failed for all test runs in VKMCP-TS-21'",
+            "Step 1: Discover all executions (9 found)",
+            "Step 2: Fetch all tcRunIDs (486 total)",
+            "Step 3: Inform user: 'Found 486 test case runs across 9 executions. Will update in 25 batches of 20 runs each.'",
+            "Step 4: Process in batches with progress updates",
+            "Step 5: Report completion: 'Successfully updated all 486 test case runs to Failed status.'",
+            "",
             "CRITICAL: tsrunID and viewId parameters are REQUIRED",
             "tsrunID is a STRING identifier for the test suite run execution",
             "viewId is a NUMERIC identifier for the test execution view",
-            "HOW TO GET tsrunID:",
-            "1. Call API 'Execution/Fetch Executions' to get available executions",
-            "2. From the response, get value of following attribute -> data[<index>].tsRunID",
-            "3. Example: Test Suite Run might have ID '107021'",
-            "HOW TO GET viewId:",
-            "1. Call API 'Admin/Get info Service' to get project info",
-            "2. From the response, get value of following attribute -> latestViews.TE.viewId",
-            "3. Example: Test Execution view might have ID 6887",
+            "!MOST IMPORTANT HOW TO GET tsrunID:",
+            "1. Call API 'Execution/Fetch Executions' (FETCH_EXECUTIONS_BY_TESTSUITE) to get ALL available executions",
+            "2. From the response, get value of following attribute -> data[<index>].tsRunID for EVERY execution",
+            "3. Example: Test Suite might have multiple executions with IDs '107021', '107022', '107023', etc.",
+            "4. NEVER assume there are only 2-3 executions - always fetch to discover the actual count",
+            "!MOST IMPORTANT HOW TO GET viewId:",
+            "CRITICAL: Always resolve and use the correct test execution viewId for the current project when calling this tool.",
+            "The viewId parameter must be fetched from the active project's info (latestViews.TE.viewId).",
+            "Each QMetry project may have a different test execution viewId, so using a stale or incorrect viewId will result in incomplete or invalid test case run data.",
+            "Usage workflow:",
+            "1. Fetch project info for the current project (Admin/Get info Service).",
+            "2. Extract latestViews.TE.viewId from the response.",
+            "3. Use this viewId in the Fetch Test Case Runs by Test Suite Run API call.",
+            "Example:",
+            "   {",
+            '     tsrunID: "2362144",',
+            "     viewId: 104123,", // This is an example viewId, must be resolved per project TE viewId
+            "     start: 0,",
+            "     page: 1,",
+            "     limit: 25",
+            "   }",
+            "This ensures the tool fetches the proper execution runs data for the selected project context.",
             "SIMPLIFIED PAYLOAD: API only accepts essential parameters",
             "SUPPORTED PARAMETERS: start, page, limit, tsrunID, viewId",
             "REMOVED PARAMETERS: filter, sort, showTcWithDefects, udfFilter (cause API errors)",
             "PAGINATION: Use start, page, and limit for result pagination",
             "API REQUIREMENT: Must use exact payload structure that works in Postman",
-            'PAYLOAD FORMAT: {"start": 0, "page": 1, "limit": 10, "tsrunID": "2362144", "viewId": 104123}',
+            'PAYLOAD FORMAT: {"start": 0, "page": 1, "limit": 10, "tsrunID": "2362144", "viewId": 104123}', // Example payload, must use resolved viewId per project TE viewId
             "Use pagination for large result sets (start, page, limit parameters)",
             "This tool is essential for detailed test execution analysis and reporting",
             "Critical for monitoring individual test case execution performance",
@@ -769,4 +857,230 @@ export const TESTSUITE_TOOLS = [
         readOnly: true,
         idempotent: true,
     },
+    {
+        title: "Bulk Update Test Case Execution Status",
+        summary: "Update execution status for individual or multiple test case runs in bulk",
+        handler: QMetryToolsHandlers.BULK_UPDATE_EXECUTION_STATUS,
+        inputSchema: BulkUpdateExecutionStatusArgsSchema,
+        purpose: "Update the execution status (Pass, Fail, Blocked, Not Run, WIP, etc.) for one or more test case runs. " +
+            "This tool enables both single and bulk status updates for test executions, providing flexibility for " +
+            "manual test execution management, automated test result updates, and test execution tracking. " +
+            "Essential for maintaining accurate test execution records and execution status reporting.",
+        useCases: [
+            "Update single test case run status to Pass, Fail, Blocked, or Not Run",
+            "Bulk update multiple test case run statuses in a single operation",
+            "Mark all selected test case runs as Not Run for re-execution",
+            "Update execution status after manual test execution",
+            "Set execution status based on automated test results",
+            "Update test execution status across different test environments",
+            "Track test execution progress and completion",
+            "Manage test execution status for compliance and reporting",
+        ],
+        examples: [
+            {
+                description: "Update single test case run status to Failed (single execution)",
+                parameters: {
+                    entityIDs: "66095087",
+                    entityType: "TCR",
+                    qmTsRunId: "2720260",
+                    runStatusID: 123266,
+                    isBulkOperation: false,
+                },
+                expectedOutput: "Test case run 66095087 status updated to Failed successfully",
+            },
+            {
+                description: "Bulk update two test case runs to Pass status (bulk execution)",
+                parameters: {
+                    entityIDs: "66095069,66095075",
+                    entityType: "TCR",
+                    qmTsRunId: "2720260",
+                    runStatusID: 123268,
+                    isBulkOperation: true,
+                    comments: "All test cases passed successfully",
+                },
+                expectedOutput: "Test case runs 66095069 and 66095075 updated to Pass status successfully",
+            },
+            {
+                description: "Bulk update all selected test case runs to Not Run status",
+                parameters: {
+                    entityIDs: "66095069,66095075,66095081,66095087,66095093,66095099,66095105",
+                    entityType: "TCR",
+                    qmTsRunId: "2720260",
+                    runStatusID: 123269,
+                    isBulkOperation: true,
+                },
+                expectedOutput: "7 test case runs updated to Not Run status successfully for re-execution",
+            },
+            {
+                description: "Update test case run with build/drop information",
+                parameters: {
+                    entityIDs: "66095087",
+                    entityType: "TCR",
+                    qmTsRunId: "2720260",
+                    runStatusID: 123266,
+                    dropID: 947,
+                    isBulkOperation: false,
+                },
+                expectedOutput: "Test case run updated with execution status and build information",
+            },
+            {
+                description: "Update automated test execution status with automation flag",
+                parameters: {
+                    entityIDs: "66095069,66095075",
+                    entityType: "TCR",
+                    qmTsRunId: "2720260",
+                    runStatusID: 123268,
+                    isAutoExecuted: "1",
+                    isBulkOperation: true,
+                    comments: "Automated test execution completed",
+                },
+                expectedOutput: "Automated test case runs updated to Pass status with automation flag",
+            },
+            {
+                description: "Update test case run status with Part 11 Compliance authentication",
+                parameters: {
+                    entityIDs: "66095087",
+                    entityType: "TCR",
+                    qmTsRunId: "2720260",
+                    runStatusID: 123266,
+                    username: "dhaval.mistry",
+                    password: "Ispl123#",
+                    isBulkOperation: false,
+                },
+                expectedOutput: "Test case run status updated with Part 11 Compliance authentication",
+            },
+            {
+                description: "Update ALL executions of test suite VKMC-TS-20 to Failed (MULTI-CALL OPERATION)",
+                parameters: {
+                    entityIDs: "66341841,66342887,66342893,66342899",
+                    entityType: "TCR",
+                    qmTsRunId: "2733104",
+                    runStatusID: 123269,
+                    isBulkOperation: true,
+                },
+                expectedOutput: "Execution 1/4 updated. The MCP Agent will automatically repeat this operation for executions 2733205, 2733306, and 2733407 using their corresponding entityIDs.",
+            },
+        ],
+        hints: [
+            "CRITICAL: entityIDs, entityType, qmTsRunId, and runStatusID are REQUIRED parameters",
+            "",
+            "⚠️ CRITICAL - ALWAYS FETCH STATUS IDs FROM PROJECT INFO:",
+            "NEVER use hardcoded or memorized status IDs. Status IDs are PROJECT-SPECIFIC and must be fetched dynamically.",
+            "MANDATORY WORKFLOW BEFORE USING runStatusID:",
+            "1. Call mcp_smartbear_qmetry_fetch_qmetry_project_info with the current projectKey",
+            "2. Extract the 'allstatus' array from the response",
+            "3. Match the desired status NAME to find its corresponding ID",
+            "4. Use the fetched ID in the runStatusID parameter",
+            "",
+            "EXAMPLE STATUS ID RESOLUTION:",
+            "User says: 'Update status to Failed'",
+            "Step 1: Call FETCH_PROJECT_INFO → Get allstatus array",
+            "Step 2: Find status where name='Failed' → Extract its id property",
+            "Step 3: Use that id as runStatusID (e.g., 123269 for 'Failed')",
+            "",
+            "COMMON STATUS NAMES (IDs vary by project - MUST VALIDATE):",
+            "- 'Passed' / 'Pass' - Test case executed successfully",
+            "- 'Failed' / 'Fail' - Test case failed with errors",
+            "- 'Blocked' - Test case cannot be executed due to blockers",
+            "- 'Not Run' - Test case not yet executed or needs re-execution",
+            "- 'WIP' / 'Work In Progress' - Test case execution in progress",
+            "- 'Not Applicable' - Test case not applicable for this execution",
+            "",
+            "WHY THIS IS CRITICAL:",
+            "- Status IDs are assigned per QMetry project and are NOT universal",
+            "- Using wrong status ID will update tests with incorrect status",
+            "- Example: ID 123268 might be 'Blocked' in one project but 'Passed' in another",
+            "- The allstatus array is the AUTHORITATIVE source for all status mappings",
+            "",
+            "HOW TO GET entityIDs (Test Case Run IDs):",
+            "1. Call API 'Execution/Fetch Testcase Run ID' (FETCH_TESTCASE_RUNS_BY_TESTSUITE_RUN tool)",
+            "2. From the response, get value of following attribute -> data[<index>].tcRunID",
+            "3. Example: Single ID '66095087' or Multiple IDs '66095069,66095075,66095081'",
+            "4. For bulk operations, provide comma-separated IDs without spaces",
+            "HOW TO GET qmTsRunId (Test Suite Run ID):",
+            "1. Call API 'Execution/Fetch Executions' (FETCH_EXECUTIONS_BY_TESTSUITE tool)",
+            "2. From the response, get value of following attribute -> data[<index>].tsRunID",
+            "3. Example: Test Suite Run ID might be '2720260'",
+            "HOW TO GET runStatusID (Execution Status ID) - DETAILED PROCESS:",
+            "1. Call API 'Admin/Get info Service' (FETCH_PROJECT_INFO tool) with projectKey",
+            "2. From the response, locate the 'allstatus' array",
+            "3. Search for the status object where name matches your desired status (case-insensitive)",
+            "4. Extract the 'id' property from the matching status object",
+            "5. NEVER use example IDs from documentation - they are project-specific",
+            "",
+            "EXAMPLE allstatus ARRAY STRUCTURE:",
+            "allstatus: [",
+            "  { name: 'Passed', defaultName: 'passed', id: 123266, color: '#14892C|#FFFFFF' },",
+            "  { name: 'Failed', defaultName: 'failed', id: 123269, color: '#FF6666|#FFFFFF' },",
+            "  { name: 'Blocked', defaultName: 'blocked', id: 123268, color: '#CCCCCC|#FFFFFF' },",
+            "  { name: 'Not Run', defaultName: 'notrun', id: 123270, color: '#205081|#FFFFFF', isdefault: true },",
+            "  { name: 'Not Applicable', defaultName: 'empty', id: 123267, color: '#59AFE1|#FFFFFF' }",
+            "]",
+            "Note: Above IDs are EXAMPLES ONLY - fetch actual IDs from your project",
+            "HOW TO GET dropID (Build/Drop ID) - OPTIONAL:",
+            "1. Call API 'Build/List' (FETCH_BUILDS tool)",
+            "2. From the response, get value of following attribute -> data[<index>].dropID",
+            "3. Example: Build/Drop ID might be 947",
+            "ENTITY TYPES:",
+            "- 'TCR' = Test Case Run (most common use case)",
+            "- 'TCSR' = Test Case Step Run (for step-level execution updates)",
+            "BULK OPERATION FLAG:",
+            "- isBulkOperation=false: Single test case run update (one entityID)",
+            "- isBulkOperation=true: Multiple test case runs update (comma-separated entityIDs)",
+            "- Auto-detected: If entityIDs contains comma, defaults to true; otherwise false",
+            "AUTOMATION FLAG (isAutoExecuted) - OPTIONAL:",
+            "- '1' = Automated execution (test run by automation framework)",
+            "- '0' = Manual execution (test run by human tester)",
+            "- Used for execution tracking and reporting purposes",
+            "PART 11 COMPLIANCE (username & password) - CONDITIONAL:",
+            "- Required ONLY if Part 11 Compliance is active in your QMetry instance",
+            "- Used for regulatory compliance and audit trail purposes",
+            "- Not needed for standard QMetry installations",
+            "COMMENTS FIELD - OPTIONAL:",
+            "- Add execution notes, failure reasons, or status change context",
+            "- Useful for tracking why status was changed",
+            "- Appears in execution history and audit logs",
+            "COMMON EXECUTION STATUS NAMES:",
+            "- Pass: Test case executed successfully",
+            "- Fail: Test case failed with errors",
+            "- Blocked: Test case cannot be executed due to blockers",
+            "- Not Run: Test case not yet executed or needs re-execution",
+            "- WIP: Work In Progress - test case execution in progress",
+            "WORKFLOW FOR USER PROMPTS:",
+            "1. If user says 'execute test case run by id to failed' or 'update status to fail':",
+            "   - Fetch test case runs to get tcRunID (entityIDs)",
+            "   - Fetch project info to get 'Fail' status ID (runStatusID)",
+            "   - Set isBulkOperation=false for single ID",
+            "2. If user says 'bulk update test case run status to pass' or 'update all to passed':",
+            "   - Fetch test case runs to get multiple tcRunIDs",
+            "   - Fetch project info to get 'Pass' status ID",
+            "   - Set isBulkOperation=true",
+            "   - Join multiple IDs with commas (no spaces)",
+            "3. If user says 'execute status to not run of given test case run ids':",
+            "   - Use provided IDs or fetch if needed",
+            "   - Fetch project info to get 'Not Run' status ID",
+            "   - Set isBulkOperation based on ID count",
+            "4. If the user requests updating status for ALL executions of a test suite, the agent must:",
+            "   1. Call FETCH_EXECUTIONS_BY_TESTSUITE to get all qmTsRunIds.",
+            "   2. For each qmTsRunId:",
+            "      - Call FETCH_TESTCASE_RUNS_BY_TESTSUITE_RUN to get tcRunID (entityIDs)",
+            "      - Fetch project info to get 'Fail' status ID (runStatusID)",
+            "      - Call BULK_UPDATE_EXECUTION_STATUS with the corresponding qmTsRunId + tcRunID + desired runStatusID",
+            "   3. Repeat until all executions are updated.",
+            "   This tool is intended to be invoked multiple times in sequence for multi-execution updates.",
+            "FIELD MAPPING CRITICAL NOTES:",
+            "- entityIDs must be comma-separated STRING (e.g., '66095069,66095075')",
+            "- qmTsRunId must be STRING format (e.g., '2720260')",
+            "- runStatusID must be NUMERIC (e.g., 123268)",
+            "- dropID can be numeric or string (flexible)",
+            "API ENDPOINT: PUT /rest/execution/runstatus/bulkupdate",
+            "This tool is essential for test execution management and status tracking",
+            "Critical for maintaining accurate test execution records and reporting",
+            "Use for manual test execution updates and automated test result integration",
+            "Essential for test execution audit trails and compliance requirements",
+        ],
+        outputDescription: "JSON object with success status, updated execution details, and confirmation message",
+        readOnly: false,
+        idempotent: false,
+    },
 ];

package/dist/qmetry/config/constants.js

@@ -27,6 +27,7 @@ export const QMetryToolsHandlers = {
     FETCH_TESTSUITES_FOR_TESTCASE: "getTestSuitesForTestCase",
     FETCH_TESTCASES_BY_TESTSUITE: "getTestCasesByTestSuite",
     FETCH_EXECUTIONS_BY_TESTSUITE: "getExecutionsByTestSuite",
+    BULK_UPDATE_EXECUTION_STATUS: "bulkUpdateExecutionStatus",
     FETCH_TESTCASE_RUNS_BY_TESTSUITE_RUN: "getTestCaseRunsByTestSuiteRun",
     FETCH_LINKED_ISSUES_BY_TESTCASE_RUN: "getLinkedIssuesByTestCaseRun",
     FETCH_ISSUES_LINKED_TO_TESTCASE: "getIssuesLinkedToTestCase",
@@ -37,4 +38,9 @@ export const QMetryToolsHandlers = {
     FETCH_ISSUES: "getIssues",
     LINK_ISSUES_TO_TESTCASE_RUN: "linkIssuesToTestcaseRun",
     LINK_PLATFORMS_TO_TESTSUITE: "linkPlatformsToTestSuite",
+    IMPORT_AUTOMATION_RESULTS: "importAutomationResults",
+    FETCH_AUTOMATION_STATUS: "fetchAutomationStatus",
+    CREATE_RELEASE: "createRelease",
+    CREATE_CYCLE: "createCycle",
+    UPDATE_CYCLE: "updateCycle",
 };

package/dist/qmetry/config/rest-endpoints.js

@@ -5,6 +5,9 @@ export const QMETRY_PATHS = {
         GET_RELEASES_CYCLES: "/rest/admin/scope/tree",
         GET_BUILD: "/rest/admin/drop/list",
         GET_PLATFORMS: "/rest/admin/platform/list",
+        CREATE_RELEASE: "/rest/admin/release",
+        CREATE_CYCLE: "/rest/admin/cycle",
+        UPDATE_CYCLE: "/rest/admin/cycle",
     },
     TESTCASE: {
         GET_TC_LIST: "/rest/testcases/list/viewColumns",
@@ -31,6 +34,7 @@ export const QMETRY_PATHS = {
         GET_TESTCASE_RUNS_BY_TESTSUITE_RUN: "/rest/execution/list/viewColumns",
         GET_LINKED_ISSUES_BY_TESTCASE_RUN: "/rest/execution/issue/list/forTCRun",
         LINK_PLATFORMS_TO_TESTSUITE: "/rest/testsuites/link/platforms",
+        BULK_UPDATE_EXECUTION_STATUS: "/rest/execution/runstatus/bulkupdate",
     },
     ISSUES: {
         GET_ISSUES_LIST: "/rest/issues/list/viewColumns",
@@ -38,4 +42,8 @@ export const QMETRY_PATHS = {
         GET_ISSUES_LINKED_TO_TC: "/rest/issues/list/ForTC",
         LINK_ISSUES_TO_TESTCASE_RUN: "/rest/execution/link/issue",
     },
+    AUTOMATION: {
+        IMPORT_RESULTS: "/rest/import/createandscheduletestresults/1",
+        GET_STATUS: "/rest/admin/status/automation/:requestID",
+    },
 };

package/dist/qmetry/types/automation.js

@@ -0,0 +1,8 @@
+/**
+ * Default payload values for import automation results
+ */
+export const DEFAULT_IMPORT_AUTOMATION_PAYLOAD = {
+    automationHierarchy: "1",
+    skipWarning: "0",
+    is_matching_required: "true",
+};