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
Web Development with Blazor

You're reading from   Web Development with Blazor A hands-on guide for .NET developers to build interactive UIs with C#

Arrow left icon
Product type Paperback
Published in Jun 2021
Publisher Packt
ISBN-13 9781800208728
Length 310 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Jimmy Engström Jimmy Engström
Author Profile Icon Jimmy Engström
Jimmy Engström
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Section 1:The Basics
2. Chapter 1: Hello Blazor FREE CHAPTER 3. Chapter 2: Creating Your First Blazor App 4. Section 2:Building an Application with Blazor
5. Chapter 3: Introducing Entity Framework Core 6. Chapter 4: Understanding Basic Blazor Components 7. Chapter 5: Creating Advanced Blazor Components 8. Chapter 6: Building Forms with Validation 9. Chapter 7: Creating an API 10. Chapter 8: Authentication and Authorization 11. Chapter 9: Sharing Code and Resources 12. Chapter 10: JavaScript Interop 13. Chapter 11: Managing State 14. Section 3:Debug, Test, and Deploy
15. Chapter 12: Debugging 16. Chapter 13: Testing 17. Chapter 14: Deploy to Production 18. Chapter 15: Where to Go from Here 19. Other Books You May Enjoy

Chapter 13: Testing

In this chapter, we will take a look at testing. Writing tests for our projects will help us develop things rapidly.

We can run the tests and make sure we haven't broken anything with the latest change, and also we don't have to invest our own time in testing the components since it is all done by the tests. Testing will increase the quality of the product since we know that things that worked earlier still function as they should.

But writing tests for UI elements isn't always as easy; the most common way is to spin up the site and use tools that click on buttons and then read the output to determine whether things work or not. The upside of this method is that we can test our site on different browsers and devices. The downside is that it usually takes a lot of time to do these tests. We need to spin up the web, start a web browser, verify the test, close the web browser, and repeat for the next test.

We can use this method in Blazor as...

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