As, mothers know their baby well, and they will never put them into a test, where they know their baby is going to fail, so is true, with developers also. I believe we developers always want to see our code working properly, so we will test it to check if it’s working correctly as, designed by us and not as desired by the customer.
Testers will test it to fail it in any way. This is the difference between developer testing and a tester testing.
Developers are considered to be very lenient while testing their piece of development as they tend to skip the bugs.
We will always test it, such that it would work always…; whereas, testers would always query your product such that it will always break the functionality.
Hence, Developers are said to be creators and testers, the destroyers.
It’s always better to get it reviewed from others instead of analyzing it yourself. Try looking at it from customer point of view than from a Developers point of view; that would make your baby smarter. The more we ignore the know bugs, failures then we end up putting more efforts correcting them.
Correcting the bugs at an earlier stage is better than doing it later; we end up putting more efforts figuring out what needs to be fixed. If we face the obstacles at the earlier stage, helps us improve the quality of the code and its efficiency.
Just like a successful life cannot exist without failures, any code cannot be 100% error free without any bugs. It is those bugs which help us know more on the issue and improve our code quality. So, it is developer’s responsibility also to do proper unit testing, we should be good testers to develop good products……
I believe a Good developer should have good testing skills…..by wearing the ’tester’s hat’, he can not only improve the code quality, but also helps him satisfy the customers requirements.
well captured @bsayna
ReplyDelete-Ram