Performance

This page is generated from the live QualityMax MCP registry. Examples use placeholders; replace them with values for your workspace.

`gatling_to_k6`

Purpose

Convert a Gatling Scala simulation to k6 JavaScript. Handles HTTP builders, injection profiles, checks, and feeders.

Parameters

Parameter	Type	Required	Description
`gatling_code`	`string`	Yes	Gatling Scala simulation code
`target_url`	`string`	No	Override target URL
`test_type`	`string`	No	Target k6 test type
`project_id`	`integer`	No	Project to save converted script to

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "gatling_code": "your-gatling-code"
  },
  "tool": "gatling_to_k6"
}

`jmeter_to_k6`

Purpose

Convert a JMeter .jmx test plan to k6 JavaScript. Handles thread groups, HTTP samplers, timers, assertions, and extractors.

Parameters

Parameter	Type	Required	Description
`jmeter_xml`	`string`	Yes	JMeter .jmx XML content
`target_url`	`string`	No	Override target URL in converted script
`test_type`	`string`	No	Target k6 test type
`project_id`	`integer`	No	Project to save converted script to

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "jmeter_xml": "your-jmeter-xml"
  },
  "tool": "jmeter_to_k6"
}

`k6_check_status`

Purpose

Check the status and results of a k6 test execution. Poll this after k6_run_test.

Parameters

Parameter	Type	Required	Description
`execution_id`	`string`	Yes	Execution ID from k6_run_test
`include_receipt_details`	`boolean`	No	No description supplied.
`include_artifacts`	`boolean`	No	No description supplied.

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "execution_id": "your-execution-id"
  },
  "tool": "k6_check_status"
}

`k6_create_script`

Purpose

Create a k6 performance test script. Supports load, stress, spike, soak, smoke, breakpoint, API, security, and browser test types.

Parameters

Parameter	Type	Required	Description
`project_id`	`integer`	Yes	Project ID to create script in
`name`	`string`	Yes	Script name
`test_type`	`string`	No	Type of k6 test
`target_url`	`string`	Yes	Target URL to test
`code`	`string`	No	k6 script code (optional - will be generated if not provided)
`test_case_id`	`integer`	No	Optional test case ID to link to
`description`	`string`	No	Script description

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "name": "your-name",
    "project_id": 1,
    "target_url": "https://example.com"
  },
  "tool": "k6_create_script"
}

`k6_generate`

Purpose

Generate a k6 performance test script from a target URL and optional endpoint list. Auto-creates load profiles with thresholds.

Parameters

Parameter	Type	Required	Description
`project_id`	`integer`	Yes	Project ID
`target_url`	`string`	Yes	URL to generate test for
`test_type`	`string`	No	Type of test to generate
`endpoints`	`array`	No	API endpoints to test [{method, path, body?}]
`vus`	`integer`	No	Virtual users
`duration`	`string`	No	Test duration
`name`	`string`	No	Script name

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "project_id": 1,
    "target_url": "https://example.com"
  },
  "tool": "k6_generate"
}

`k6_generate_from_test_case`

Purpose

Generate a k6 performance test from an existing QualityMax test case. Extracts HTTP interactions and builds a load test.

Parameters

Parameter	Type	Required	Description
`test_case_id`	`integer`	Yes	Test case ID to generate k6 script from
`test_type`	`string`	No	k6 test type
`vus`	`integer`	No	Virtual users
`duration`	`string`	No	Test duration

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "test_case_id": 1
  },
  "tool": "k6_generate_from_test_case"
}

`k6_get_script`

Purpose

Get a k6 script by ID including its code

Parameters

Parameter	Type	Required	Description
`script_id`	`integer`	Yes	k6 script ID

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "script_id": 1
  },
  "tool": "k6_get_script"
}

`k6_list_scripts`

Purpose

List k6 performance test scripts for a project

Parameters

Parameter	Type	Required	Description
`project_id`	`integer`	Yes	Project ID to list scripts for
`test_type`	`string`	No	Filter by test type

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "project_id": 1
  },
  "tool": "k6_list_scripts"
}

`k6_report`

Purpose

Generate a performance test report. Supports single execution reports, comparison reports, and project-level summaries.

Parameters

Parameter	Type	Required	Description
`execution_id`	`string`	No	Single execution ID for detailed report
`project_id`	`integer`	No	Project ID for project summary report
`compare_executions`	`array`	No	List of execution IDs to compare
`format`	`string`	No	Report format

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {},
  "tool": "k6_report"
}

`k6_run_test`

Purpose

Execute a k6 performance test. Returns an execution ID for polling status. Supports overriding VUs, duration, and thresholds.

Parameters

Parameter	Type	Required	Description
`script_id`	`integer`	Yes	k6 script ID to execute
`vus`	`integer`	No	Number of virtual users (overrides script default)
`duration`	`string`	No	Test duration (e.g., ‘30s’, ‘5m’)
`env_vars`	`object`	No	Environment variables for the test

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "script_id": 1
  },
  "tool": "k6_run_test"
}

`k6_update_script`

Purpose

Update a k6 script’s code, name, or configuration

Parameters

Parameter	Type	Required	Description
`script_id`	`integer`	Yes	k6 script ID to update
`code`	`string`	No	Updated k6 script code
`name`	`string`	No	Updated name
`test_type`	`string`	No	Updated test type

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "script_id": 1
  },
  "tool": "k6_update_script"
}

`locust_to_k6`

Purpose

Convert a Locust Python load test to k6 JavaScript. Handles HttpUser tasks, wait times, on_start/on_stop, and task weights.

Parameters

Parameter	Type	Required	Description
`locust_code`	`string`	Yes	Locust Python test code
`target_url`	`string`	No	Override target URL
`test_type`	`string`	No	Target k6 test type
`project_id`	`integer`	No	Project to save converted script to

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "locust_code": "your-locust-code"
  },
  "tool": "locust_to_k6"
}

`playwright_to_k6`

Purpose

Convert Playwright API tests or page navigations to k6 load tests. Extracts HTTP calls and builds k6 equivalents.

Parameters

Parameter	Type	Required	Description
`playwright_code`	`string`	Yes	Playwright JavaScript/TypeScript test code
`target_url`	`string`	No	Override target URL
`test_type`	`string`	No	Target k6 test type
`project_id`	`integer`	No	Project to save converted script to

Return shape

The live registry does not declare a response schema. Expect a tool-specific JSON result and handle success, error, and result fields defensively.

Worked example

{
  "arguments": {
    "playwright_code": "your-playwright-code"
  },
  "tool": "playwright_to_k6"
}