Contents [hide]
Why it is recommended that a programmer should avoid attempting to test his or her own program?
A programmer should avoid attempting to test his or her own program. It is extremely difficult, after a programmer has been constructive while designing and coding a program, to suddenly, overnight, change his or her perspective and attempt to form a completely destructive frame of mind toward the program.
Why you shouldn’t test your own code?
Your developers, as good as they may be, write bugs in their software. They can’t find their own bugs. Even if they go testing each other’s code, they don’t have the kind of software breaking thinking & skills that QA do and just won’t find as many bugs.
When to let developers test their own code?
Developers should unit test their own code. Independent testers not only test to break, they test the unstated and undefined assumptions that the developers made while coding. I would expect the developer to do some initial testing before they commit any changes and to have satisfied themselves that the code works.
Why do so many developers complain about testing?
Some developers also complain that creating unit tests wastes time and that it is too complicated and too difficult to execute repeatedly, even when the testing process is automated. The bottom line, they say, is that testing slows down the development process and decreases coding productivity.
Why do developers need a dedicated testing team?
They are professional users. There are a few good reasons to have a dedicated testing team. First, as mentioned above, developers are very good at testing that their code works, but not a breaking it. Also, as you say, a developer knows what they wrote, but a testing teams knows what should have been written.
How are testers and developers alike and different?
Developers develop in the way that the required functionality will work perfectly. They will be pretty good enough in picking a functionality and only focus on building that functionality efficiently whereas they are totally opposite from testers. Testers think creatively to break the software in various ways.