Learn about achievable and reasonable testing and code quality goals, such as metrics, timelines, team collaboration, and avoiding being pedantic.
- (Instructor) We've been discussing…theory and practice of testing and code quality.…How does that apply to what you're working on?…Let's admit the truth to ourselves.…There's no such thing as a perfect code base.…It's okay to say that because software…that we're working on is always changing.…Improvement is always an option…and I'd like to give you some ways to make that happen.…When improving an existing code base,…start off by setting achievable and reasonable goals.…Documenting every single function…and updating every package in an afternoon?…Not going to happen.…
Part of the goals should include metrics.…An example goal is 70% code coverage…on a particular component.…So that a project doesn't drag on forever,…have a timeline that you can work towards.…It can be as easy as by Friday or a multi-step process.…Do some research into how you'd like…to improve based on your needs.…This might include tooling or different approaches.…Finally, write a plan.…It doesn't have to be long.…Just state what you want to do and how.…
- 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.