Unit tests can be another iteration of requirements, a stake in the ground for the future. Nothing like having a merge request come across that fundamentally changes a unit test to know that an old requirement was broken. Sometimes it's not obvious from a code change how it could change the ecosystem of code.
post
there doesn't seem to be anything here
1 comment in c/programming@programming.dev view that post
no comments (yet)