I've got relatively little experience (less than 2 years), but I'm doing most of the senior type roles on my team including reviewing PRs
I work on a small team, it's just a few of us developing. But all of them repeatedly put changes up for review that they've blatantly not tested at all. Not even making sure it runs without syntaxes errors, and certainly no data validation or edge cases being found
I haven't worked with enough different developers to know, maybe it's just this team, but is it really this common for software devs to put their changes up with little or no testing?
Follow up: what's the best way to approach this? What can I do as a reviewer to disincentivize this behavior without just flat out rejecting things?
submitted by /u/multiple4
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/yBv05ts