Testing Your Web Apps
summary
Coverage strategy for .NET web apps focuses on concrete tradeoffs: favor many unit tests, fewer brittle integration/UI tests, and plan the upfront cost of automation because manual regression grows until it exceeds automation. Practical tips include using Microsoft.AspNetCore.Mvc.Testing to spin a TestServer and HttpClient, prefer SQLite over in-memory EF to avoid LINQ-to-SQL mismatches, seed databases with fixtures via class/collection fixtures, stub external services, run Selenium for E2E, and drive BDD with SpecFlow/gherkin; examples show working seeded tests and successful runs.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:42Testing Pyramid
- 4:47Small NonPage Companies
- 8:46Cost of Bugs
- 12:02Integration Testing
- 16:45Restrictions
- 17:16Integration Tests
- 22:09Web Application Factory
- 22:43Selenium Integration Testing
- 23:13How Does Selenium Work
- 26:33BDD
- 30:23Syntaxes
- 31:48Example
- 34:17Frameworks
- 35:18Stress Tests
- 37:33Demo
related talks
01h 02mTesting First - Getting The How
58mTesting strategy for your ASP.NET Core micro-service
53mModern Web Testing: Going Beyond Selenium
01h 05mMicrotesting
41mTesting .NET Web APIs from A to Z
49mAlex Pshe: 13 Best Practices for Building Web App Test Automation from Scratch
38mStating the Obvious: Adding Non-functional Tests to CI
38mModern Web Testing: Going Beyond Selenium