News for hackers. Stuff that matters.
Re:Monitoring Sucks. But Monitoring as Testing Sucks A Lot More by aidenn0 on Thursday July 19, 2012 @12:54PM (#4266910)
Talking about not testing at all is both stupid and non-sensical, as there will always be some informal integration testing

Not doing any integration testing would translate to the developer making a change in the code and checking it into the VCS without running it. That does happen from time to time, but it's obviously a bad thing, right?

If you build and run a smoke-test before checking in, that's integration testing! So clearly everyone does at least a tiny amount of integration testing, and the question is how far do you take it, and how much effort do you put into automating it is a tradeoff. From experience, the more effort that is put into testing, the fewer bugs will be seen by customers, though you do run into diminishing returns.

Monitoring has the advantage of reporting just bugs that are seen by customers.

QA I think of more as having professionals that pretend to be customers, which, done right, can let you catch the bugs that are egregious enough to make you look had actual customers seen it.

There are no comments on this comment yet.