Prisma Repository Integration Tests with PostgreSQL TaskFlow - Full Stack Developer 2026
Why this layer must be real A Prisma repository exists specifically to encode persistence behavior. Its important risks are relation filters, tenant scoping, count queries, sort order, constraints and PostgreSQL behavior. Mocking Prisma cannot prove those things.
Dedicated test database lifecycle 1. create/reset dedicated TEST_DATABASE_URL 2. prisma migrate deploy 3. seed minimal scenario data 4. run repository integration tests 5. cleanup/reset 6. never point this command at development or production
Scoped query example • Seed Workspace A + User A membership + Task A.
• Seed Workspace B + Task B with no membership for User A.
• Call listScoped(userA).
• Assert Task A is returned and Task B never appears.
• Repeat with filtering/pagination/count so security scope and collection metadata are proven together.
Isolation strategy Start simple: transaction/reset or ordered deleteMany cleanup against a dedicated database. Parallelize integration tests only after data isolation is designed explicitly; speed is not worth cross-test contamination.
Prisma improves developer ergonomics, but migrations and generated queries still change a real relational database. You should be able to inspect both sides.
Restate the goal of “Prisma Repository Integration Tests with PostgreSQL” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: domain intent → Prisma Client → generated SQL → PostgreSQL → mapped result. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Vitest + integration + Playwright test suite with deterministic fixtures and CI-ready commands.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
const tasks = await prisma.task.findMany({
where: { workspaceId },
orderBy: [{ createdAt: "desc" }, { id: "desc" }],
take: 20,
});Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Verify connection string, host, port, SSL/pooler mode, network reachability, and which environment file the process loaded.
Read the generated SQL before applying it and compare the change against existing production-shaped data.
Without copying the final source, create a second small scenario that applies “Prisma Repository Integration Tests with PostgreSQL” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Run an API test through NestJS for validation/auth/error contract.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Mocking the thing the test is supposed to prove
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.