Learn how to create a coding standard, including best practices for involving a team. Then learn how linters can force coding conventions automatically to improve code quality.
- [Instructor] Now that we know what a coding standard is,…let's go through the steps for creating and enforcing one.…The process for creating a coding standard is iterative,…much like specifying software.…First, determine what coding conventions…are available and fit your project or organization.…Out of what's available, decide what has the most positive…impact on the quality of your code base and morale.…Some rules help developers,…while others may annoy and be needlessly strict.…Experiment with what's out there…to find what works and what doesn't.…
When you've made a choice,…briefly document to the justification…of why you've chosen to use or not use a particular rule.…Less is more, so try for a maximum of one sentence.…Once the rules have been defined,…create the configurations for any software you're using.…We're going to be discussing…how to do this later in the course.…Finally, revisit the rules on a regular basis…to make sure they're still logical.…Some may work, others won't,…and new ones might be available.…
- 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.