Software testing principles

Page 1

Software testing principles Software testing Principles: 1) an exhaustive examination is not possible A comprehensive examination is not possible. Instead, we need the optimal amount of Tests based on the risk assessment of the application. how do you determine this risk? What operation is most likely to cause your operating system to fail? I'm sure most of you would have guessed, Open 10 different application all at the same time. So if you were testing this operating system, you would realize that defects are likely to be found in multi-tasking activities and need to be thoroughly tested. 2) Lack Clustering Defect Clustering, which means that a small number of modules contain most of the defects found. This is the application of the Pareto principle to software testing: approximately 80% of the problems are found in 20% of the modules. By experience you can identify such risky modules. But this approach has its own problems If the same tests are repeated again and again, the same test cases will eventually no longer find any new errors. 3) Pesticide Paradox The repeated use of the same pesticide mixture for the eradication of insects during agriculture leads over time to the fact that insects develop resistance to the pesticide, whereby pesticides on insects become ineffective. The same applies to software testing. If the same repeated tests are performed, the method is useless to discover new defects. To overcome this, the test cases need to be reviewed and revised regularly, adding new & different test cases to find more defects. The Tester can not simply rely on existing test techniques. He must constantly take care to improve the existing methods in order to make Tests more effective. But even after all the sweat & hard work in the Test, you can claim


Turn static files into dynamic content formats.

Create a flipbook
Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.