I had to suddenly change the internals of a class a couple weeks ago. This class was responsible for sending messages to our developers through our internal chat. The algorithm was something like this: * It would get the list of messages to be sent For each message, it would:
It doesn't matter!
3
An example with code!
One of the biggest truths when it comes to developer testing is that it has to be easy! If it's not easy, we'll simply don't do it. We'll find lots of…
4
In enterprise systems, especially those that are a little distributed, a common argument against unit testing is that "in real life, most bugs occur…
3
We are all past the idea that a unit testing has to only test a single class, isolating it from all its dependencies. We can, but it doesn't mean we…
1
In the amazing The Philosophy of Software Design, John Ousterhout argues that having large classes that implement the full expected behaviour can be…
1
No, you would not! In fact, I would argue that focusing solely on E2E tests can actually have the opposite effect, meaning, you will find less bugs.
1
See all

Effective Software Testing