/explore
|
You are here 
|
matthiasnoback.nl | ||
| | | | |
php-and-symfony.matthiasnoback.nl
|
|
| | | | | [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. | |
| | | | |
blog.cleancoder.com
|
|
| | | | | [AI summary] Robert C. Martin argues that mocking should be used sparingly, written manually, and only across significant architectural boundaries to balance test speed, reliability, and good software design. | |
| | | | |
jmmv.dev
|
|
| | | | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | |
| | | | |
arne-mertz.de
|
|
| | | Contents Inmy last post I have written about the main and secondary usesof unit tests and how they compare to other kinds of automated tests. This time I will explore [...] | ||
