# Scale Playwright Tests with Azure

Local browser capacity can slow large Playwright suites and obscure centralized results. This skill guides Azure configuration, authentication, parallel execution, reporting, CI integration, and package migration.

## Install

```bash
npx skillstore add sickn33/azure-microsoft-playwright-testing-ts
```

## Metadata

- Status: approved
- Slug: sickn33-azure-microsoft-playwright-testing-ts
- Skillstore revision: r2
- Version status: missing
- Tree hash: ae8650facfbce8761c89c2b3a363a01228fce8b993b3e0bf864dc025f0af059e
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-microsoft-playwright-testing-ts
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-azure-microsoft-playwright-testing-ts
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-azure-microsoft-playwright-testing-ts/manifest

## Capabilities

- Guides installation of the current Azure Playwright package and its TypeScript dependencies.
- Builds service configuration for Linux or Windows cloud-hosted browsers.
- Configures Microsoft Entra ID, default credentials, or managed identity authentication.
- Runs Playwright suites with configurable worker counts and connection timeouts.
- Adds Azure reporting to local, GitHub Actions, or Azure Pipelines workflows.
- Maps retired package APIs and settings to their current replacements.

## Use Cases

- Scale a Test Suite: Create an Azure service configuration and run a large TypeScript Playwright suite across cloud-hosted browsers.
- Add Cloud Tests to CI: Configure identity-based authentication and execute Azure-hosted Playwright tests from GitHub Actions or Azure Pipelines.
- Migrate the Retired Package: Replace retired package imports, options, credentials, and reporter settings with the current Azure Playwright APIs.

## Prompt Templates

### Create a Basic Azure Setup

```
Review my TypeScript Playwright project. Add the current Azure package, create a service configuration, and list required environment values.
```

### Configure Secure Authentication

```
Configure this Playwright project for Microsoft Entra ID. Choose between default and managed identity credentials based on the deployment environment.
```

### Integrate Azure Tests into CI

```
Add Azure-hosted Playwright tests to this CI workflow. Preserve least privilege, protect service values, retain failure artifacts, and explain required repository settings.
```

### Migrate and Tune a Large Suite

```
Migrate this project from the retired Azure Playwright package. Update APIs and reporters, then recommend worker, timeout, network, and artifact settings.
```

## Limitations

- Requires an Azure Playwright workspace, service URL, and appropriate Azure permissions.
- Examples target TypeScript and require supported Playwright package versions.
- Does not provision Azure resources or verify pricing, quotas, and regional capacity.
- Generated configuration still requires testing within the target repository and CI environment.

## Best Practices

- Use Microsoft Entra ID with explicit credentials instead of long-lived access tokens.
- Store service values in protected CI variables and grant only required workflow permissions.
- Validate worker counts, timeouts, artifacts, and reporter ordering in the target environment.

## Anti Patterns

- Do not embed Azure tokens, service URLs, or identity values in committed source files.
- Do not reuse retired package imports or options in new configurations.
- Do not maximize worker counts without checking suite isolation, quotas, and target capacity.

## Security Audit

- Audited at: 2026-07-23T21:41:29.407\+00:00
- Summary: All 50 static findings are false positives caused by Markdown code fences, inline code, documented pipeline syntax, or benign example URLs. The credential references use standard GitHub Actions secret interpolation without exposing values, and no prompt injection or credential exfiltration intent was found.

## Stats

- Views: 92
- Downloads: 7
- Favorites: 0
- Popularity score: 0