familynido/web/familynido-web/e2e/fixtures.ts
Pablo Fernández a308041d59 Initial commit
FamilyNido — a self-hosted PWA for a single household: shared calendar,
chores, meals, school agenda, health records and a family wall. One
instance per family, deployable with `docker compose` on any home
server.

Stack: .NET 10 (ASP.NET Core Minimal APIs) + EF Core 10 + PostgreSQL 16
on the backend, Angular 21 (standalone, signals, zoneless) + Tailwind
CSS v4 on the frontend, SignalR for realtime, optional OIDC alongside
local credentials, integration via a versioned `/api/v1/**` public API.

See README.md for the module overview and how to deploy.
2026-05-13 00:23:14 +02:00

26 lines
877 B
TypeScript

import { test as base, type Page } from '@playwright/test';
/**
* Playwright `test` extended with a `pageB` fixture that opens a second
* browser context loaded with tester B's storage state. Use this in any
* spec that needs two distinct authenticated identities — e.g. user A
* creates a task, user B completes it, user A verifies the result.
*
* Single-user specs should keep importing `test` from `@playwright/test`
* directly; only opt-in here when the second context is actually needed.
*/
export const test = base.extend<{ pageB: Page }>({
pageB: async ({ browser }, use) => {
const context = await browser.newContext({
storageState: 'e2e/.auth/state-b.json',
});
const page = await context.newPage();
try {
await use(page);
} finally {
await context.close();
}
},
});
export { expect } from '@playwright/test';