ASP.NET 5 & Unit Testing
Download as PPTX, PDF•2 likes•7,938 views
The document highlights the importance of unit testing in building robust web applications, detailing steps like writing and running tests, using mocks, and understanding various testing types like integration and UI tests. It discusses how unit testing can decrease costs and human error while improving speed, along with concepts like dependency injection and coverage standards. Additionally, it mentions different tooling and frameworks, underscoring the cost implications of not implementing unit tests.
![public test class [Fact] for public methods without parameters
[Theory] and [InlineData] for methods with parameters](https://image.slidesharecdn.com/aspdotnet5-unittesting-shahedchowdhuri-150823013233-lva1-app6892/85/ASP-NET-5-Unit-Testing-20-320.jpg)
ASP.NET 5 & Unit Testing
- 1. Build Robust Web Apps in the Real World @shahedC WakeUpAndCode.com
- 3. Why Unit Testing? > Getting Started > Writing and Running Tests > 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
- 9. Why Unit Testing? > Getting Started > Writing and Running Tests > Mocking What’s Next?
- 12. Unit Tests Integration Tests UI Tests
- 18. xUnit.net references Web App being tested
- 20. public test class [Fact] for public methods without parameters [Theory] and [InlineData] for methods with parameters
- 21. Build Solution Run Tests in Test Explorer
- 22. Verify actual result against expected result Note “var” keyword
- 23. Verify that expected view equal to returned view
- 25. Temporarily ignore tests with an optional message.
- 26. Correct Views? Redirect to URL? Correct Models? HTTP Code? Mock Depen- dencies! Model Populated?
- 30. 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
- 35. 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?
- 41. Why Unit Testing? > Getting Started > Writing and Running Tests > Mocking What’s Next?
- 42. Email: [email protected] Twitter: @shahedC
Editor's Notes
- #2: Title Page: ASP .NET & Unit Testing Build Robust Web Apps in the Real World By Shahed Chowdhuri Senior Technical Evangelist @ Microsoft Blog: WakeUpAndCode.com Twitter: @shahedC
- #4: Agenda
- #5: Introduction
- #10: Agenda
- #11: Introduction
- #20: Introduction
- #28: Introduction
- #34: Introduction
- #42: Agenda
- #43: Contact Microsoft email: [email protected] Personal Twitter: @shahedC Dev Blog: WakeUpAndCode.com