Hacker News Reader

No need to read such a post...

Title says: "You don't inject for tests"

And, before opening the link, you know what you're going to find.

Someone confusing "testing" and "unit testing".

First thing that came to my mind (while reading the header on HN) was "There are several kind of testing..." but... Curiosity killed the cat. Let's open the link.

Ouch, first sentence:

"What is unit testing for?"

OK, closed.

Don't waste your time reading this crap ; )

View on HN

I'm not sure I understand what you're so upset about?

"Don't waste your time reading this crap" because of some imprecise verbiage?

According to the typical "testing pyramid", unit testing should be the most common type of testing done -- is it really so unforgivable that someone would use a general term (test) for what they do most often (unit test)?

I scoped my blog just to unit tests, because it's short note rather than article. DI can be useful on integration and acceptance level too - for simple apps you should be able to configure whole app or its parts as easy as you run it on production. Without DI you have to do some magic with class / module constants, which can populate on other parts.

Reply on news.ycombinator.com