What is Test Coverage Specificity?
by Nataliia Vasylyna | April 29, 2014 10:00 am
Information technology is rather abstract thing for many ordinary people.
Tangible result of software development is properly working applications. Results of mobile testing, desktop testing and web site testing are error reports and absence of significant defects in the program after release.
Testers have to communicate with their customers and give them reports about progress and results of manual and automated testing. Test coverage is often mentioned in such reports. Test coverage is intangible. In order to demonstrate the progress and the current results of testing activities certain test coverage metrics are used.
Test Coverage is Often Represented in Reports for the Customers As:
- percentage of performed tests;
- quantity of tests that passed;
- quantity of tests that failed.
Software developers and testers sometimes utilize special instruments for measuring percentage of performed tests during automated testing.
But it is wrong to understand test coverage only as simple quantity or percentage of executed, passed and failed tests. It’s a complex, plural concept comprising various perspectives of the application under test and the testing process.
A software testing company wants its testers to look at the software product from diverse angles and perform tests of different types. Only in this case test coverage can be sufficient and testers will be able to find all the serious errors in the software.
Learn more from QATestLab
Related Posts:
- How to Provide the Best Test Coverage?: https://blog.qatestlab.com/2014/04/30/how-to-provide-the-best-test-coverage/
- How to Enlarge Test Coverage?: https://blog.qatestlab.com/2014/04/26/how-to-enlarge-test-coverage/
- 7 Ways to Measure Test Coverage: https://blog.qatestlab.com/2011/03/31/ways-to-measure-test-coverage/
Source URL: https://blog.qatestlab.com/2014/04/29/what-is-test-coverage-specificity/