azure-app-testing Skill
✓ OffiziellBietet Experten-Unterstützung bei der Fehlersuche, Konfiguration und dem Deployment von Azure Load Testing und Playwright Workspaces.
- GitHub Stars
- 811
- Dateien
- 1
- Letzter Commit
- 9. Nov. 2026
- Lizenz
- CC-BY-4.0
- Erlaubte Tools
- —
Was macht der azure-app-testing Skill?
Bietet Experten-Unterstützung bei der Fehlersuche, Konfiguration und dem Deployment von Azure Load Testing und Playwright Workspaces.
Zusammenfassung erzeugt aus der SKILL.md des Skills.
Über den azure-app-testing skill
Entwickler, die mit Azure Load Testing und Playwright Workspaces arbeiten, können diesen Skill nutzen, um Experten-Unterstützung bei der Fehlersuche, Konfiguration und dem Deployment von Testumgebungen zu erhalten. Er hilft bei komplexen Aufgaben wie der Diagnose fehlerhafter Load Tests, der Verwaltung von privaten Endpoints innerhalb virtueller Netzwerke und der Optimierung der Playwright-Parallelität. Der Skill ist für Engineers konzipiert, die Architektur- und Designmuster implementieren, Sicherheit via RBAC und Key Vault verwalten oder Service-Limits und Quotas handhaben müssen.
Wenn ein Agent diesen Skill lädt, kann er auf lokale Referenzinhalte zugreifen oder Live-Dokumentation über mcp_microsoftdocs:microsoft_docs_fetch oder fetch_webpage abrufen. Dies ermöglicht es dem Agenten, aktuelle Ratschläge zur Integration von JMeter oder Locust, zum Setup von CI/CD-Pipelines und zur Konfiguration von Multi-Region Load Tests zu geben. Er ist speziell auf die Entwicklung von Application Testing zugeschnitten und nicht für die Verwaltung von Azure Test Plans, Azure DevOps, Azure Pipelines oder Azure App Service gedacht.
Was ein agent damit machen kann
- 1Fehlerhafte Load Tests troubleshootenDiagnose und Behebung von Problemen, die während Azure Load Testing Runs auftreten, mittels Debug-Modus oder KI-gestützter Insights.
- 2Testumgebungen absichernImplementierung von Sicherheitsmaßnahmen wie Managed Identities, Key Vault und RBAC für deine Testing-Infrastruktur.
- 3Playwright Performance optimierenErmittlung der besten Konfiguration für Parallelität, um die Effizienz von Playwright Workspaces zu steigern.
- 4Netzwerk-Isolation konfigurierenDesign von Test-Setups, die virtuelle Netzwerke und private Endpoints für eine sichere Konnektivität nutzen.
Geschrieben basierend auf dem SKILL.md des skills. Jeder use case wurde gegen ein zitat daraus geprüft.
So installierst du den azure-app-testing Skill
Jeder Befehl kopiert den Skill-Ordner in das Skills-Verzeichnis des Clients. Starte den Client neu oder beginne eine neue Session, um ihn zu laden.Den azure-app-testing Skill in Claude Code installieren
~/.claude/skills/azure-app-testing/SKILL.md
$ npx degit MicrosoftDocs/Agent-Skills/skills/azure-app-testing ~/.claude/skills/azure-app-testingDen azure-app-testing Skill in Claude Code (project) installieren
.claude/skills/azure-app-testing/SKILL.md
$ npx degit MicrosoftDocs/Agent-Skills/skills/azure-app-testing .claude/skills/azure-app-testingDen azure-app-testing Skill in Codex installieren
~/.agents/skills/azure-app-testing/SKILL.md
$ npx degit MicrosoftDocs/Agent-Skills/skills/azure-app-testing ~/.agents/skills/azure-app-testingDen azure-app-testing Skill in Gemini CLI installieren
~/.gemini/skills/azure-app-testing/SKILL.md
$ npx degit MicrosoftDocs/Agent-Skills/skills/azure-app-testing ~/.gemini/skills/azure-app-testingDen azure-app-testing Skill in Claude.ai installieren
npx degit MicrosoftDocs/Agent-Skills/skills/azure-app-testing azure-app-testing && zip -r azure-app-testing.zip azure-app-testing # claude.ai → Customize → Skills → + → Create skill → Upload a skill → azure-app-testing.zip
Automatisierte Checks
Geluften am 15. Nov. 2026Vollständiger Bericht →Noch nicht verifiziert. Ein Skill braucht 80 Punkte, keinen schweren Befund und genug Daten für unsere Prüfung. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarmicrosoftdocs/agent-skills/skills/azure-app-testing is public and reachablegithub.com/microsoftdocs/agent-skills/tree/HEAD/skills/azure ↗Bestanden
- Open Source Lizenz (OSI)CC-BY-4.0 is not OSI-approvedspdx.org/licenses/CC-BY-4.0.html ↗Befund
- Commit oder Release im letzten JahrLast commit 2026-11-09github.com/microsoftdocs/agent-skills/commits ↗Bestanden
- Keine Download-und-Ausführen-Muster oder Zugangsdatendiebstahl in SkriptenNo scripts in the skill folderBestanden
- Keine versteckten Anweisungen in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/microsoftdocs/agent-skills/blob/HEAD/skills/azure ↗Bestanden
- Vorab erlaubte Tools sind eingeschränktNo pre-approved tools; the agent asks before using onegithub.com/microsoftdocs/agent-skills/blob/HEAD/skills/azure ↗Bestanden
- SKILL.md folgt dem Agent-Skills-FormatValid name and description; says when to use it; 130 linesgithub.com/microsoftdocs/agent-skills/blob/HEAD/skills/azure ↗Bestanden
SKILL.md
Auf GitHub ansehenAzure App Testing Skill
This skill provides expert guidance for Azure App Testing. Covers troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities.
How to Use This Skill
IMPORTANT for Agent: Use the Category Index below to locate relevant sections. For categories with line ranges (e.g.,
L35-L120), useread_filewith the specified lines. For categories with file links (e.g.,[security.md](security.md)), useread_fileon the linked reference file
IMPORTANT for Agent: If
metadata.generated_atis more than 3 months old, suggest the user pull the latest version from the repository. Ifmcp_microsoftdocstools are not available, suggest the user install it: Installation Guide
This skill requires network access to fetch documentation content:
- Preferred: Use
mcp_microsoftdocs:microsoft_docs_fetchwith query stringfrom=learn-agent-skill. Returns Markdown. - Fallback: Use
fetch_webpagewith query stringfrom=learn-agent-skill&accept=text/markdown. Returns Markdown.
Category Index
| Category | Lines | Description |
|---|---|---|
| Troubleshooting | L37-L48 | Diagnosing and fixing Azure Load Testing issues, including AI-driven insights, debug mode, browser recorder, private endpoints, and Playwright Workspaces (remote MCP, reporting, and test run errors). |
| Best Practices | L49-L57 | Guidance on load testing App Service apps, tuning high-scale tests, finding performance bottlenecks, and optimizing Playwright Workspace tests for reliability and low latency. |
| Decision Making | L58-L65 | Guides for deciding load test resource moves (regions, groups, subscriptions) and tuning performance settings like Azure Functions configs and Playwright parallelism. |
| Architecture & Design Patterns | L66-L71 | Designing Azure Load Testing setups with virtual networks and private endpoints, including VNet-injected tests, network isolation, and testing services over private connectivity. |
| Limits & Quotas | L72-L79 | Usage caps, service limits, and configuration for Azure Load Testing and Playwright Workspaces, including monthly quotas, free trial restrictions, and how to adjust or review these limits. |
| Security | L80-L92 | Securing Azure Load Testing and Playwright Workspaces: RBAC, auth for endpoints, managed identities, Key Vault, CMK encryption, certificates, access tokens, and Azure Policy controls. |
| Configuration | L93-L113 | Configuring and running Azure Load Testing and Playwright Workspaces: test definitions, HTTP/JMeter settings, secrets, monitoring, baselines, reporting/export, CI/CD YAML, scheduling, and multi-region load. |
| Integrations & Coding Patterns | L114-L125 | Patterns and tools for integrating Azure Load Testing with JMeter, Locust, VS Code/Copilot, CSV data, plugins, and Playwright (including MCP and local/private app testing). |
| Deployment | L126-L130 | Setting up and automating CI/CD for Azure Load Testing, including manual pipeline configuration and integration with Azure Pipelines for automated test runs. |
Troubleshooting
Best Practices
| Topic | URL |
|---|---|
| Load test Azure App Service apps with Azure Load Testing | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/concept-load-test-app-service |
| Configure high-scale load tests and engine instances in Azure | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/how-to-high-scale-load |
| Identify performance bottlenecks using Azure Load Testing | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/tutorial-identify-bottlenecks-azure-portal |
| Configure Playwright visual comparisons in Workspaces reliably | https://learn.microsoft.com/en-us/azure/app-testing/playwright-workspaces/how-to-configure-visual-comparisons |
| Optimize regional latency for Playwright Workspaces tests | https://learn.microsoft.com/en-us/azure/app-testing/playwright-workspaces/how-to-optimize-regional-latency |
Decision Making
| Topic | URL |
|---|---|
| Move Azure Load Testing resources between regions | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/how-to-move-between-regions |
| Move Azure Load Testing resources across resource groups or subscriptions | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/how-to-move-between-resource-groups-subscriptions |
| Choose optimal Azure Functions configuration with load tests | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/how-to-optimize-azure-functions |
| Determine optimal Playwright Workspaces parallelism configuration | https://learn.microsoft.com/en-us/azure/app-testing/playwright-workspaces/concept-determine-optimal-configuration |
Architecture & Design Patterns
| Topic | URL |
|---|---|
| Choose virtual network deployment scenarios for Azure Load Testing | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/concept-azure-load-testing-vnet-injection |
| Test private endpoints with virtual network–injected Azure Load Testing | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/how-to-test-private-endpoint |
Limits & Quotas
| Topic | URL |
|---|---|
| Configure monthly usage limits for Azure Load Testing | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/how-to-manage-usage-limits |
| Service limits and quotas for Azure Load Testing | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/resource-limits-quotas-capacity |
| Understand Playwright Workspaces free trial limits | https://learn.microsoft.com/en-us/azure/app-testing/playwright-workspaces/how-to-try-playwright-workspaces-free |
| Review Playwright Workspaces limits and configuration | https://learn.microsoft.com/en-us/azure/app-testing/playwright-workspaces/resource-limits-quotas-capacity |
Security
Configuration
Integrations & Coding Patterns
Deployment
| Topic | URL |
|---|---|
| Manually configure CI/CD pipelines for Azure Load Testing | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/how-to-configure-load-test-cicd |
| Automate Azure Load Testing in Azure Pipelines CI/CD | https://learn.microsoft.com/en-us/azure/app-testing/load-testing/quickstart-add-load-test-cicd |
Dateien in diesem Skill
1azure-app-testing Skill-Fragen
Wie installiere ich den azure-app-testing Skill in Claude Code?
Führe npx degit MicrosoftDocs/Agent-Skills/skills/azure-app-testing ~/.claude/skills/azure-app-testing aus. Claude Code lädt Skills aus ~/.claude/skills (alle Projekte) oder .claude/skills (ein Projekt) und nutzt einen Skill, wenn seine Beschreibung zur Aufgabe passt.
Welche Clients können den azure-app-testing Skill nutzen?
Jeder Client, der das Agent Skills-Format liest: Claude Code, Codex, Gemini CLI und claude.ai (als ZIP hochladen). Skripte im Skill laufen nur dort, wo der Client Codeausführung erlaubt.
Kann ich private Endpoints mit Azure Load Testing testen?
Ja, du kannst private Endpoints testen, indem du Azure Load Testing mit Virtual Network Injection nutzt.
Wie sichere ich Azure Load Testing Ressourcen?
Die Sicherheit kann über RBAC-Rollen, Managed Identities, Key Vault, Verschlüsselung mit Customer-Managed Keys (CMK) und Azure Policy Controls verwaltet werden.