Binary Spectrum Geeks at work: Software testing Part 2

Classic Testing Misconceptions and Mistakes:

Assumption that all defects in the software product have been detected
The assumption that he or she is capable of testing the program completely
The opinion that testing team is responsible for assuring quality
The opinion that the goal of testing is to find bugs only
Careless approach to the detection of major bugs
Negligence in reporting usability problems
Starting the testing phase too late (bugs detection, not bugs reduction)
Putting stress and load testing off to the last minute
Incomplete evaluation of the related project’s documentation
Ignore testing of installation procedures
Failure in correctly identifying risk areas
Paying more attention to running tests than to designing them.
Not reviewing test designs.
Checking that the product does what it’s supposed to do, but not that it doesn’t do what it isn’t supposed to do
Poor bug reporting
Attempting to automate all tests
Expecting to re-run all manual tests

Typical Tester’s Mistakes:

Assuming that the program works correctly.
Unwillingness to document each and every error.
Ignoring or even hiding the problem.
Falling under influence of developers which pressurize the tester not to submit detected defects or to ignore existing intelligence about defects without adequate reasons.
Attempting to have a “not escalate” attitude towards the developer.
Insufficient attention to test planning.
Writing defect reports about non existing problems.

An ideal tester 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.
Possess a good knowledge of the application being tested.
Possess a considerable intelligence.
Possess a hyper-sensitivity to little things.
Be steady to chaos and pressure of development, management, as well as pressure of different circumstances.
Possess organizational skills.
Be skeptical, but not take hostile attitude.
Be capable of breaking the software without feeling any remorse.
Be self-sufficient and tough.
Be a technology hungry.
Be honest.
Be capable to bring the bad news to developers and management.
Be patient – be ready to perform monotonous work during a long time.
Possess a flexible thinking.
Be capable of viewing the project from a global point of view.
Possess detective skills.

Possess strong communication skills which include.

The Author Abdul Quddus is a Test Engineer at Binary Spectrum

Binary Spectrum Geeks at work