Build Blazor Components with Confidence and Precision
summary
Uses a Blazing Story template to run a Storybook-like Blazor app (install via CLI, two templates for Server or Wasm), shows that Storybook has ~84,000 stars while Blazing Story has ~300, explains required naming convention component.stories and how properties produce controls like a Color Picker control. Demonstrates Playwright for E2E with Playwright codegen & trace viewer, generates NUnit tests (no xUnit), adds assertions for DOM state, saves trace ZIPs for CI, and runs axe‑playwright accessibility checks that initially fail then pass after excluding the “best-practices” tag.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:14Blazing Story benefits
- 5:48Setting up Blazing Story
- 15:12Creating component stories
- 21:16Playwright testing intro
- 24:57Writing Playwright tests
- 37:20Accessibility testing with axe
- 45:17Q&A
related talks
01h 04mBuild Your First Full-Stack Blazor App
01h 16mTest-Driven Development With Blazor
39mBlazor Stability Testing for Bullet Proof Application
49mArchitecting Blazor applications – An Angular inspired approach
01h 01mBlazor, a new framework for browser-based .NET apps
01h 02mBlazor in more depth
43mBlazor in .NET 8: Mastering the New Render Modes and Building Interactive Web Apps
41mModern Full-Stack Web Development with ASP.NET Core & Blazor