Code coverage is the process of monitoring how much code is covered by a unit test. Code coverage tools can monitor anything from statements and lines to functions and branches. Target thresholds are set in the configuration and coverage reports are output to the command line.
So, like I said, code coverage…with library you should…probably just do 100% code coverage,…there's not really any reason not to,…and so because normally it's pretty easy,…the problems are really well defined…and it'll save you from breaking stuff…when you're making changes…or somebody makes a port crash or something.…So,…what code coverage is is it basically…consists of four metrics,…lines, branches, functions and now I can't remember.…
Anybody know what the last one is?…My brain just decided to give up.…Statements.…So,…basically all that code coverage tells you…is that this line ran…or this if statement was evaluated to true…
Note: This course was created by Frontend Masters. It was originally released on 08/09/2016. We're pleased to host this training in our library.
- Creating an open-source library
- Linting and testing
- Code coverage
- Installing and configuring Babel
- Peer dependencies
- Forking and renaming
- Continuous integration and automating releases
Skill Level Intermediate
1. Creating an Open-Source Library
2. Linting and Testing
3. Git Hooks, Babel, and Webpack
4. Continuous Integration and Automating Releases
- 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.