Click here to Skip to main content
15,909,440 members

Survey Free Text Answers

Should developers test their own code?

13 Dec 2010 to 20 Dec 2010 Let the religious wars begin.

Text entry answers for sorted by frequency of occurrance.

(3) CListCtrl
(2) Developers should do some testing, but there should be external formal (or formal-ish) testing as well.
(1) Developers should test their code, then dedicated testers should test again.
(1) developers should test their own code before dedicated testers
(1) Developers should test their own code fully, plus there should be a full automated or planned test
(1) Developers should test their own code, but should also be tested by dedicated testers.
(1) Everyone should test all the code. If a bug slips though, it's _everyone's_ fault, not just one person's.
(1) fully test your own code but if possible you shouldn't be the only one testing it.
(1) html codes
(1) If you make a change - you should test it before you pass it on to the testers. You wont necessarily find all problems - but you'll get most of them
(1) radar display
(1) Test all code that has Bacon as an output
(1) tests are boring
(1) They should only remove bugs and all other should be left on customers.
(1) Yes, developers should fully test their own code, but other testing should also be done also.
(1) Depends
(1) depends completely on situation
(1) Depends on the use.
(1) A combination of options 1 and 2
(1) all of the above
(1) Answer a fool according to his folly - lest he be wise in his own conceit.
(1) batch files
(1) Both developers and dedicated testers