Skills azure-microsoft-playwright-testing-ts
📦

azure-microsoft-playwright-testing-ts

Low Risk ⚙️ External commands🌐 Network access🔑 Env variables

Run Playwright Tests on Azure Cloud Browsers

Scale your end-to-end browser tests across Azure's cloud-hosted browsers without managing infrastructure. Integrate with CI/CD pipelines and view results in Azure portal with built-in reporting.

Supports: Claude Codex Code(CC)
📊 69 Adequate
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

Toggle on and start using

Test it

Using "azure-microsoft-playwright-testing-ts". Set up Azure Playwright Testing with default configuration

Expected outcome:

Creates playwright.service.config.ts with createAzurePlaywrightConfig, DefaultAzureCredential for authentication, and HTML reporter enabled before Azure reporter for proper output rendering.

Using "azure-microsoft-playwright-testing-ts". Run tests with 20 parallel workers on Azure

Expected outcome:

Executes npx playwright test --config=playwright.service.config.ts --workers=20, distributing tests across cloud-hosted browsers and displaying results in Azure portal.

Security Audit

Low Risk
v1 • 2/25/2026

Static analysis flagged 60 patterns but all are false positives from Markdown documentation. The skill contains TypeScript code examples for Azure Playwright Testing SDK. External command patterns are npm/bash examples in code blocks, not executable code. Network and environment variable access are legitimate Azure authentication patterns required for the service.

1
Files scanned
308
Lines analyzed
4
findings
1
Total audits
Low Risk Issues (1)
SKILL.md:13-14SKILL.md:34-35
Documentation Contains External Service URLs
The skill documentation includes Azure service endpoint URLs and references to external Microsoft APIs. These are legitimate service endpoints for Azure Playwright Workspaces but users should verify URLs match their workspace configuration.

Risk Factors

⚙️ External commands (3)
SKILL.md:17-25 SKILL.md:100-102 SKILL.md:204-210
🌐 Network access (2)
SKILL.md:34-35 SKILL.md:139-140
🔑 Env variables (1)
SKILL.md:200-202
Audited by: claude

Quality Score

38
Architecture
100
Maintainability
87
Content
31
Community
88
Security
91
Spec Compliance

What You Can Build

Enterprise QA Team Scaling Tests

Run large test suites across multiple browser configurations in parallel without maintaining local browser infrastructure. Reduce test execution time from hours to minutes.

CI/CD Pipeline Integration

Add cloud-hosted browser testing to GitHub Actions or Azure Pipelines with automatic authentication and result reporting in Azure portal.

Cross-Browser Compatibility Testing

Execute tests across Chromium, Firefox, and WebKit browsers hosted on Azure infrastructure with consistent environments.

Try These Prompts

Basic Azure Playwright Setup 
Help me set up Azure Playwright Testing for my TypeScript project. I need to configure the package with Entra ID authentication and run my existing Playwright tests on cloud browsers.
Configure CI/CD Pipeline 
Create a GitHub Actions workflow that runs Playwright tests on Azure Playwright Workspaces. Include Azure login step, environment variables for the service URL, and parallel test execution with 20 workers.
Migration from Old Package 
My project uses the deprecated @azure/microsoft-playwright-testing package. Help me migrate to @azure/playwright by updating the configuration, authentication, and reporter imports.
Advanced Configuration with Artifacts 
Configure Azure Playwright Testing with trace collection on retries, video recording on failures, and custom run names for the Azure portal. Use ServiceOS.LINUX and set connection timeout to 30 seconds.

Best Practices

  • Use Entra ID authentication with explicit credential parameter instead of access tokens for better security
  • List HTML reporter before Azure reporter in configuration to ensure proper report generation
  • Enable trace and video artifacts for debugging failures with trace set to on-first-retry

Avoid

  • Do not hardcode access tokens in configuration files - use environment variables or Azure Key Vault
  • Avoid running tests without sufficient workers - underutilizes Azure's parallel execution capability
  • Do not skip HTML reporter when using Azure reporter - Azure reporter depends on HTML reporter output

Frequently Asked Questions

What is the difference between @azure/playwright and @azure/microsoft-playwright-testing?
The @azure/microsoft-playwright-testing package is retired as of March 8, 2026. The new @azure/playwright package requires explicit credential parameters and uses createAzurePlaywrightConfig instead of getServiceConfig.
How do I authenticate with Azure Playwright Workspaces?
Use Entra ID authentication with DefaultAzureCredential for local development or ManagedIdentityCredential for CI/CD. Authenticate with az login before running tests locally.
What Playwright version do I need?
Playwright 1.47 or higher is required for basic usage. Azure reporter features require Playwright 1.57 or higher.
How many parallel workers can I use?
Azure Playwright Workspaces supports 20 or more parallel workers depending on your workspace configuration. Use --workers=20 or higher for optimal parallel execution.
Can I use this with existing Playwright tests?
Yes, the skill wraps your existing Playwright configuration. Import your base config and extend it with createAzurePlaywrightConfig without modifying individual test files.
How do I view test results after execution?
Test results appear in Azure portal under your Playwright Workspace. Configure the Azure reporter and list HTML reporter first for local HTML reports.

Developer Details

Author

sickn33

License

MIT

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-microsoft-playwright-testing-ts

Ref

main

File structure

📄 SKILL.md