Book Image

Mastering Blazor WebAssembly

By : Ahmad Mozaffar
3.5 (2)
Book Image

Mastering Blazor WebAssembly

3.5 (2)
By: Ahmad Mozaffar

Overview of this book

Blazor WebAssembly is a revolutionary technology in software development that enables you to develop web applications with a rich user interface using C# without JavaScript. It can be run natively in the browser and soon on mobile apps with .NET MAUI, making it a superweapon in the .NET developer’s toolbox. This capability has opened the doors for the JavaScript community to have a stable framework to build single page applications (SPAs) maintained by Microsoft and driven by the community. Mastering Blazor WebAssembly is a complete resource that teaches you everything you need to build client-side web applications using C# & .NET 7.0. Throughout this book, you’ll discover the anatomy of a Blazor WebAssembly project, along with the build, style, and structure of the components. You’ll implement forms to catch user input and collect data, as well as explore the topics of navigating between the pages in depth. The chapters will guide you through handling complex scenarios like RenderTrees, writing efficient unit tests, using variant security methods, and publishing the app to different providers, all in a practical manner. By the end of this book, you’ll have the skills necessary to build web apps with Blazor WebAssembly, along with the basics for a future in mobile development with .NET MAUI and Blazor.
Table of Contents (21 chapters)
1
Part 1: Blazor WebAssembly Essentials
5
Part 2: App Parts and Features
13
Part 3: Optimization and Deployment

Introducing Playwright for E2E tests

In E2E tests, we need to ensure that our system is fully behaving as expected, including the interaction with external services, such as the web API.

Even though unit testing is more crucial than E2E testing, a great testing strategy includes all different types of tests, including unit tests, integration tests, E2E tests, and performance tests. The reason why automated E2E tests are less important than unit tests is that all the components have to be available and running. In our case, every time you want to run E2E tests, the API has to be up and running, and a sandbox environment has to be available, otherwise the tests will keep adding, editing, or deleting data if the API doesn’t support test data. E2E tests are also slower to run, so running them all the time, as we can with unit tests, is not preferable.

E2E tests complement rather than replace unit tests for the product’s overall testing. E2E testing is not meant to replace...