xforge-testing

Use Vitest for a component's rendered output, props, variants, and accessibility roles, placed next to the component. Use Playwright only for real-browser concerns like navigation, server responses, layout, and focus across a page, since it is roughly 100x slower.

Use @testing-library/user-event instead of fireEvent. Call userEvent.setup() before render, then await each method such as user.click(screen.getByRole("button")). Under React 19 with RTL 16, act is handled automatically.

No. Vite 8 supports resolve.tsconfigPaths natively, which makes imports like @/app/page resolve under test. Adding the vite-tsconfig-paths plugin is a mistaken re-addition, not missing wiring.

The reuseExistingServer option points the suite at whatever already listens on the e2e port, which may be a stale server serving a different app. Check the port with curl or netstat before believing the failure; the app itself is usually healthy.

Prefer getByRole first, since it asserts the accessibility tree, followed by getByLabelText and getByText. getByTestId is a last-resort escape hatch that requires a justifying comment, and container.querySelector should be avoided entirely.

Mock the @/features/<domain>/actions module because server actions import server-only code that throws under jsdom. Declare mock functions inside vi.hoisted(() => ({...})), since a plain const is in its temporal dead zone when the hoisted factory runs.