qmetry_fetch_executions_by_test_suite

Get executions for a given test suite in QMetry Parameters: - projectKey (string): Project key - unique identifier for the project (default: "default") - baseUrl (string): The base URL for the QMetry instance (must be a valid URL) (default: "https://testmanagement.qmetry.com") - tsID (number) *required*: Test Suite numeric ID (required for fetching test cases linked to test suite). This is the internal numeric identifier, not the entity key. NOTE: To get the tsID - Call API 'Testsuite/Fetch Testsuite' From the response, get value of following attribute -> data[<index>].id - tsFolderID (number): Test Suite folder ID (required for fetching test suites). This is the numeric identifier for the test suite folder. IMPORTANT: Get from project info response → rootFolders.TS.id (e.g., 113557 for MAC project). Use FETCH_PROJECT_INFO tool first to get this ID if not provided by user. For root folder: use rootFolders.TS.id, for sub-folders: use specific folder IDs. - gridName (string): Grid Name to be displayed (default 'TESTEXECUTIONLIST') - viewId (number): ViewId for test execution - SYSTEM AUTOMATICALLY RESOLVES THIS. Leave empty unless you have a specific viewId. System will fetch project info using the projectKey and extract latestViews.TE.viewId automatically. Manual viewId only needed if you want to override the automatic resolution. - start (number): Start index for pagination - defaults to 0 (default: 0) - page (number): Page number to return (starts from 1) (default: 1) - limit (number): Number of records (default 10). (default: 10) - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") Output Description: JSON object with executions array containing execution details, status, platforms, releases, and execution metadata Use Cases: 1. Get all executions for a specific test suite for reporting purposes 2. Analyze test execution results and trends within a test suite 3. Filter executions by release, cycle, platform, or automation status 4. Monitor test suite execution performance across different environments 5. Generate execution reports for specific test suites 6. Track execution history and patterns for test suite optimization 7. Validate test suite execution coverage across releases and cycles 8. Audit test execution data for compliance and quality assurance 9. Export execution data for external reporting and analytics Examples: 1. Get all executions for test suite ID 194955 json { "tsID": 194955 } Expected Output: List of executions for the test suite with execution details, status, and metadata 2. Get executions with test suite folder and view ID json { "tsID": 194955, "tsFolderID": 126554, "viewId": 41799 } Expected Output: Executions filtered by test suite folder and specific view configuration 3. Filter executions by release and cycle json { "tsID": 194955, "filter": "[{\"type\":\"list\",\"value\":[55178],\"field\":\"releaseID\"},{\"type\":\"list\",\"value\":[111577],\"field\":\"cycleID\"}]" } Expected Output: Executions filtered by specific release (55178) and cycle (111577) 4. Filter executions by platform and automation status json { "tsID": 194955, "filter": "[{\"type\":\"list\",\"value\":[12345],\"field\":\"platformID\"},{\"type\":\"boolean\",\"value\":true,\"field\":\"isAutomatedFlag\"}]" } Expected Output: Automated executions filtered by specific platform (12345) 5. Get only active (non-archived) executions json { "tsID": 194955, "filter": "[{\"value\":[0],\"type\":\"list\",\"field\":\"isArchived\"}]" } Expected Output: Active executions that are not archived 6. Get executions with custom pagination and grid name json { "tsID": 194955, "gridName": "TESTEXECUTIONLIST", "page": 1, "limit": 25 } Expected Output: Paginated list of executions with 25 items per page using specific grid configuration Hints: 1. !MOST IMPORTANT HOW TO GET viewId: 2. CRITICAL: Always resolve and use the correct test execution viewId for the current project when calling this tool. 3. The viewId parameter must be fetched from the active project's info (latestViews.TEL.viewId). 4. 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. 5. Usage workflow: 6. 1. Fetch project info for the current project (Admin/Get info Service). 7. 2. Extract latestViews.TEL.viewId from the response. 8. 3. Use this viewId in the Fetch Test Case Runs by Test Suite Run API call. 9. Example: 10. { 11. tsID: 1533730, 12. viewId: 94194, 13. gridName: 'TESTEXECUTIONLIST' 14. } 15. CRITICAL: tsID parameter is REQUIRED - this is the Test Suite numeric ID 16. HOW TO GET tsID: 17. 1. Call API 'Testsuite/Fetch Testsuite' to get available test suites 18. 2. From the response, get value of following attribute -> data[<index>].id 19. 3. Example: Test Suite 'Regression Suite' might have ID 194955 20. HOW TO GET tsFolderID (optional): 21. 1. Call API 'Testsuite/List of folders' to get test suite folders 22. 2. From the response, get value of following attribute -> data[<index>].id 23. 3. Example: Test Suite folder might have ID 126554 24. FILTER CAPABILITIES: Extensive filtering by execution properties 25. FILTER FIELDS: releaseID (list), cycleID (list), platformID (list), isAutomatedFlag (boolean), isArchived (list) 26. RELEASE/CYCLE FILTERING: Use numeric IDs in list format (get from FETCH_RELEASES_AND_CYCLES) 27. PLATFORM FILTERING: Use numeric platform IDs (get from FETCH_PLATFORMS) 28. AUTOMATION STATUS: Use boolean true/false for isAutomatedFlag field 29. ARCHIVE STATUS: 0=Active executions, 1=Archived executions 30. GRID NAME: Default is 'TESTEXECUTIONLIST' - used for execution list display configuration 31. VIEW ID: Optional numeric identifier for specific execution view configurations 32. Multiple filter conditions are combined with AND logic 33. Use pagination for large execution result sets (start, page, limit parameters) 34. This tool is essential for test execution analysis and reporting 35. Critical for monitoring test suite performance and execution trends 36. Use for compliance reporting and execution audit trails 37. Essential for test execution planning and resource optimization. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

qmetry_fetch_executions_by_test_suite accepts 10 parameters: page, tsID, limit, start, filter, viewId, baseUrl, gridName, projectKey, tsFolderID. Required: tsID. The full parameter table on this page comes from the server's own tool schema.

Register the SmartBear MCP server in PolicyLayer and add a rule for qmetry_fetch_executions_by_test_suite: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches SmartBear MCP. Nothing to install.

qmetry_fetch_executions_by_test_suite is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Yes. Add a rate_limit block to the qmetry_fetch_executions_by_test_suite rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

Set action: deny in the PolicyLayer policy for qmetry_fetch_executions_by_test_suite. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

qmetry_fetch_executions_by_test_suite is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.