Sep 1, 2018 · 1 min read
I think you are wrong.
It is actually a quite an important role to check if that what is done matches spec (requirements, stories etc.). Nothing to do with “agile”, “waterfall” or whatever tag you put on it.
I have seen it (and done it myself too) when a developer taking up a task misses the finer points of requirements. We are humans and humans make mistakes.
The point of testing in this case is for someone else to read the requirements and to see if nothing is missing. It is the fresh pair of eyes that is important and it actually helps if that pair of eyes see your code as a black box.
