cspell VS supertest

CSpell is a great spell checker for code. It can be added as a source to null-ls. However, a lot of features are missing when it's used from null-ls, for instance the ability to ignore certain paths. According to this comment in a null-ls thread cspell would need its own companion plugin.

I use cspell CLI to test for spelling errors at build time so that spelling errors cannot get committed. It's very easy to automate to avoid introducing errors. I don't know of an offline library to check for grammar though.

Spell check

Are this.state.representative and this.respresentative supposed to be the same thing? First off, they are misspelled, second, not the same property. Highly recommend at least using a code spell checker cspell and VS Code - Code Spell Checker if you aren't going to use TypeScript or ESLint.

You could definitely use a spellchecker. cspell is a great programatic spellchecker that you can add to your commit or build validations to enforce that things are spelled correctly.

- cspell: https://github.com/streetsidesoftware/cspell/tree/main/packages/cspell

Also, it's response not responce. Highly recommend using the Code Spellchecker plugin for VS Code and/or the cspell cli for spellchecking.

Supertest is quite popular and easy to use test tool, you can do integration and E2E test as well, you just need to pass it the server instance or a string to make a request and assert over the response.

If the latter, there are a bunch of different options for writing automated tests. One popular way is using Jest to run your tests. If you're trying to test the backend end-to-end flow, you could use Supertest to make requests and assert on the responses.

I did something similar with a full stack Typescript project, using supertest and node-fetch. It was nice.

Unit, Integration and E2E tests using Jest and Supertest

This is why integration tests > unit tests. I really hate mocking and I never bother testing individual units that don't affect how users use my app and code. In your case, I'd just use something like supertest to test this functionality e2e.

Yes, but when every function handler is separate from the router, then you can use node-mocks-http to test each handler, to test the router is simpler to use supertest to write integration tests, for E2E tests I personally recommend [pactum](pactumjs.github.io/)

Simple booking api attempt with Typescript, Express, TypeORM and Postgres. Testing with Jest & Supertest.

In a Node.js application, writing API tests is a good start. They provide more coverage than unit testing. You can use frameworks like Supertest, Jest, or any other library that provides a high-level abstraction for testing APIs.

supertest npm package that helps test HTTP

If you want to write integration tests - https://jestjs.io - https://github.com/visionmedia/supertest