> There is also a philosophical question you're touching on: > When is testing a developer function, and when is it a > software tester function?
It's not just a philosophical question. At our company we're involved right now in hashing out exactly what sort of testing ought to be done on development projects and whose responsibility each piece really is.
We're at a point in integrating Agile methods into the mainstream IT department where there are collisions between different groups and disagreement about fundamentals, and nailing down these issues is important to make sure the ball isn't dropped somewhere along the line.
For instance, developers tend to think they needn't take unit testing as far as UI testing, say with tools like httpUnit or htmlUnit. They consider it functional testing, and in the jurisdiction of the testing group. But from a holistic point of view, code that had been unit tested up to the UI layer would certainly be more solid and functional testing would go more smoothly. We've already had problems with sloppy output from webapps that would have been nipped in the bud had developers taken unit testing just one more layer up.
Unit testing at that level can follow Michael's guidelines quite easily and successfully. There's no need to unit test with a real browser any more than there is with a real file or a real database or a real mail server.
Anyway, I understand Michael's comments as pertaining specifically to unit testing, which is clearly a developer function. Some of the other points people have raise are perfectly valid, but they don't pertain specifically to unit testing.
Flat View: This topic has 50 replies
on 51 pages
[
«
|
404142434445464748
|
»
]
Previous Topic
