Go

We all love to say that tests are important and strive to get at least 80% test coverage. But very often, tests are not considered to be a real code. Developers treat tests as second-class citizens. It’s just a test; who cares if it is messy, right? And nowadays, with all the AI coding assistant tools, we can just ask the machine to write tests for us because writing tests is boring. ...

When you’re testing software that interacts with another system, it’s common to mock all the dependencies. But let’s be real — mocks are great for simulating interactions, yet they don’t give you any guarantees that the actual integration between systems will work as expected. What is the purpose of mocking database if your code relies on the database behavior (e.g. unique index constraint)? You should always consider writing integration tests! ...