When Does Testing Stop?

Aug. 23, 2011 - PRLog -- Here is a list of ways to decide when software testing stops:
•   One of the reasons why testing might stop it is when all the test cases have been run and passed. Such an arrangement is good if you are sure that you have identified the peculiar test cases and that the percent that were not run are not your most significant ones. If 80 % of the test cases are invariably run and that is identified as ample, it is fine questions to ask "Is that 80 % invariably the same 80 %? Does the 80 % contain the indeed significant scenarios and functions? Are there 20 % of the test cases that have never been run?”
•   Another possible way when testing might finish is because a deadline has been met, either an accidental one or one in a client covenant. But making software decisions by dates is problematical because it doesn’t pay attention the status of the project. Features may not be implemented or severe troubles may exist in the product. Finishing the project based on the date doesn’t permit the product to evolve and doesn’t pay attention supplementary work detailed, severe risks that may still exist, problems encountered.
•   Well, testing also might stop when the bug rate or severity falls to a fixed point. But such a fall could be caused by some other reasons, for example, the team of testers being given a week off.
•   It may happen so that the budget has been expended. So testing also comes to a cessation because of this reason. This cessation is another very poor finish to a software project. The reason is that quality of the product is not linked with the financial position allocated to produce software product. Nevertheless, if the money have run out, there is seldom any other option.
•   Software testing http://qatestlab.com/services/our-qa-services/software-pr... might stop when a coverage percentage is met as well, either by function or by code paths. Such dimension is not a bad metric, but should be used in another way to evaluate if there are any places where software bugs http://qatestlab.com/services/sample-deliverables/bug-rep... could be.
•   One more reason when testing may also stop is when a certain metric is met, perhaps three months of uptime under stress without a failure. This is a fine metric because the needs of the user have been translated into purposes of the product. When the product is able to meet these purposes it will meet customer’s needs.

# # #

QATestLab is independent, offshore software testing company located in Kiev, Ukraine. QATestLab performs testing of products on each stage of software development cycle.