Testing, TDD and Code Quality in .NET
Complete guide and related articles on Testing
Complete guide to testing in .NET: unit tests, TDD, mocking and quality control to write predictable software you can change without fear of regressions.
Practical guides on testing in .NET
1 articles found
When testing becomes essential
Testing becomes essential when software must evolve over time, when multiple developers work on the same codebase, and when a defect can block business operations. In these scenarios tests are not optional overhead: they are the system that makes refactoring, new features, and continuous releases trustworthy.
Useful .NET technologies for testing
- C# — language in which both tests and the code under test are written
- .NET — platform with native support for xUnit, NUnit and MSTest
- ASP.NET — the framework where integration testing is most critical
- Blazor — UI components that require dedicated testing strategies
- Entity Framework — ORM that should be tested with in-memory or SQLite for isolation
Sources and references
Kent Beck - Test Driven Development
I include this because testing is not just end-of-line verification; it is also a design discipline.
Martin Fowler - Refactoring and tests
This supports the idea that without tests, refactoring remains fragile, expensive, and harder to justify.
Robert C. Martin - Clean Code
I use this to connect testing with the professional obligation to produce readable and maintainable code.