fixtures
Skill1 starsChanged 3 months agoMITView on GitHub
Use when wiring a page object into dependency injection, sharing setup/teardown across tests, or adding a new fixture category. Defines the fixture layering and the single import point.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- dev-okinawa/ai-sdlctheir own version, first seen Nov 16, 2026
- idavidov13/agentic-playwrighttheir own version, first seen Nov 8, 2026
- gridaco/gridatheir own version, first seen Oct 8, 2026
- efficience-it/claude-skills-phptheir own version, first seen Mar 31, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- gridaco/grida★ 2.7ksame name
- idavidov13/agentic-playwright★ 294same name
- efficience-it/claude-skills-php★ 1same name
- dev-okinawa/ai-sdlc★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- ai-native-workflowSkill
- api-testingSkill
- bootstrapSkill
- common-tasksSkill
- configSkill
- data-strategySkill
- debuggingSkill
- enumsSkill
- page-objectsSkill
- salesforce-authSkill
- salesforce-dataSkill
- salesforce-locatorsSkill
- salesforce-metadata-contractSkill
- salesforce-personasSkill
- salesforceSkill
- salesforce-waitsSkill
- security-testingSkill
- selectorsSkill
- test-standardsSkill
- type-safetySkill
- wait-strategySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Add await productsPage.goto() before use ONLY if every consumer starts on that page.
- Very specific: line 44
Promotion rule: create a helper fixture only when the same setup/teardown is reused across 3+ files.
- Distinctive: line 53
Don't put assertions in fixtures.
- Distinctive: line 54
Don't share mutable state between tests via fixtures (breaks parallelism/independence).
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fixtures
Fixtures give auto-init and auto-cleanup. Three layers, merged into one import point.
fixtures/
├── api/ api-fixture.ts (the `api` client) + api-request.ts + schemas/
├── pom/ page-object-fixture.ts (page object DI)
├── helper/ helper-fixture.ts (setup/teardown lifecycle)
└── test-options.ts ← mergeTests(...) — the ONLY thing specs importEvery spec: import { test, expect } from '<...>/fixtures/test-options';
Importing test from @playwright/test directly is a bug — it bypasses all custom fixtures.
Page-object fixtures
Register each page object once in pom/page-object-fixture.ts:
productsPage: async ({ page }, use) => { await use(new ProductsPage(page)); },Add await productsPage.goto() before use ONLY if every consumer starts on that page. Tests then
destructure { productsPage } — never new.
Helper fixtures (setup/teardown)
Setup → await use(data) → teardown. The teardown half runs even on failure, so data never leaks.
seededUser: async ({ request }, use) => {
const user = await create(...); // setup
await use(user);
await delete(user.id).catch(() => {}); // teardown, best-effort
},Promotion rule: create a helper fixture only when the same setup/teardown is reused across 3+
files. Otherwise call api directly in the test — don't over-fixture.
New category
base.extend<MyFixtures>({...}) in its own file, then add it to the mergeTests(...) in test-options.ts.
Don't
- Don't put assertions in fixtures.
- Don't share mutable state between tests via fixtures (breaks parallelism/independence).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

