Start-up times for Prisma are totally fine for production, but crazy slow for tests. It’s adding about 20-30 seconds or more per test suite as the test starts up Prisma. Since I have about a hundred test suites, this is a lot of extra time. I used to be able to run our test suite in a minute or two, but now it is closer to 15 minutes. Is there a way to launch the Prisma engine as a separate process? I’d love to launch it via docker and just point my runtime clients at the engine process. Is this possible? It would also be helpful to limit the

Launching Prisma (and its engine) itself is super fast usually, thing of ms. What takes time depending on your setup is creating the connection to your database. And how often that happens is based on your test setup. You can totally reuse the same Prisma Client with the same connection across tests.