book

Testing Angular Applications

by Corinna Coen, Jesse Palmer, Corinna Cohn, Craig Nishina, Michael Giambalvo

January 2019

Intermediate to advanced

240 pages

5h 59m

English

Manning Publications

Read now

Unlock full access

Who should read this bookHow this book is organized: a roadmapAbout the code Book forum
1.1 Angular testing overview1.2 Getting friendly with TypeScript1.3 A closer look at test types1.3.1 Unit tests1.3.2 E2E tests1.3.3 Unit tests vs. E2E testsSummary

2.1 Writing tests using Jasmine2.1.1 Writing basic tests2.2 Testing classes2.2.1 Adding the rest of the testsSummary
3.1 Basic component tests3.2 Real-world component testing3.2.1 Importing the dependencies3.2.2 Setting up the tests3.2.3 Adding the testsSummary
4.1 What are directives?4.1.1 Components vs. directives4.1.2 Different directives4.2 Testing attribute directives4.2.1 Introducing the favorite icon directive4.2.2 Creating tests for FavoriteIconDirective4.2.3 Setting up the FavoriteIconDirective test suite4.2.4 Creating the FavoriteIconDirective tests4.3 Testing structural directives4.3.1 Introducing ShowContactsDirective4.3.2 Creating your tests for ShowContactsDirective4.3.3 Setting up the ShowContactsDirective test suite4.3.4 Creating the ShowContactsDirective testsSummary
5.1 Introducing PhoneNumberPipe5.2 Testing PhoneNumberPipe5.2.1 Testing the default usage for a pipe5.2.2 Testing a pipe with a single parameter5.2.3 Pipes with multiple parametersSummary
6.1 What are services?6.2 How do services work in Angular?6.2.1 Dependency injection6.2.2 The @Injectable class decorator6.3 Creating services with Angular CLI6.4 Testing PreferencesService6.4.1 Testing for failures6.5 Testing services with promises6.5.1 How asynchronous changes testing 6.5.2 Testing for failures with asynchronous services6.6 Testing HTTP services with observablesSummary
7.1 What is the Angular router?7.1.1 Configuring the router7.1.2 Route guards: the router’s lifecycle hooks7.2 Testing routed components7.2.1 Testing router navigation with RouterTestingModule7.2.2 Testing router parameters7.3 Testing advanced routes7.3.1 Route guards7.3.2 Resolving data before loading a routeSummary
8.1 How Protractor works8.2 Writing your first Protractor test8.2.1 File structure8.3 Installing and running8.4 Interacting with elements8.4.1 Test scenario: creating a new contact8.4.2 Test scenario: workflows that don’t create a new contact8.5 by and element methods8.6 Interacting with a list of elements8.6.1 Filtering web elements8.6.2 Mapping the contact list to an array8.6.3 Reduce8.7 Page objectsSummary
9.1 Kinds of timeouts9.2 Testing pages without Angular9.2.1 Disabling waitForAngular9.2.2 Automatically waiting for Angular9.2.3 When to use browser.waitForAngularEnabled()9.3 Waiting with ExpectedConditions9.3.1 Waiting for the contact list to load9.3.2 Testing a dialog9.3.3 Waiting for elements to become stale9.4 Creating custom conditions9.4.1 Using browser.wait9.4.2 Getting elements from the browser9.5 Handling long-running tasks9.5.1 Using expected conditions9.5.2 The browser event loop9.5.3 What happened to $timeout?9.5.4 Highway to the Angular zone9.5.5 Fixing the testSummary
10.1 Configuration file in depth10.1.1 Driver provider options10.1.2 Desired capabilities10.1.3 Plugins10.1.4 Environment variables10.2 Screenshot testing10.2.1 Taking screenshots10.2.2 Taking screenshots on test failure10.2.3 Comparing screenshots10.3 Experimental debugging features10.3.1 WebDriver logs10.3.2 Highlight delay10.3.3 Blocking proxy10.4 The control flow and debugging with Chrome DevTools10.4.1 Asynchronous functions and promises10.4.2 The WebDriver control flow10.4.3 The future: async/await10.4.4 Using Chrome DevToolsSummary
11.1 Jenkins11.1.1 Setting up Jenkins11.1.2 Unit tests11.1.3 E2E tests11.2 CircleCISummary
Introducing the Angular CLIInstalling prerequisitesInstalling the Angular CLI the first timeUpdating an old version of the Angular CLIInstalling the sample projectInstalling dependenciesRunning the application
Angular testingGeneral testing

Overview

Testing Angular Applications is an example-rich, hands-on guide that gives you the real-world techniques you need to thoroughly test all parts of your Angular applications. By the end of this book, you'll be able to confidently write unit and end-to-end tests for Angular applications in TypeScript.

About the Technology

Don't leave the success of your mission-critical Angular apps to chance. Proper testing improves code quality, reduces maintenance costs, and rewards you with happy users. New tools and best practices can streamline and automate all aspects of testing web apps, both in development and in production. This book gets you started.

About the Book

Testing Angular Applications teaches you how to make testing an essential part of your development and production processes. You'll start by setting up a simple unit testing system as you learn the fundamental practices. Then, you'll fine-tune it as you discover the best tests for Angular components, directives, pipes, services, and routing. Finally, you'll explore end-to-end testing, mastering the Protractor framework, and inserting Angular apps into your continuous integration pipeline.

What's Inside

Getting to know TypeScript
Writing and debugging unit tests
End-to-end tests with Protractor
Building continuous integration for your entire test suite

About the Reader

This book is for readers with intermediate JavaScript skills.

About the Authors

Jesse Palmer is a senior engineering manager at Handshake. Corinna Cohn is a single-page web application specialist. Mike Giambalvo and Craig Nishina are engineers at Google.

Quotes
Provides guidance on the overall strategy for how to think about testing on your projects to get the best return on your investment.
- From the Foreword by Brad Green, Engineering Director for Angular at Google

A must-have if you want to learn how to test your Angular applications correctly.
- Rafael Avila Martinez, Intersys Consulting

Essential to development shops delivering products built on the popular Angular framework.
- Jason Pike, Atlas RFID Solutions

Developers of all levels will benefit from the material covered in this book.
- Jim Schmehil, National Heritage Academies