Search
Who is online?
In total there are 2 users online :: 0 Registered, 0 Hidden and 2 Guests None
Most users ever online was 74 on Sun Oct 20, 2024 6:05 am
Comparison of Inspection and testing
Page 1 of 1
Comparison of Inspection and testing
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.
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.
puneet- Posts : 21
Reward Points : 41
Join date : 2010-08-22
testing
Hi,
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 serviceshttp://testing-whiz.com/
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 serviceshttp://testing-whiz.com/
Guest- Guest
Similar topics
» Can you say some major techniques used by iPad App Testing Services to tackle testing challenges in 2016?
» Can you suggest some top testing frameworks used by Android App Testing Services?
» What is the differences between Automated testing and Manual testing?
» Economics of Testing
» QA Testing Training
» Can you suggest some top testing frameworks used by Android App Testing Services?
» What is the differences between Automated testing and Manual testing?
» Economics of Testing
» QA Testing Training
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
Mon Mar 06, 2017 3:29 am by JebaQpt
» Can you say some unavoidable aspects for all Android App Testing Services?
Thu Oct 20, 2016 3:12 am by testbytes
» Can someone say about the things to look for while hiring iPad App Testing Services?
Fri Oct 14, 2016 5:26 am by testbytes
» Can you suggest some top testing frameworks used by Android App Testing Services?
Fri Oct 14, 2016 5:24 am by testbytes
» Can someone say why should hire specialist iPad app testing services?
Fri Oct 14, 2016 5:21 am by testbytes
» Can someone say how Android mobile app testing will become crucial in next 5 years?
Wed Aug 17, 2016 5:44 am by testbytes
» Can you say how iPhone app testing services fare in next few years?
Wed Aug 17, 2016 5:33 am by testbytes
» Can anyone say how different types of Mobile Application Testing improve the credibility of apps?
Wed Aug 17, 2016 5:07 am by testbytes
» Can you say some useful fragmentation tools used by android app testing services?
Mon Jul 25, 2016 1:01 am by testbytes