SOFTWARE TESTING REALITIES. ►Complete testing is not possible. ►Software testing is Risk based. ►Testing can't show that bugs don't exist. ►The more Bugs you find, the more exist. ►Pesticide Paradox. ►Not all bugs can be fixed. ►Product specification are never final. ►Software testers are not most popular in team members. ►Not all bugs you find, will be fixed. ►When a Bug's Bug difficult to say. ►Complete testing is not possible. Complete testing of the software is not possible, even with the simplest programs. It is due to the following four reasons. ♦The number of possible inputs is very large. ♦The number of possible outputs is very large. ♦The number of paths through the software is very large. ♦The software specification is subjective You might say that a bug is in the eye of beholder. ►Software testing is Risk based. Software testing is risk based because software tester decides to test some parts of the software and some to leave. Software tester leaves some parts of software untested because it is impossible to test the software completely. So software tester leaves some parts untested and delivers the software to the customer. Hence the risk exist for the paths that were decided not to be tested. ►Testing can't show that bugs don't exist. Testing the software do not show that all the bugs of software are uncovered due to the reason that a software can't be tested completely. ►The more Bugs you find, the more they exist. It is common that bugs are related with each other, If a bug exist, then this bug can cause more bugs and removing that bug can remove all the related bugs also. ►Pesticide Paradox. Spending more time on software testing reveals more bugs. Giving more time to testing means you are making your project more late. This is what is called, Pesticide Paradox. ►Not all bugs can be fixed. While testing the software, it is not possible to fix all the bugs that are uncovered. It is due to the following factors: ♦There is not enough time. ♦It's really not a bug. ♦It's too risky to fix. ♦It's just not worth it. ►Product specification are never final. Software developers have a serious problem that product specification are never final. The industry is moving so fast that last years's cutting-edge products are obsolete this year. At the same time, software is getting larger and gaining more features and complexity, resulting in longer and longer development schedules. This two opposing forces resulting in conflict, and the result is a constantly changing product specification. ►Software testers are not most popular in team members. Thst job of software tester is to inspect and critic your peer's work, find problems with it publicize what you found.Here are couple of tips to keep the pace with your felloow teammates. ♦Find bugs early. ♦Temper your enthusiasm. ♦Don't just report bad news. ►When a Bug's Bug difficult to say. Sometimes, a bug exist in the software in the progrmmer perspective not in the tester perspective. Thes type of conflicts exist because the definition for the bug is not defined. Here are some rules to define a BUG. ♦The software does not do something that the product specification says it should do. ♦The software does something that the product specification says it should not do. ♦The software does something that the product specification does not mention. ♦The software does not do something that the product specification does not mention, but should do. ♦The software is difficult to understand.