Write meaningful unit tests

▤ Summary

The normal answer would probably be that it alerts a future maintainer if a change breaks the tested functionality. Consider a test that breaks (or needs changing) for every refactoring, even if the new code actually provides the desired functionality. Since you need to write a failing test, you use the immediate signal to prove the assumption that your code doesnt handle this case yet. I dont always do it, especially if the code is mostly about shovelling data back and forth, but I probably should overcome my laziness and at least write some component test with acceptance criteria. Whether you decide to TDD or not, I hope youve gotten some food for thought on how to improve the quality of your unit tests.

▦ Linked Companies