a documentation argument

I’m test­ing some ven­dor-sup­plied soft­ware, and I’ve been test­ing a vari­ety of func­tions and inte­gra­tions. I’ve been more delib­er­ate in my test­ing on this project, less mon­key-at-a-key­board and more cre­ative think­ing about how it might be bro­ken. I’m test­ing things that aren’t nec­es­sar­i­ly doc­u­ment­ed in the require­ments. I got some push-back about it, that we should only be doc­u­ment­ing (and even run­ning) tests that have writ­ten require­ments. That’s basi­cal­ly telling me that I should­n’t do a thor­ough job because some­one else did­n’t do a thor­ough job. And that’s not how I want to work.

Comments are closed.