Book Image

Accelerating Angular Development with Ivy

By : Lars Gyrup Brink Nielsen, Mateus Carniatto, Jacob Andresen
Book Image

Accelerating Angular Development with Ivy

By: Lars Gyrup Brink Nielsen, Mateus Carniatto, Jacob Andresen

Overview of this book

Angular Ivy is the latest rendering engine and compiler introduced in Angular. Ivy helps frontend developers to make their Angular applications faster, better optimized, and more robust. This easy-to-follow guide will help you get to grips with the new features of Angular Ivy and show you how to migrate your Angular apps from View Engine to Ivy. You'll begin by learning about the most popular features of Angular Ivy with the help of simple stand-alone examples and realize its capabilities by working on a real-world application project. You'll then discover strategies to improve your developer workflow through new debugging APIs, testing APIs, and configurations that support higher code quality and productive development features. Throughout the book, you'll explore essential components of Angular, such as Angular Component Dev Kit (CDK), Ahead-of-time (AOT) compilation, and Angular command line interface (CLI). Finally, you'll gain a clear understanding of these components along with Angular Ivy which will help you update your Angular applications with modern features. By the end of this Angular Ivy book, you will learn about the core features of Angular Ivy, discover how to migrate your Angular View Engine application, and find out how to set up a high-quality Angular Ivy project.
Table of Contents (14 chapters)

Testing as a user with component harnesses

The Angular CDK's API for authoring and using component testing harnesses is a fresh approach with the test-as-a-user philosophy in mind. Each component or related set of components can have a component harness for tests. A component harness is a testing API for interacting with those components that can be used in unit, integration, and end-to-end tests.

Component testing harnesses internally rely only on a single selector for the component they wrap. Library authors can publish component harnesses for their Angular components. In this way, their consumers' tests, which depend on the library's components, will not have dependencies on the DOM structure except for that one selector, which the library authors are able to change if needed.

This is exactly what the Angular Components team do for Angular CDK and Angular Material. They release and maintain component harnesses for all their Angular components.

Harness environments...