# extendify/3.1.1/tests/playwright/fixtures.ts

Extendify, version 3.1.1. 13 lines.

- Page: https://pluginprobe.com/plugins/extendify/3.1.1/code/tests/playwright/fixtures.ts
- Raw: https://pluginprobe.com/plugins/extendify/3.1.1/raw/tests/playwright/fixtures.ts
- Modified: 2026-06-11T18:37:12+00:00

Line numbers below start at 1. Link to a line or a range by appending a fragment to the
page URL, for example `https://pluginprobe.com/plugins/extendify/3.1.1/code/tests/playwright/fixtures.ts#L10-L20`.

```typescript
// Specs declare state via their nearest blueprint.json (defineWpConfigConsts +
// setSiteOptions + updateUserMeta steps). Keep this file as a thin re-export so
// spec imports stay stable as helpers come and go.
//
// API mocking convention: per-spec `page.route()` inside the spec's own
// `beforeEach` (or per-test, where one branch needs a different stub). No
// shared mock fixture, no cassette layer — most ported specs assert on UI
// shape, not response data, so they hit real APIs by design and match the
// Cypress posture for the same scope. The only spec that depends on a stubbed
// response today is `Draft/completions/completions.spec.ts`; copy that shape
// when a new spec needs to assert against a specific payload.
export { expect, test } from '@wordpress/e2e-test-utils-playwright';

```