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

Getting started with testing in Blazor with bUnit

Blazor doesn’t have a native unit testing framework, so its great community came up with bUnit, which became the standard for testing Blazor apps.

bUnit allows you to write unit tests either in C# files or in Razor components, and it’s compatible with all the common testing frameworks, such as xUnit, NUnit, and MSTest.

While testing a component, bUnit renders the target component in isolation and provides a full simulation, such as passing parameters, cascading values, and injecting services. It also simulates interactions with the component, such as clicking buttons or triggering event handlers.

The component being tested is known as the Component Under Test (CUT). The term CUT is what we will use throughout this chapter to name the component that we are testing. The term CUT is derived from the term Service Under Test (SUT), which is a known term in testing software overall, not just UI components.

After...