QA Forums
Welcome on the QA Forums.

To take full advantage of everything offered by our software testing & Quality forums, please log in if you are already a member or join our community if you're not yet.... Smile

Display results as :

Rechercher Advanced Search

Who is online?
In total there is 1 user online :: 0 Registered, 0 Hidden and 1 Guest


[ View the whole list ]

Most users ever online was 36 on Wed Jan 10, 2018 12:25 am
October 2019

Calendar Calendar

Comparison of Inspection and testing

Go down

Comparison of Inspection and testing  Empty Comparison of Inspection and testing

Post  puneet on Fri Oct 08, 2010 12:36 am

Inspection and testing both aim at evaluating and improving the quality of the software engineering product before it reaches the customers. The purpose of both is to find and then fix errors, faults and other potential problems.

Inspection and testing can be applied early in software development, although Inspection can be applied earlier than test. Both Inspection and test, applied early, can identify faults, which can then be fixed when it is still much cheaper to do so.

Inspection and testing can be done well or badly. If they are done badly, they will not be effective at finding faults, and this causes problems at later stages, test execution, and operational use.

We need to learn from both Inspection and test experiences. Inspection and testing should both ideally (but all too rarely in practice) produce product-fault metrics and processĀ¬ improvement metrics, which can be used to evaluate the software development process. Data should be kept on faults found in Inspection, faults found in testing, and faults that escaped both Inspection and test, and were only discovered in the field. This data would reflect frequency, document location, security, cost of finding, and cost of fixing.

There is a trade-off between fixing and preventing. The metrics should be used to fine-tune the balance between the investment in the fault detection and fault prevention techniques used. The cost of Inspection, test design, and test running should be compared with the cost of fixing. The faults at the time they were found, in order to arrive at the most cost-effective software development process.


Posts : 21
Reward Points : 41
Join date : 2010-08-22

Back to top Go down

Comparison of Inspection and testing  Empty testing

Post  Guest on Thu Jul 21, 2011 4:47 am

Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test.Software testing can also provide an objective, independent view of the
software to allow the business to appreciate and understand the risks
of software implementation. Test techniques include, but are not limited
to, the process of executing a program or application with the intent
of finding software bugs (errors or other defects).

SQA services


Back to top Go down

Back to top

Permissions in this forum:
You cannot reply to topics in this forum