/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 www.code4it.dev
4 ways to create Unit Tests without Interfaces in C# | Code4IT
| | php-and-symfony.matthiasnoback.nl
Mocking at architectural boundaries: persistence and time - Matthias Noback - Blog
2.9 parsecs away

Travel
| | [AI summary] The author advocates for the principle of 'don't mock what you don't own' by designing application interfaces for side effects like persistence and time, thereby improving architecture and removing brittle test dependencies.
| | adamstorr.co.uk
Autofixture and IOptions - A Winning Combination | Adam Storr
3.2 parsecs away

Travel
| | A look at how you can customize AutoFixture to allow for IOptions to be created without mocking.
| | matthiasnoback.nl
Mocking at architectural boundaries: persistence and time - Matthias Noback - Blog
2.7 parsecs away

Travel
| |
| | blog.wingman-sw.com
Legacy Code Change - a Boy Scout Adds Tests | James Grenning's Blog
17.9 parsecs away

Travel
| Here is a legacy code change policy for a team adopting TDD that has a legacy code base: Test-drive new code Add tests to legacy code before modification Test-drive changes to legacy code Refactori...