What is test coverage and what percentage should you aim for?
Coverage measures what percentage of code is tested (line, branch, function, statement). Run with jest --coverage. Aim for 80%+ overall, but focus on critical paths. 100% coverage doesn't mean bug-free focus on meaningful tests, not just coverage numbers.
Verify This Answer
Cross-check this information using these trusted sources:
More FAQs in Node.js Testing Interview Questions Jest, Supertest, and Testing Best Practices
Unit tests (individual functions in isolation), integration tests (components working together), end-to-end tests (full application flow), performance tests (speed and scalability), and security tests (vulnerabilities). Unit tests are fast and numerous, E2E tests are slow and few.
Use Jest as the test runner and Supertest for HTTP requests. Import the Express app, use request(app).post('/api/signup').send({...}), and assert on the response status, body, and headers. Supertest doesn't require the server to be running it calls the Express app directly.
Use mongodb-memory-server to create an in-memory MongoDB instance. Connect in beforeAll, clean collections in afterEach (deleteMany({})), and disconnect in afterAll. This ensures tests are isolated, fast, and don't affect your development database.
Still have questions?
Browse all our FAQs or reach out to our support team