PluginProbe
Extendify / 3.1.0
Extendify v3.1.0
3.2.1 3.2.0 3.1.6 3.1.5 3.1.4 3.1.3 3.1.2 3.1.1 3.1.0 3.0.6 3.0.5 3.0.4 trunk 0.1.0 0.10.0 0.10.1 0.10.2 0.11.0 0.11.1 0.2.0 0.3.0 0.3.1 0.4.0 0.5.0 0.6.0 All 127 releases
extendify / tests / playwright / fixtures.ts

fixtures.ts in Extendify 3.1.0, at tests/playwright/fixtures.ts

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