100% test coverage does not mean that software is perfect or bug free, nor is it a substitute for peer code review. Discover the perils of pursuing the elusive 100%.
- [Instructor] An often held but mistaken belief is…that 100% test coverage means that software is perfect.…Should you try to get 100% test coverage?…Yes, but with a huge caveat.…100% test coverage does not mean…that your application is bug free.…Especially if you designed your tests…to conform to the buggy application.…100% test coverage does not mean…that you wrote good tests,…it just means that your tests didn't fail.…100% test coverage could mean…that your tests were not properly isolated…so unexpected behavior could still occur.…
A user of the system can't use 100% test coverage…because it does not deliver new functionality.…Finally, 100% test coverage is not a substitute…for peer code review.…Okay, so what does this 100% test coverage look like?…Rather than dragging you…through writing a number of additional tests,…I've gone ahead and done the work already.…If you really want to learn,…try to get to 100% yourself.…Either way, a solution is available in the exercise files.…
Switch to your desktop.…From the desktop open up the Exercise Files.…
- What is code quality?
- Testing and code quality fundamentals
- Coding conventions and standards
- Creating and enforcing coding standards
- Unit, integration, and functional testing
- Test-driven development test specificatons
- Behavior-driven development test specifications
- Finding errors with linting
- Extending an ESLint shareable config
- Validating correctness with unit testing
- Replacing and inspecting with stubs, spies, and mocks
- Code coverage and why it matters
- Coverage with continuous integration
Skill Level Intermediate
Node.js: Build Your First Microservicewith Daniel Khan2h 9m Intermediate
Building APIs Using Hapi in Node.jswith Kirsten Hunter2h 23m Intermediate
Node.js: Extend and Maintain Applicationswith Daniel Khan3h 35m Intermediate
1. Testing and Code Quality Fundamentals
2. Finding Errors with Linting
3. Validating Correctness with Unit Testing
4. Replacing and Inspecting with Stubs, Spies, and Mocks
5. Reporting on Your Entire Codebase
Where to go from here?3m 46s
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.