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 realise 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,...