
Test selection at Adyen
Saving time and resources
bits and pieces on software testing, design, maintenance, and evolution. A continuation of the https://www.effective-software-testing.com book.
Dormant Last read · last published · next check
Read 3 days ago and current, but nothing has been published for 22 months.

Saving time and resources

If you work on a legacy system, you probably have questioned a technical decision or two there.

Whenever you gather a team to discuss their insufficient testing efforts, common responses include:

What's the best way to populate database data?

I had to suddenly change the internals of a class a couple weeks ago.

It doesn't matter!

An example with code!

One of the biggest truths when it comes to developer testing is that it has to be easy!

In enterprise systems, especially those that are a little distributed, a common argument against unit testing is that "in real life, most bugs occur when apps communicate with each other".

We are all past the idea that a unit testing has to only test a single class, isolating it from all its dependencies.