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)

Creating a component harness

Let's imagine that we want to expose our Video component so that it can be integrated with other applications. Here, it would make sense to write a test harness for it – but how should we structure it? Our example of displaying YouTube videos using a YouTube Player component inside a Video component, which will be inside a Course component, turns out to be difficult to test using a "test as a user" approach in the DOM directly. So, let's take a layered approach here.

When constructing a component, we should strive to only have a single reference point – the DOM – for each page. Taking a layered approach, we start the test from the Course component, which knows about the Video component, which, in turn, knows about the YouTube Player component. By doing this, we can test from the Course component by exposing the Video harness that encapsulates the workspace-video selector as a Page Object for each of the instances...