Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Angular for Enterprise-Ready Web Applications

You're reading from   Angular for Enterprise-Ready Web Applications Build and deliver production-grade and cloud-scale evergreen web apps with Angular 9 and beyond

Arrow left icon
Product type Paperback
Published in May 2020
Publisher Packt
ISBN-13 9781838648800
Length 824 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Doguhan Uluca Doguhan Uluca
Author Profile Icon Doguhan Uluca
Doguhan Uluca
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Introduction to Angular and Its Concepts 2. Setting Up Your Development Environment FREE CHAPTER 3. Creating a Basic Angular App 4. Automated Testing, CI, and Release to Production 5. Delivering High-Quality UX with Material 6. Forms, Observables, and Subjects 7. Creating a Router-First Line-of-Business App 8. Designing Authentication and Authorization 9. DevOps Using Docker 10. RESTful APIs and Full-Stack Implementation 11. Recipes – Reusability, Routing, and Caching 12. Recipes – Master/Detail, Data Tables, and NgRx 13. Highly Available Cloud Infrastructure on AWS 14. Google Analytics and Advanced Cloud Ops 15. Another Book You May Enjoy
16. Index
Appendix A: Debugging Angular 1. Appendix B: Angular Cheat Sheet

Angular e2e tests

While unit tests focus on isolating the CUT, e2e tests are about integration testing. The Angular CLI leverages Protractor along with WebDriver so that you can write Automated Acceptance Tests (AAT) from the perspective of a user interacting with your application in a browser. As a rule of thumb, you should always write an order of magnitude more unit tests than AATs, because your app changes frequently, and as a result, AATs are vastly more fragile and expensive to maintain compared to unit tests.

If the term web driver sounds familiar, it's because it is an evolution of the canonical Selenium WebDriver. On March 30th, 2017, WebDriver was proposed as an official web standard at the W3C. You read more about it at https://www.w3.org/TR/webdriver. If you're familiar with Selenium, you should feel right at home, since a lot of the patterns and practices are nearly identical.

The CLI provides e2e tests for the initial AppComponent and...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime