News for hackers. Stuff that matters.
Re:Apple's Mistake by erso on Friday November 20, 2009 @12:21AM (#951945)
You mean like functional tests, end-to-end integration tests, and view tests?

No developer should limit themselves to unit tests.

Re:Apple's Mistake by Quarrelsome on Friday November 20, 2009 @07:30AM (#952307)
Bullshit, its attitudes like this that lead to crap software. Developers should work with QA to find the bugs, they're not "QA's bugs" they're OUR Bugs, we're a team, right? When you change a component you should also be able to write a simple manual test to prove the functionality works you should also perform this test yourself.

As an optional if the QA people are good then describe what else might be effected by the code (if you edited a generic component). Good QA people will run your test, work out their own variations and also check other areas.

Re:Apple's Mistake by erso on Thursday December 10, 2009 @09:48PM (#989079)
I'm really unsure of where your attitude here is coming from.

At ThoughtWorks we work with QAs constantly. It's a great relationship. There's no such thing as "QA's bugs".