[FAILING TEST] Unit testing a NestJS Service that consumes a TypeORM Repository about testing-nestjs HOT 6 CLOSED

What's the reason for module.createNestApplication in this unit test?

from testing-nestjs.

It was paving the way for future tests, which ended up getting broken out into an integration spec file.

I think the @golevelup/nestjs-testing module is just broken. It is at v0.1.2, and I just couldn't get it working. I finally resorted to creating very basic jest.fn() based mocks, which I then mockedResolvedValues for on a test-by-test case basis, and that seemed to work.

from testing-nestjs.

Gotcha. What if you use @golevelup/ts-jest (same package but new name and updates). If it still has problems could you provide a reproduction so I can take a deeper look?

from testing-nestjs.

Sure, I'll give it a whirl today.

from testing-nestjs.

So, in the long run, we decided we didn't necessarily need the @golevelup stuff. At least, not the testing stuff (we use other packages from them). The testing stuff just doesn't seem to be ready, and isn't even listed in their repos, so we decided to just mock things manually (which turned out to be easier than it seemed at first.)

from testing-nestjs.

The testing package is under the golevelup/nestjs repository. Either way, glad you got something that worked for you. Closing the issue out.

from testing-nestjs.