Test-Driven Development With Blazor
summary
Claims that TDD works on the frontend with Blazor, then shows it: tests drive a recreated Counter and a Loan Application page, tests fail first, code is added and tests go green. Tools used are bUnit, xUnit and shouldly (plus bUnit.web.query and Playwright for end-to-end). Demo notes Shouldly ~80M NuGet downloads and component tests run in ~10–15ms. Tests focus on user behavior not CSS or implementation details.
AI-written summary · about
chapters (11)
- 0:00Introduction to test-driven development with Blazor
- 0:27Who this talk is for
- 3:37Why write tests and TDD benefits
- 5:43Understanding test-driven development fundamentals
- 19:31TDD for Blazor components
- 23:03What to test in frontend
- 35:48Live TDD demo with Counter
- 42:10Chekhov's gun for tests
- 45:21Better tests with BUnit WebQuery
- 50:41Start TDD overcoming objections
- 1:01:50Q&A
related talks
39mBlazor Stability Testing for Bullet Proof Application
38mTesting Blazor Application Components: Fun with Benefits
55mBest practices unit testing Blazor components with bUnit
37mTesting Blazor Components
59mBlazor-testing from A to Z
54mHow to create maintainable and testable Blazor components
36mHow to create maintainable and testable Blazor components
59mBuild Blazor Components with Confidence and Precision
