News for hackers. Stuff that matters.
Re:Unit testing is not (generally) useful by axod on Thursday February 05, 2009 @11:24AM (#468119)
It's a false sense of security though. It's like putting a big badge on your website saying it 'validates' - even if it's totally broken in real world browsers.

In my experience, the more common bugs are integration bugs, scaling bugs, weird memory usage issues, not to mention interfacing to external systems - for example some weird browser comes along and does idiotic requests you'd never expect a sane person to do.

Those things are very hard to test for, and don't really produce a good ROI as abstractbill says... Best just to log things, graph things where possible, spot weirdness, investigate and fix.

Re:Unit testing is not (generally) useful by biohacker42 on Thursday February 05, 2009 @01:15PM (#468403)
Everything you mentioned I count as part of TDD or BDD or what ever automated testing acronym you like.

What I suspect is that all of us have basically the same idea in mind, and what we're disagreeing over is mostly semantics and context.

Btw, all of my unit tests include memory usage validation. It's easy in c and c++, but I'm not sure how it would be done in a web development environment.