Learn how continuous integration, which executes tasks on your code upon changes to a central repository, can report errors and coverage to developers to improve code quality. Discover services that can run continuous integration workflows, including Jenkins, CircleCI, and Travis CI.
- [Instructor] Code coverage can be reported automatically…with a technique called continuous integration.…What's that?…Continuous integration is a technique…for continually executing tasks on your code.…When code is merged to a central repository,…like pushing a change to a GIT server,…automated builds can run and tests can be executed.…For example, unit tests and coverage reports,…lending tasks to check for suspicious code,…and functional testing can be run automatically.…
The results can be used to report problems immediately…to a developer, warning about potential issues…with their changes.…The end result is an improvement in software quality…assuming the feedback is addressed.…There are a number of options for open-source…continuous integration tools that you can host yourself.…Each of the following are extensible using…plugins and configuration and, as a result,…are flexible for many different use cases.…I'll discuss each example in more detail.…The examples include Buildbot,…Jenkins, and Strider CD.…
Let's start with Buildbot.…
- 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
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.