nt of view "incomplete evaluation of the related projects documentation", "ignoring the testing of installation procedures" and the "failure to identify risk areas accurately" can also lead to the degeneration of the effectiveness of the Test. Another common complaint that is encountered is the exceClassic Testing Misconceptions and Mistakes

Let's take a look at some of the common mistakes or misconceptions that actually reflect on a Testers quality, his efficiency and effectiveness. A couple of assumptions that are the key culprits, are the assumptions that all defects in the software product have been detected and that he or she are capable of testing the program completely.

Other misconceptions like "quality assurance is the responsibility of the testing team" and "the goal of testing is only to find bugs" can lead to a very unhealthy form of testing. Another mistake (usually associated with Junior Testers) is a rather careless approach to with regard to the detection of major bugs and the negligence in reporting usability issues.

In certain organizations more emphasis is given to the unit testing front carried out by the developers leading to the starting of the testing phase too late, This will usher a false sense of security or complacence that they at times even go to the extend of delaying or putting off the stress and load testing to the last minute. This results in the whole testing process being rendered ineffective.

From a testers point of view "incomplete evaluation of the related projects documentation", "ignoring the testing of installation procedures" and the "failure to identify risk areas accurately" can also lead to the degeneration of the effectiveness of the Test. Another common complaint that is encountered is the exces

tware product have been detected and that he or she are capable of testing the program completely.

Other misconceptions like "quality assurance is the responsibility of the testing team" and "the goal of testing is only to find bugs" can lead to a very unhealthy form of testing. Another mistake (usually associated with Junior Testers) is a rather careless approach to with regard to the detection of major bugs and the negligence in reporting usability issues.

In certain organizations more emphasis is given to the unit testing front carried out by the developers leading to the starting of the testing phase too late, This will usher a false sense of security or complacence that they at times even go to the extend of delaying or putting off the stress and load testing to the last minute. This results in the whole testing process being rendered ineffective.

From a testers point of view "incomplete evaluation of the related projects documentation", "ignoring the testing of installation procedures" and the "failure to identify risk areas accurately" can also lead to the degeneration of the effectiveness of the Test. Another common complaint that is encountered is the exce

e (usually associated with Junior Testers) is a rather careless approach to with regard to the detection of major bugs and the negligence in reporting usability issues.

In certain organizations more emphasis is given to the unit testing front carried out by the developers leading to the starting of the testing phase too late, This will usher a false sense of security or complacence that they at times even go to the extend of delaying or putting off the stress and load testing to the last minute. This results in the whole testing process being rendered ineffective.

From a testers point of view "incomplete evaluation of the related projects documentation", "ignoring the testing of installation procedures" and the "failure to identify risk areas accurately" can also lead to the degeneration of the effectiveness of the Test. Another common complaint that is encountered is the exce

g of the testing phase too late, This will usher a false sense of security or complacence that they at times even go to the extend of delaying or putting off the stress and load testing to the last minute. This results in the whole testing process being rendered ineffective.

From a testers point of view "incomplete evaluation of the related projects documentation", "ignoring the testing of installation procedures" and the "failure to identify risk areas accurately" can also lead to the degeneration of the effectiveness of the Test. Another common complaint that is encountered is the exce

nt of view "incomplete evaluation of the related projects documentation", "ignoring the testing of installation procedures" and the "failure to identify risk areas accurately" can also lead to the degeneration of the effectiveness of the Test. Another common complaint that is encountered is the excessive attention that is paid to running the Test rather than designing and planning the same.

What are the characteristics of a Good Test Engineer?

He or she should possess at least a minimum knowledge of software engineering. Often a Tester should be an expert in a number of areas. He or she should possess a substantial knowledge of the application that is tested. The tester should have a natural hyper-sensitivity to trivial things,

He should possess software engineering skills (understanding the rules of software engineering, knowing computer programming and having operating system level knowledge). Often a tester needs to be an expert in a number of areas, be steady to chaos and pressure of development, management, as well as pressure of different circumstances. While its ok for the tester skeptical of the developers claims, He should not take a Hostile Attitude!

Typically he should be capable of breaking the software with out feeling bad, possess detective skills and strong communication skills which include people skills, Tenacity and the capability to criticize and interpret the criticism is a mature manner.