jmeter-swagger-conversion

Convert Swagger/OpenAPI specifications into parameterized JMeter JMX scripts.

4|1|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/canyonlabz/mcp-perf-suite --skill jmeter-swagger-conversion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jmeter-swagger-conversion
Source: https://github.com/canyonlabz/mcp-perf-suite/tree/main/.cursor/skills/jmeter-swagger-conversion
Command: npx skills add https://github.com/canyonlabz/mcp-perf-suite --skill jmeter-swagger-conversion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts Swagger/OpenAPI specifications into JMeter JMX scripts for automated performance testing from API definitions.

Core Features & Use Cases

  • Swagger/OpenAPI to JMX: Convert Swagger 2.x or OpenAPI 3.x specs into ready-to-run JMeter scripts.
  • Automation-ready outputs: Generate parameterized JMX scripts suitable for integration into CI/CD/test pipelines.
  • Use Case: Turn an OpenAPI definition into a reusable load test for a REST API.

Quick Start

Provide an absolute path to the Swagger/OpenAPI spec file and a unique test_run_id to begin the conversion and artifact generation.

Frequently Asked Questions about jmeter-swagger-conversion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert an OpenAPI spec to a JMeter JMX script?

Converting an OpenAPI spec to a JMeter JMX script requires providing an absolute spec file path and a unique test run ID to generate parameterized load test artifacts.

Can I use Swagger 2.x specifications to generate JMeter load tests?

Yes, Swagger 2.x specifications can be used to generate JMeter load tests alongside OpenAPI 3.x definitions. The conversion produces ready-to-run, parameterized JMX scripts for REST API performance testing.

What is the best way to automate JMeter performance testing from an API spec in CI/CD?

Automating JMeter performance testing from an API spec in CI/CD is done by generating automation-ready, parameterized JMX scripts from OpenAPI definitions for reproducible test pipelines.

Does converting API specs to JMeter scripts require a base URL?

Converting API specs to JMeter scripts requires an absolute spec path and test run ID, while the base URL is optional. You can also apply grouping controls to organize the generated JMX artifacts.

Where are the generated JMX artifacts output when exporting JMeter scripts from OpenAPI?

Generated JMX artifacts are output under the artifacts/{test_run_id}/jmeter directory structure. This organizes reproducible performance test scripts by their unique test run identifier.