ASP.NET Core Unit Testing
Download as PPTX, PDF1 like3,992 views
The document provides guidance on building robust web applications using ASP.NET 5, with a focus on writing and running tests, utilizing dependency injection, and incorporating mocking techniques. It emphasizes the importance of unit tests, outlines various testing types, and discusses best practices for managing dependencies in application code. Additionally, it highlights the costs associated with testing and the benefits of reduced human error and improved performance.
![public test class [Fact] for public methods without parameters
[Theory] and [InlineData] for methods with parameters](https://image.slidesharecdn.com/aspdotnetcore-unittesting-shahedchowdhuri-160418173110/85/ASP-NET-Core-Unit-Testing-19-320.jpg)
ASP.NET Core Unit Testing
- 1. Build Robust Web Apps in the Real World @shahedC WakeUpAndCode.com * aka ASP.NET 5 before RC1
- 3. Background > Getting Started > Writing and Running Tests > Dependency Injection & Mocking What’s Next?
- 5. > Nothing new to learn > Error-prone > Expensive > Slower
- 6. > Less human error > Faster! > Decreasing costs > Learning curve
- 7. Legacy New/ Improved • SRP • OCP • LSP • ISP • DIP
- 11. Unit Tests Integration Tests UI Tests
- 19. public test class [Fact] for public methods without parameters [Theory] and [InlineData] for methods with parameters
- 20. Build Solution Run Tests in Test Explorer
- 21. Verify actual result against expected result Note “var” keyword
- 22. Verify that expected view equal to returned view
- 24. Temporarily ignore tests with an optional message.
- 25. Correct Views? Redirect to URL? Correct Models? HTTP Code? Mock Depen- dencies! Model Populated?
- 28. In Startup: Add namespace and dependencies In Application Code: • Constructor Injection • Setter Injection
- 31. Mocks Pre-programmed with expected results, doesn’t actually connect to DB, behavior verification. Fakes Working examples, but not production-ready (e..g in-memory database) Stubs Provides canned answers http://martinfowler.com/articles/mocksArentStubs.html
- 36. Cost of Adding Unit Tests Cost of Not Having Unit Tests Bugs Features Expenses
- 37. Views & ViewModels Controllers Service Layer Repository Layer Entity Framework (ORM) SQL Server (database)
- 39. 60 to 80% coverage ok?
- 40. • Databases • File Systems • Network Resources • Web Requests & Responses
- 42. Background > Getting Started > Writing and Running Tests > Dependency Injection & Mocking What’s Next?
- 43. Email: [email protected] Twitter: @shahedC
Editor's Notes
- #2: Title Page: Automated Testing in ASP .NET Core* 1.0 Build Robust Web Apps in the Real World * aka ASP.NET 5 before RC1 By Shahed Chowdhuri Senior Technical Evangelist @ Microsoft Blog: WakeUpAndCode.com Twitter: @shahedC
- #4: Agenda
- #5: Introduction
- #10: Introduction
- #19: Introduction
- #27: Introduction
- #35: Introduction
- #43: Agenda
- #44: Contact Microsoft email: [email protected] Personal Twitter: @shahedC Dev Blog: WakeUpAndCode.com