Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Learning Angular

You're reading from   Learning Angular A practical guide to building web applications with modern Angular

Arrow left icon
Product type Paperback
Published in Jan 2025
Publisher Packt
ISBN-13 9781835087480
Length 486 pages
Edition 5th Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Aristeidis Bampakos Aristeidis Bampakos
Author Profile Icon Aristeidis Bampakos
Aristeidis Bampakos
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Building Your First Angular Application 2. Introduction to TypeScript FREE CHAPTER 3. Structuring User Interfaces with Components 4. Enriching Applications Using Pipes and Directives 5. Managing Complex Tasks with Services 6. Reactive Patterns in Angular 7. Tracking Application State with Signals 8. Communicating with Data Services over HTTP 9. Navigating through Applications with Routing 10. Collecting User Data with Forms 11. Handling Application Errors 12. Introduction to Angular Material 13. Unit Testing Angular Applications 14. Bringing Applications to Production 15. Optimizing Application Performance 16. Index

Testing components

You may have noticed that whenever we used the Angular CLI to scaffold a new Angular application or generate an Angular artifact, it created some test files for us.

Test files in the Angular CLI contain the word spec in their filename. The filename of a test is the same as the Angular artifact it is testing, followed by the suffix .spec.ts. For example, the test file for the main component of an Angular application is app.component.spec.ts and it resides in the same path as the component file.

We should consider an Angular artifact and its corresponding test one thing. When we change the logic of the artifact, we may need to modify the unit test as well. Placing unit test files with their Angular artifacts makes it easier for us to remember and edit them. It also helps us when we need to refactor our code, such as moving artifacts (not forgetting to move the unit test).

When we scaffold a new Angular application, the Angular CLI automatically...

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 €18.99/month. Cancel anytime