tests include:

• Unit tests for individual components and isolated functions.


• Integration tests for interactions between multiple components.


• End-to-end tests that assess the entire system’s functionality from a user’s perspective

Tests should be simple. It should be easy to identify what went wrong when reading a failing test.

There are two practices that should be adhered to from the beginning that will allow us to pay down technical debt later on: continuous integration and a small number of basic unit and user-journey tests. The moment a product (if we are in Horizon 3) or feature (in Horizon 2) goes from being an experiment to validated, we need to start aggressively

... See more

code was clean, organized, and logical . Each decision made in their code made sense, and when something didn’t, it was documented well within the code.

A good way to write clean code is to follow principles, like the SOLID principles. Though they were initially designed with OOP (object-oriented programming) in mind, they are extensible to general ... See more

As a developer for 40+ years, I could not live without tests. I think unit tests are one of the great inventions of our trade. For mey they are part of developer accountability. Tests give me security, they tell me things are right. All tests running green gives me a warm feeling and makes me proud. Whenever I write more tests for existing code, I

... See more