Re:That won't scale Or present cost vs. future value
by rf15 on Monday April 24, 2023 @03:27AM
(#35684632)
Is it really a good idea to bend your code to satisfy your testing environment and not the other way around?
[ Parent
| on HN ]
Re:That won't scale Or present cost vs. future value
by rtheunissen on Monday April 24, 2023 @03:37AM
(#35684705)
"Bend" is not a good description of the intention here. Good code should be easy to test effectively and interfaces are a common way to achieve that. We should absolutely design our code with testing in mind.
For example, you have a repository for some entity as a dependency of a service and you would like to test some behavior of the service when the repository fails. In this case, the service can depend on an interface of the repository instead and the test can create a stub that implements that interface, whereby you can simulate the error. If the service depended on the actual repository, this becomes very difficult to do.
Re:That won't scale Or present cost vs. future value
by agalunar on Monday April 24, 2023 @06:29AM
(#35685771)
> Good code should be easy to test effectively
Can you explain why this is? or maybe more specifically what you mean by this.
Re:That won't scale Or present cost vs. future value
by robertlagrant on Monday April 24, 2023 @05:00AM
(#35685206)
Your tests are part of your code. Your implementation code should not make writing your test code difficult.
Re:That won't scale Or present cost vs. future value
by pjc50 on Monday April 24, 2023 @09:35AM
(#35687455)
It's kind of unavoidable once you're trying to do unit tests with mocks. You either end up with interfaces for everything and a dependency injection framework, or you end up with some very non-isolated tests that take ages to run because they need inseparable parts of the whole real system.