ado-test-case-conversion

Converts Azure DevOps QA functional test cases into Markdown specifications for JMeter MCP workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts Azure DevOps QA functional test cases into Markdown specifications that the JMeter MCP workflow can parse.

Core Features & Use Cases

  • Converts ADO test cases into Markdown specs consumable by the JMeter MCP
  • Applies the 9-rule conversion process: artifact removal, sequential step numbering, placeholder substitution, explicit login step insertion, natural-language steps, shadow DOM preservation, multi-item step formatting, a closing END TASK pattern, and file-naming conventions
  • Use cases include migrating test cases from Azure DevOps to JMeter MCP workflows for automation and performance testing

Quick Start

Provide the ADO source path and required metadata to generate a Playwright-ready JMeter MCP spec.

Frequently Asked Questions about ado-test-case-conversion

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

FAQPage Schema
How do I convert Azure DevOps test cases to Playwright specs?

You can convert Azure DevOps test cases to Playwright-ready Markdown specs by providing the ADO source path and required metadata. The conversion applies a 9-rule process including artifact removal, step renumbering, placeholder replacement, and login insertion to generate JMeter MCP-compatible specifications.

What is the JMeter MCP workflow conversion process for ADO test cases?

The JMeter MCP conversion process applies nine rules to Azure DevOps test cases: artifact removal, sequential step numbering, placeholder substitution, explicit login step insertion, natural-language steps, shadow DOM preservation, multi-item step formatting, END TASK closure, and standard file naming conventions.

Does the ADO to Markdown conversion support shadow DOM contexts?

Yes, the ADO to Markdown conversion preserves shadow-root elements during transformation. This shadow DOM preservation ensures that Playwright-ready specs accurately reflect shadow DOM interactions present in the original Azure DevOps functional test cases.

Can I use Azure DevOps test cases with JMeter MCP for automation testing?

Yes, Azure DevOps test cases can be used with JMeter MCP by first converting them into Markdown specifications. This allows you to migrate ADO QA functional test cases into JMeter MCP workflows for automation and performance testing.

What are the limitations of converting ADO test cases to Markdown specs?

The conversion requires the correct ADO source path and required metadata to generate Playwright-ready specs. It strictly applies artifact removal, step renumbering, and standard file naming, so test cases with non-standard ADO formatting or missing metadata may not convert correctly.