testing

Assert values the code transformed, side effects like specific Prisma where clauses or log calls, or structural wrapping such as response envelopes. If the only possible assertion is the raw mock return value, treat it as a suspected code bug instead of shipping a vacuous test.

Mock withAuth and withAdminAuth from lib/auth/guards as identity functions and mock the prisma client methods with vi.mock. Then call the route handler directly with a NextRequest and a stubbed session, and assert transformations like stripped sensitive fields.

Treat the code as wrong when behavior contradicts documented contracts, docstrings, or Zod schemas, then write the failing test with correct expectations and flag it with a BUG comment. Fix the test when you assumed a wrong return shape, mocked incorrectly, or asserted an implementation detail.

Yes, component tests use React Testing Library with userEvent and assert behavior such as onSubmit being called with form values, not styling or implementation details. Templates cover forms, loading states, validation errors, and mocking the Next.js router and auth client.

The global tests/setup.ts mocks several internal modules, so dedicated tests of those modules silently exercise the stub. Add vi.unmock for the module under test at the top of the file, before dependency mocks and imports, to run the real implementation.

Inner callbacks like onConnect and node drag handlers are unreachable under a static @xyflow/react mock, capping function coverage around 55-65 percent. Focus tests on effects, save and publish handlers, dialog side effects, and conditional renders instead of chasing full function coverage.