@playwright/test 1.x

Use @playwright/test 1.x correctly: distinguish its runner-managed test API from standalone imports, configure projects, define fixtures, and compose test/assertion extensions.

For

@playwright/test@1.63.0

Verified

2026-09-07, 5 examples executed

Package

@modootoday/pmcp-playwright-test@1.0.0

What it covers

• Scope and package shape
• The common shape mistake
• Plain-script surface
• Generic `expect`
• Configuration with `defineConfig`
• Device descriptors
• Custom fixtures with `test.extend`
• Combining test and assertion extensions
• Runner-only operations
• What this skill does not cover

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import { expect } from '@playwright/test';

const value = { status: 'ready', count: 2 };
expect(value.status).toBe('ready');
expect(value.count).toBeGreaterThan(1);
expect(value).toEqual({ status: 'ready', count: 2 });

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-playwright-test

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.