The 22 ORM commands have no end-to-end test through the shipped prisma binary

packages/cli/tests/e2e-coverage.test.ts excuses all 22 ORM commands (contract *, db *, migration *, ...) with ORM_FAMILY_REASON: "no management API involved. Real e2e lives in prisma/prisma". That reasoning was rejected on 2026-08-13: the ORM repository's suite passed throughout while the assembled prisma binary exited 2 on ORM commands, because those tests call the commands directly, not through the binary. orm-mount.test.ts covers only migration list.

Write happy-path e2e tests that run the shipped prisma binary against a local Postgres, and remove the 22 exclusions.

Recorded in the prisma-cli-v8 project ledger, which is being deleted at close-out:

prisma-cli/.drive/projects/prisma-cli-v8/deferred.md

Line 120 in 4356b36

    
           - **The e2e coverage convention excludes all 22 ORM commands on reasoning #171 disproved.** `tests/e2e-coverage.test.ts` excuses them with "Real e2e lives in prisma/prisma (R7); the shell proves composition in orm-mount.test.ts (R8)." prisma/prisma's suite passed throughout the presentations change while the assembled binary exited 2, and `orm-mount.test.ts` proves composition for exactly one command, `migration list`, not per family. The operator's ruling (2026-08-13) is that every mounted command needs a happy path in this repo, precisely because the product repos cannot reproduce the assembled CLI. The exclusion should become a backlog entry once the first item above is fixed and the commands can run at all.

🤖 Generated with Claude Code

Navigation Menu

Repository navigation

The 22 ORM commands have no end-to-end test through the shipped prisma binary #310

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

The 22 ORM commands have no end-to-end test through the shipped prisma binary #310

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions