#testing

Strategies that I’ve found helpful when performing a major technology upgrade.

To build robust tests, each test should verify only what it needs.

Mocks encode our assumptions, which might differ from reality.

Sometimes when you make a change, it ends up changing you.

A deep dive into unit testing looking to answer why, how much, and what.

Testability and reusability goes hand in hand. When you test a function, you run the code in another context than it was built for.

A selection of functional programming concepts that I feel are helpful to all developers.

A few examples of how viewing tests as documentation can affect your test writing.

Concrete tips on how to write robust tests that survive a refactoring.

The need to test a private method often indicates a new class waiting to get out.

For every bug you fix there should be an automated test which will fail if the bug reappears.

Most complexity should be in classes with few dependencies, and most dependencies should be in classes with little complexity.

Don’t try to test code which calls static methods, try to get rid of the static methods.

When naming tests, include both the input as well as the expected outcome.