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!

文件	最后提交记录	最后更新时间
.github	chore: properly call docker compose and reference jest config	2 年前
.husky	Update .husky/pre-commit Co-authored-by: Jay McDoniel <jmcdo29@gmail.com>	4 年前
.vscode	feat(app): convert to NestJS monorepo	6 年前
apps	chore: remove unused/erroneous prisma hooks	1 年前
public	feat(render): implements render example with fully working tests * style(docs): change badges to be spaced out in readme * feat(render): implements render example with fully working tests Implement E2E and unit tests for Handlebars rendering Nest application. Update all workflows to run test:cov instead of test fix #74	6 年前
tools	chore: upgrade nx to version 16	3 年前
.dockerignore	Dockerize (#601) * chore: moves to eslint and starts dockerization * fix(websocket): fix jest not exiting properly Because I was using `io.connect()` without a properport, socketIo was not properly disconnecting after the test. Now that I am useing `io.connect(await app.getUrl())` everything works just fine fix #14 * ci: starts dockerizing the e2e testing process I'm tired of seeing CRON failures so I'm also adding in the necessary service to the cron.yml for the moment. I'll get it all fixed in the future * test(typeorm): fixes up typeorm e2e tests with docker-compose * feat: removes typeorm-graphql-sample The TypeOrm-GraphQL-Sample project is removed as there is no need for two sample projects to use TypeORM. The point of the repository is to show how testing can be done with NestJS. As there is a fully working typeorm-sample project and a graphql-sample project, there is no need to combine the two. BREAKING CHANGE: removal of the typeorm-graphql-sample * feat(e2e): adds docker-compose for e2e tests There's still some bugs with how the microservices tests were implemented, I'll need to spend more time on that, but now the TypeORM test has an actual database to query and use. Mongo is next, but I want to get rid of the failing CRON test for now. * fix: fixes microservice tests	6 年前
.editorconfig	chore(mrm): add file configs using mrm Add in EditorConfig, Contributing.md, update prettier, jest in root directory and move several configs to package.json	7 年前
.eslintrc.js	chore: update eslint and igrate to pnpm	4 年前
.eslintrc.json	chore: update eslint and igrate to pnpm	4 年前
.gitignore	chore(deps): upgrade nx v15	3 年前
.npmrc	chore(deps): upgrade version nestjs v9 and others updated	4 年前
.prettierignore	chore: migrate to nx monorepo I'm moving over from a Nest monorepo to an [nx][1] monorepo to allow for easier development and more robust commands. The ability to use `npm run nx affected:test` to take care of all of the changed tests at once is incredibly useful. Also, it helps with running the projects locally via compiling with webpack, and generally has a better DX in my honest opinion. Plus, it can allow for a useful refactor pattern later, and better exposure to using Nx. closes #1222 [1]: https://nx.dev	4 年前
.prettierrc	chore(mrm): add file configs using mrm Add in EditorConfig, Contributing.md, update prettier, jest in root directory and move several configs to package.json	7 年前
CODE_OF_CONDUCT.md	chore: create code of conduct	7 年前
Contributing.md	chore: upgrade nx to version 16	3 年前
Dockerfile	Dockerize (#601) * chore: moves to eslint and starts dockerization * fix(websocket): fix jest not exiting properly Because I was using `io.connect()` without a properport, socketIo was not properly disconnecting after the test. Now that I am useing `io.connect(await app.getUrl())` everything works just fine fix #14 * ci: starts dockerizing the e2e testing process I'm tired of seeing CRON failures so I'm also adding in the necessary service to the cron.yml for the moment. I'll get it all fixed in the future * test(typeorm): fixes up typeorm e2e tests with docker-compose * feat: removes typeorm-graphql-sample The TypeOrm-GraphQL-Sample project is removed as there is no need for two sample projects to use TypeORM. The point of the repository is to show how testing can be done with NestJS. As there is a fully working typeorm-sample project and a graphql-sample project, there is no need to combine the two. BREAKING CHANGE: removal of the typeorm-graphql-sample * feat(e2e): adds docker-compose for e2e tests There's still some bugs with how the microservices tests were implemented, I'll need to spend more time on that, but now the TypeORM test has an actual database to query and use. Mongo is next, but I want to get rid of the failing CRON test for now. * fix: fixes microservice tests	6 年前
LICENSE	docs(): update LICENSE	4 年前
README.md	docs(): update readme	4 年前
commitlint.config.js	chore: set up first projects Set up the initial projects for a simple project, complex project, TypeORM project, and a MongoDB project. The simple project will be nothing more than a controller, a service, and a pipe. The complex project will be a few controllers, a few services, some interceptors, pipes, a filter or two, and maybe authentication. The TypeORM project will be focused on TypeORM usage and testing. The MongoDB project will be focused on MongoDB usage and testing.	7 年前
docker-compose.yml	chore(prisma-sample): setup postgres db for prisma e2e tests before running e2e tests, expose prisma postgres on different port than typeorm postgres	5 年前
jest.config.js	chore(): updated	3 年前
jest.e2e.js	chore(): update config jest e2e	3 年前
jest.preset.js	chore: upgrade nx to version 16	3 年前
migrations.json	chore: upgrade nx to version 16	3 年前
nest-cli.json	feat(prisma-sample): Add Prisma example	5 年前
nx.json	chore: upgrade nx to version 16	3 年前
package.json	chore: upgrade nest to v10 packages	3 年前
pnpm-lock.yaml	chore: update lockfile	1 年前
setupPrismaDatabase.sh	fix: set all commands to pnpm	4 年前
tsconfig.base.json	chore(): updated	3 年前
tsconfig.build.json	feat(app): convert to NestJS monorepo	6 年前
tsconfig.json	chore: migrate to nx monorepo I'm moving over from a Nest monorepo to an [nx][1] monorepo to allow for easier development and more robust commands. The ability to use `npm run nx affected:test` to take care of all of the changed tests at once is incredibly useful. Also, it helps with running the projects locally via compiling with webpack, and generally has a better DX in my honest opinion. Plus, it can allow for a useful refactor pattern later, and better exposure to using Nx. closes #1222 [1]: https://nx.dev	4 年前

自动翻译

持续集成测试

testing-nestjs

本项目旨在向社区展示NestJS的测试方法，包括单元测试、集成测试、端到端测试、管道、过滤器、拦截器、GraphQL、Mongo、TypeORM等！

项目结构

每个文件夹都是一个独立的、功能完整的Nest应用程序。克隆仓库后，您只需进入相应的文件夹，安装依赖项，然后进行测试！或者，您也可以在GitHub上查看测试，这也不是什么大问题。

动机

我注意到很多人在测试上遇到了困难，不知道如何使用Nest提供的工具进行测试。希望这个由社区驱动的测试仓库能帮助其他人更好地理解并掌握如何运行测试。

注意事项

这并非一定是Nest官方推荐的测试应用程序的方式，也不是在任何情况下唯一的方式。我将尽力展示不同的测试运行方法，但我很可能会遗漏某些特定的测试运行方式，比如特定的模拟方法等。再次强调，这是一个由社区维护的项目，不是官方文档的一部分。如果您发现了其他测试应用程序的方式，欢迎分享，但请不要认为这是唯一的方式。

运行项目

git clone https://github.com/jmcdo29/testing-nestjs.git
cd testing-nestjs/<文件夹名>
npm install 或 yarn add 或 pnpm install
npm run test 或 yarn test 或 pnpm test

贡献

我遗漏了您最喜欢的主题吗？还是错过了您绝对需要测试的内容？那就提出一个议题，或者更好的是，一个PR!我会乐意查看任何主题，并尝试帮助您弄清楚如何测试，或者合并任何能提升仓库价值的PR。如果您提交了PR，请附上测试覆盖率的截图，以便他人了解测试运行情况。complex-sample 分支有一个很好的示例。