Testing your software is crucial. Thinking about the complexity of software products nowadays, nobody can ever understand the whole system. And even very experienced software developers are very used to see some of their tests “getting red”, even if they are in a part of the code that has absolutely nothing to do with where you changed your code. Nobody’s perfect, that’s the business. So having tests for your whole software is always considered a best practice but can often feel very cumbersome, especially in classical software products with layered architectures. Try to think about tests for the data mapping…
Software Developer based in Frankfurt, Germany, specialized in Kotlin, Spring Framework, CQRS and Event Sourcing, Test-driven development and code quality