Writing unit tests to enforce modularity in your codebase
QA engineers do all sort of testing, and even QA automation engineers automating all E2E and functional test. Wo why bother write more tests when writing code? And what for? Isn’t it redundant? We often ask ourselves if we should write more test, or what is the level of code coverage we want to reach.
These questions are clearly very relevant. And it is very hard to get clear answers. The intent of the article is exactly to provide some answers.
Please note that this article is part of My path of software craftsmanship. The intention is to share what I came to discover, understand and assimilate so you can learn something out of it.
Related articles :
- Microservices Architecture — a step further than just SOA
- Hexagonal architecture
- Automated Quality Gate, a rail guard to support continuous quality
- Testing Terminology, testing vocabularies and definitions reference
— — —
