Chapter 8. Testing Node
Testing in the real world is generally about finding what’s wrong with something. When it comes to code, testing is about finding what’s right. It’s the guarantee that something is working.
Untested code is simply dangerous. Efficient and scalable code is well-tested. Testing is not only about making sure the code is doing what it is supposed to do; it’s also about making sure the code continues to do what it is supposed to do after any changes in the code, its environment, and its use patterns. Testing is about writing high-quality code and catching potential problems as early as possible.
Regular testing of code keeps it healthy and makes maintaining it easier. It also increases the confidence of its maintainers to make changes. Making changes to untested code is a recipe for disaster. A new feature in module X might break other features in module Y. You can’t keep the dependencies in your head. You can’t test all the code manually every time there is a change. There is no way around it. You have to write code to test your code, and yes, your testing code might have problems too. Tests might introduce false negatives and false positives. That’s why it’s extremely important to get the tests right. That is what this chapter is all about.
Assertions and Runners
A test in Node is a set of assertions. To execute the tests, you need a test runner. Node has built-in modules for both. Here’s a simple test for the map method on arrays:
importtestfrom'node:test' ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access