Whenever it comes to testing a software, the first thing that comes to my mind is the duel between developers & testers. In today's IT industry, developers are working under aggressive deadlines & they have very less time to code the entire module. Lesser the time given for coding, more is the probability for errors. An error could be because of not capturing the complete requirements, misunderstanding the requirements.

The bigger task comes for the person who is testing the application. With limited time to test the application & also accomodate a test for defect fixes & to make sure the existing functionality is still working after a fix is given. The job of testing begin from understanding the requirements(not to forget a tester can also misunderstand the requirements), & creating a test plan. The most difficult task of testing is, interacting with a developer & make him understand the flaw in the system.

People often say DEVELOPERS ARE NOT GOOD TESTERS. Instead, we should say, A DEVELOPER IS NOT A GOOD TESTER OF HIS OWN CODE.

• IMPROPER USE OF DEVELOPMENT PROCESS

A developer may follow a particular development process, which may not be correct or may result in increased complecity of the system. This flaw in process may not be detected because the individual may not understand right the process.

• MISUNDERSTANDING OF REQUIREMENTS

If a developer falter in understanding the requirement he may not be able to detect it even during testing phase. As, he will believe the system is working as per the functionality is defined.

• OPTIMISM

A developer is optimistic of the correctness of the code he is developing. Due to this, they may underestimate the need of extensive testing.

• TIME MANAGEMENT

Without a formal division between coding & development time, the developer is tempted to work on enhancing the system structure & documentation, rather than allocate that time & effort in testing.