- Analyzing Angular 2 error messages
- Identifying the causes of common error messages
- Preventing common errors with custom error handling
- Analyzing testing reports
- Reviewing common testing report errors and their likely causes
Skill Level Intermediate
- [Derek] Missing dependencies, undefined variables, and poorly formatted data can all crash a web application. The faster you identify these errors, the faster your application can get back up and running. Better yet, you can prevent many of these errors in the first place by testing your code before the errors happen. My name is Derek Peruo, and I've worked with web technologies for almost 10 years. In this course, I'll guide you through the process of testing and debugging Angular 2 applications in the browser as well as tips and tricks for managing tests and errors as your application grows in size and complexity.
We'll look at an overview of all the testing and debugging options, as well as a breakdown of common error messages and their likely causes. Later in the course, we'll dive into writing custom error handlers to make working with errors easier as your application grows. Testing and debugging is one of my favorite topics for Angular applications, so let's get started.
Q: This course was updated on 10/30/2018. What changed?
A: The following topics were updated: common Angular 2 errors—including dependency injection errors—and testing Angular 2 apps.