Originally forked from https://github.com/morintd/prismock. This library is awesome, and I felt it could use some modernization to work with newer versions of prisma and add support for client extensions. My current intention is to try to maintain this and stay up to speed with bug-fixes, contributions are welcome! The focus is ESM-first, so although both ESM and CJS exports are provided, I haven't personally tested the CJS functionality.
This is a mock for PrismaClient. It actually reads your schema.prisma and generate models based on it. For postgres it also offers a true in-memory database client by using PgLite.
It perfectly simulates Prisma's API and stores everything in-memory for fast, isolated, and retry-able unit tests.
It's heavily tested, by comparing the mocked query results with real results from prisma. Tested environments include MySQL, PostgreSQL and MongoDB.
This library can also be used as an in-memory implementation of Prisma, for reasons such as prototyping, but that's not its primary goal.
After setting up Prisma:
yarn
$ yarn add -D @pkgverse/prismocknpm
$ npm add --save-dev @pkgverse/prismock
bun
$ bun add -E -D @pkgverse/prismock
import { PrismaClient } from "${your_prisma_client_directory}"
import { getClient } from '@pkgverse/prismock';
// Pass in your PrismaClient class and the path to your schema
let mockedClient = await getClient({
prismaClient: PrismaClient,
schemaPath: "prisma/schema.prisma",
})
// Optionally apply your client extensions to the client
mockedClient = applyExtensions(mockedClient)That's it, prisma will be mocked in all your tests (tested with ViTest)
If you're using prisma with postgres, you can optionally choose to have the mocked prisma client use PgLite for more 'true-to-life' tests.
import { PrismaClient } from "${your_prisma_client_directory}"
import { getClient } from '@pkgverse/prismock';
let mockedClient = await getClient({
prismaClient: PrismaClient,
schemaPath: "prisma/schema.prisma",
usePgLite: true,
})
// Optionally apply your client extensions to the client
mockedClient = applyExtensions(mockedClient)The prisma client will execute everything as it normally would purely in-memory.
schemaPath. If that's not the case, this will most likely fail.
You can mock the PrismaClient directly in your test, or setupTests (Example):
import { vi } from "vitest"
vi.mock('@prisma/client', async () => {
const actual = await vi.importActual<typeof import("@prisma/client")>("@prisma/client")
const actualPrismock = await vi.importActual<typeof import("@pkgverse/prismock")>("@pkgverse/prismock")
return {
...actual,
PrismaClient: await actualPrismock.getClientClass({
prismaClient: actual.PrismaClient,
schemaPath: "prisma/schema.prisma",
}),
};
});You can get an instantiated prisma client and pass it wherever you need to
import { PrismaClient } from '${your_prisma_client_directory}';
import { getClient } from '@pkgverse/prismock';
const client = await getClient({
PrismaClient,
schemaPath: "prisma/schema.prisma",
});Then, you will be able to write your tests as if your app was using an in-memory Prisma client.
The prisma schema went through breaking changes going from v6 -> v7.
You can import from the v6 or v7 package subpaths depending on which major version of prisma you're on.
import { PrismaClient } from '${your_prisma_client_directory}';
import { getClient } from '@pkgverse/prismock/v7';
const client = await getClient({
PrismaClient,
schemaPath: "prisma/schema.prisma",
});See use with decimal.js.
Two additional functions are returned compared to the PrismaClient, getData, and reset.
const prismock = await getClient({...});
prismock.getData(); // { user: [] }const prismock = await getClient({...});
prismock.reset(); // State of prismock back to its original| Feature | State |
|---|---|
| findUnique | ✔ |
| findFirst | ✔ |
| findMany | ✔ |
| create | ✔ |
| createMany | ✔ |
| delete | ✔ |
| deleteMany | ✔ |
| update | ✔ |
| updateMany | ✔ |
| upsert | ✔ |
| count | ✔ |
| aggregate | ✔ |
| groupBy | 💬 note |
| Feature | State |
|---|---|
| distinct | ✔ |
| include | ✔ |
| where | ✔ |
| select | ✔ |
| orderBy (Partial) | ✔ |
| select + count | ⛔ |
| Feature | State |
|---|---|
| create | ✔ |
| createMany | ✔ |
| update | ✔ |
| updateMany | ✔ |
| connect | ✔ |
| connectOrCreate | ✔ |
| upsert | ✔ |
| set | ⛔ |
| disconnect | ⛔ |
| delete | ⛔ |
| Feature | State |
|---|---|
| equals | ✔ |
| gt | ✔ |
| gte | ✔ |
| lt | ✔ |
| lte | ✔ |
| not | ✔ |
| in | ✔ |
| notIn | ✔ |
| contains | ✔ |
| startWith | ✔ |
| endsWith | ✔ |
| AND | ✔ |
| OR | ✔ |
| NOT | ✔ |
| mode | ✔ |
| search | ⛔ |
| Feature | State |
|---|---|
| some | ✔ |
| every | ✔ |
| none | ✔ |
| is | ✔ |
| Feature | State |
|---|---|
| set | ⛔ |
| push | ✔ |
| Feature | State |
|---|---|
| has | ⛔ |
| hasEvery | ⛔ |
| hasSome | ⛔ |
| isEmpty | ⛔ |
| equals | ⛔ |
| Feature | State |
|---|---|
| increment | ✔ |
| decrement | ✔ |
| multiply | ✔ |
| divide | ✔ |
| set | ✔ |
| Feature | State |
|---|---|
| path | ⛔ |
| string_contains | ⛔ |
| string_starts_withn | ⛔ |
| string_ends_with | ⛔ |
| array_contains | ⛔ |
| array_starts_with | ⛔ |
| array_ends_with | ⛔ |
| Feature | State |
|---|---|
| @@id | ✔ |
| @default | ✔ |
| @relation | ✔ |
| @unique | ⛔ |
| @@unique | ✔ |
| @updatedAt | ⛔ |
| Feature | State |
|---|---|
| autoincrement() | ✔ |
| now() | ✔ |
| uuid() | ✔ |
| auto() | ✔ |
| cuid() | ✔ |
| dbgenerated | ⛔ |
| Feature | State |
|---|---|
| onDelete (SetNull, Cascade) | ✔ |
| onDelete (Restrict, NoAction, SetDefault)() | ⛔ |
| onUpdate | ⛔ |
Basic groupBy queries are supported, including having and orderBy. skip, take, and cursor are not yet supported.
- Complete supported features.
- Refactoring of update operation.
- Replace item formatting with function composition
- Restore test on
_countfor mongodb - Add custom client method for MongoDB (
$runCommandRaw,findRaw,aggregateRaw)
Inspired by prisma-mock.