Learn how the files for the start, progress, and result of the Node.js application cleanup are organized in this testing and code quality course.
- [Instructor] If you have access to the exercise files for this course, you can download them to your desktop. We'll start with the complete but problematic Node.js restaurant reservation system. Throughout we'll make incremental changes to clean up and fix the application. The exercise file structure will reflect the course progress. There are three folders, the first folder is called Nadia which contains the Nadia's Restaurant application itself. We'll set it up in the next video. The second folder is progress which contains snapshots of the application throughout the course.
Progress is organized into sub folders by chapter and video. For example, the result of chapter two, video one will be in a sub folder named 02_01. Each video sub folder has two sub folders, begin and end which contain the respective begin and end states of the code base. The last folder, solutions, contains only the files that are changing in a particular video. It will also be organized into sub folders by chapter and video.
If you're viewing this course on a mobile device, a set-top device or your membership doesn't provide access to these exercise files, don't worry, the exercise files are a convenient and recommended way to learn but they're not a requirement. Please, continue to follow along.
- 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
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.