Repository files navigation

A repository to show off to the community methods of testing NestJS including Unit Tests, Integration Tests, E2E Tests, pipes, filters, interceptors, GraphQL, Mongo, TypeORM, and more!

Each folder is a fully functional Nest application on its own. All you need to do after cloning the repository is move into the folder, install the dependencies, and test! Or you could just, you know, look at the test on GitHub too, no big deal.

I've noticed a lot of people seem to get stuck on testing, and how to do it using the utilities given to us by Nest. Hopefully with a community driven repository of tests it will help others get a better understanding and feel for how to get tests running.

This is not necessarily the Nest canonical way to test an application, nor is it the only way in any scenario. I will do my best to show different ways to run tests, but I will more than likely miss certain ways of running the tests, whether it is mocking in a specific way or otherwise. Again, this is a community maintained project and not a part of the official documentation. If you find other ways to test applications, great, I'd love to see them, but please do not think this is the only way.

1. git clone https://github.com/jmcdo29/testing-nestjs.git
2. cd testing-nestjs/<folderName>
3. npm install ORyarn add
4. npm run test ORyarn test

Did I miss yourfavorite topic? Did I miss out on something you absolutelyneed tested? Well thenopen an issue, or better yet,a pull request! I'll be happy to look over any topics and try to help figure out how to test them or to merge any PRs that add to the value of the repository. If you do end up making a pull request, please add a screenshot of the test coverage so others can see how well the tests run. Thecomplex-sample branch has a good example.

The change log can be found on theReleases page.

Jay McDoniel andcontributors. Thanks to everyone who's helping with this effort!

MIT License, see the includedLicense.md file.