When I'm writing a unit test, it's possible to add an assertion query. I do this for tasks to verify if the task input is converted into the correct tables. But I'm still writing code. And that should be verified by another developer I think.
The ‘code review’ section is only applicable for control procedures, not for assertion queries.
- How do you deal with this? How do I let my collegue know he has to verify that assertion query to?
Currently I have to inform him by e-mail or so, what's actually changed, in stead he could take a look himself to see the difference (like a git pull request).
Maybe what I actually want is having a before data set and an after data set. But that is just an idea (to have as less code as possible, all ‘queries’ should be removed). Or maybe a complete diff what's changed.
Best answer by Anne Buit
View original
