Tests don't run queries

[tradical-allstripes]

Hello Prisma community!

I'm currently trying to write some integration tests that rely on an actual Prisma database, and running into some issues.

First question:
Do you think that using an actual DB is the way to go for this, or is something along the lines of mocking a better idea? I saw prisma-test-utils, but it seemed really strange...I couldn't find many usages of it, and absolutely no usages of the code it generates in GitHub. There were fewer total usages of the text prisma-test-utils in GitHub than there are stars on the repo! LMK if someone knows more about what's going on here.

Second question:
The issue I'm encountering now is that Prisma is straight up not running the queries in tests, but does not fail or error out in any way. When I rely on lazy connection, providing an invalid DB URL does not even cause it to break (adding a call to $connect causes it to fail in that specific case, as expected, but queries still do not run when given the correct DB URL). I have turned on query logging, but nothing prints outside of my console.log statements. Just to be sure, I've also been checking the actual table with psql after every run; always 0 rows. Here is a version of my prototype test code that has confidential information removed:

import { PrismaClient } from '@prisma/client'

// Neither of these do anything. They don't even break if I make the DB URL incorrect

describe('<redacted>Resolver', () => {
  const prisma = new PrismaClient({ log: ['query'] })

  beforeAll(async () => {
    await prisma.$connect()
  })

  afterAll(async () => {
    await prisma.$disconnect()
  })
  test('test create', () => {
    console.log(`CREATE: ${JSON.stringify(prisma.<redacted>.create({
      data: {
        objectId: 'test',
      },
    }))}`)
  })

  test('test find many', async () => {
    console.log(`RESULT: ${JSON.stringify(prisma.<redacted>.findMany({}))}`)
  })
})

Here is the output:

  console.log
    CREATE: {}

      at Object.<anonymous> (src/__tests__/resolvers/<redacted>Resolver.test.ts:16:13)

  console.log
    RESULT: {}

      at src/__tests__/resolvers/<redacted>Resolver.test.ts:24:13

Here is my datasource block in schema.prisma:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

Lastly, here is the DATABASE_URL field in my .env file:

DATABASE_URL="postgresql://tradical@localhost:5433/api_tests"

Note that I have tried all sorts of restarting and reinstalling node_modules

[janpio]

I saw prisma-test-utils, but it seemed really strange...I couldn't find many usages of it, and absolutely no usages of the code it generates in GitHub. There were fewer total usages of the text prisma-test-utils in GitHub than there are stars on the repo! LMK if someone knows more about what's going on here.

Those were utils to test Prisma - so you are correct that this is very strange in the context you were looking. You made the right choice to ignore it.

[janpio]

The issue I'm encountering now is that Prisma is straight up not running the queries in tests, but does not fail or error out in any way.

Prisma queries are async and need to be awaited. Right now you are not doing that before logging the results - which at that point in time do not exist. Just putting the queries like this probably does not even start them. If you sprinkle in a few await or .then() the queries should actually be executed.

[tradical-allstripes]

Oooooh interesting, I'll give it a try. Thank you for the prompt reply!

Now my only question is "why didn't TS warn me about this?"

[tradical-allstripes]

For posterity, I can confirm that @janpio's suggestion works