1. Attachment with source code
- As everyone know developers are emotionally attached to their code which makes them not to test like a tester. "A developer would never degrade his own baby" :P Its just like how we tester are emotionally attached to a bug. Don't we get angry when a developer counters us telling that the bug reported is never a bug? :D
2. Concentrates only on positive cases
- Most developers would normally think only about positive and straight forward scenarios whereas testers mentality would be always in breaking the code and concentrating more on negative test cases.
3. Lack of End user experience
- Testers would normally check many applications & game and would exactly know what is required, as they would have already experienced checking similar kind of application whereas most developers wouldn't ( If a developer is reading this he would surely crib about not having time to check other applications Gotcha! )
4. Not much exposure to bugs:
- A tester would have experience in testing many application and would know when a code could break whereas a developer wouldn't have much exposure to bug which make a developer fail in testing.
5. Tight schedule:
- Most companies wouldn't give sufficient time to developers which leads them to not test the whole application.
So what do you think can a developer test his own application better than a tester ?
- As everyone know developers are emotionally attached to their code which makes them not to test like a tester. "A developer would never degrade his own baby" :P Its just like how we tester are emotionally attached to a bug. Don't we get angry when a developer counters us telling that the bug reported is never a bug? :D
2. Concentrates only on positive cases
- Most developers would normally think only about positive and straight forward scenarios whereas testers mentality would be always in breaking the code and concentrating more on negative test cases.
3. Lack of End user experience
- Testers would normally check many applications & game and would exactly know what is required, as they would have already experienced checking similar kind of application whereas most developers wouldn't ( If a developer is reading this he would surely crib about not having time to check other applications Gotcha! )
4. Not much exposure to bugs:
- A tester would have experience in testing many application and would know when a code could break whereas a developer wouldn't have much exposure to bug which make a developer fail in testing.
5. Tight schedule:
- Most companies wouldn't give sufficient time to developers which leads them to not test the whole application.
So what do you think can a developer test his own application better than a tester ?
I agree only with the 4th point.
ReplyDeleteRavindra Shenoy
ReplyDelete"A developer would always deny whatever a tester says" :D
1 : A real developer treats his own code as a liability (it keeps changing so it makes no sense to get attached to the source code)
ReplyDelete2 : A real developer writes unit tests for all his code (even corner cases) aka TDD.
3 : Depends on whether the developer is experienced or an amateur on the product he is working on.
4 : Strongly Disagree , again , a real developer tests his code and passes it ahead for quality assurance only after he is fully satisfied with the code quality (the amount of bugs found here are almost uncountable in this stage).
5 : Depends mostly on the company.