QMetry: Link Platforms to Test Suite
qmetry_link_platforms_to_test_suiteDefine execution environments for test suites by linking one or more platforms, enabling organized cross-platform testing.
Instructions
Link one or more platforms to a QMetry Test Suite.
Toolset: Test Suites
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)
qmTsId (number) required: Id of Test Suite (required). CRITICAL: the parameter name is 'qmTsId' — do NOT use 'tsId', 'testSuiteId', 'tsID', or other variants. Accepts a string or number. To get the qmTsId - Call API 'Testsuite/Fetch Testsuite'. From the response, get value -> data[].id
qmPlatformId (string) required: Comma-separated Platform IDs (required). CRITICAL: the parameter name is 'qmPlatformId' — do NOT use 'platformId', 'platformID', 'platformIds', or other variants. Accepts a number or string. To get the qmPlatformId - Call API 'Platform/List'. From the response, get value -> data[].platformID
Output Description: JSON object with linkage status, success message, and details.
Use Cases: 1. Link a single platform to a test suite 2. Link multiple platforms to a test suite for cross-platform testing 3. Define execution environments for a test suite 4. Organize test suites by supported platforms 5. Set up platform-specific test suite configurations
Examples:
Link single platform to a test suite
{
"qmTsId": 1511970,
"qmPlatformId": "63004"
}Expected Output: Platform 63004 linked to test suite 1511970 successfully.
Link multiple platforms to a test suite
{
"qmTsId": 1511970,
"qmPlatformId": "63004,63005,63006"
}Expected Output: Platforms 63004, 63005, 63006 linked to test suite 1511970 successfully.
Hints: 1. CRITICAL: qmTsId and qmPlatformId are REQUIRED parameters 2. To get the qmTsId (Test Suite ID): 3. 1. Call 'Testsuite/Fetch Testsuite' API 4. 2. From response, use data[].id 5. 3. Example: Test Suite 'Login Tests' might have ID 1511970 6. To get the qmPlatformId (Platform ID): 7. 1. Call 'Platform/List' API (Fetch Platforms tool) 8. 2. From response, use data[].platformID 9. 3. Example: Platform 'Chrome' might have ID 63004 10. qmPlatformId accepts comma-separated values for multiple platforms 11. Format for multiple platforms: '63004,63005,63006' 12. No spaces in the comma-separated list 13. If test suite entity key (e.g., VT-TS-12) is provided, first fetch test suites to resolve numeric ID 14. Platforms represent browsers, operating systems, devices, or custom environments 15. This tool helps organize cross-platform test execution 16. Essential for comprehensive platform coverage testing
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| qmTsId | Yes | Id of Test Suite (required). CRITICAL: the parameter name is 'qmTsId' — do NOT use 'tsId', 'testSuiteId', 'tsID', or other variants. Accepts a string or number. To get the qmTsId - Call API 'Testsuite/Fetch Testsuite'. From the response, get value -> data[<index>].id | |
| baseUrl | No | The base URL for the QMetry instance (must be a valid URL) | |
| projectKey | No | Project key - unique identifier for the project | default |
| qmPlatformId | Yes | Comma-separated Platform IDs (required). CRITICAL: the parameter name is 'qmPlatformId' — do NOT use 'platformId', 'platformID', 'platformIds', or other variants. Accepts a number or string. To get the qmPlatformId - Call API 'Platform/List'. From the response, get value -> data[<index>].platformID |