From the course: Node.js: Testing and Code Quality
Unlock the full course today
Join today to access over 24,400 courses taught by industry experts.
Why code coverage matters
From the course: Node.js: Testing and Code Quality
Why code coverage matters
- Knowing about problems within a specific file or component is a good thing. But that's only part of the picture Having an actionable perspective of the entire code base is a key to success. In this chapter, we're going to extend what we've learned so far about testing and detecting suspicious code. We'll start with a concept of code coverage and why it's important. We'll generate a report about the restaurant reservation applications code coverage using industry standard tools. Next, we'll broaden our testing techniques with functional testing, which will extend the existing the report. We'll ask the emperor has no close question. What could possibly go wrong when you have 100% test coverage on a code base? Finally, we'll learn about ways to automate code quality measurement on an ongoing basis. Code coverage sure sounds important, but what is it? Code coverage which is the measure of how much code is executed in a…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
-
-
-
(Locked)
Why code coverage matters5m 22s
-
(Locked)
Measuring code coverage with Jest5m 54s
-
(Locked)
Functional testing with Jest4m 1s
-
(Locked)
Test doubles and Express apps5m 53s
-
(Locked)
Form submissions with SuperTest6m 9s
-
(Locked)
Fallacies of 100% test coverage4m 19s
-
(Locked)
Coverage with continuous integration4m 34s
-
(Locked)
Challenge: Isolate routes for faster tests39s
-
(Locked)
Solution: Isolate routes for faster tests9m 27s
-
(Locked)
-