Is Functional Testing sufficient to determine the Code Coverage?
Break Testing, Functional testing, Software Break Points, Software load testing, Software Quality, Software testing, Software testing tools
Is Functional Testing (User acceptance tests (business transaction flows), +ve input tests, -ve input tests) sufficient to determine the Code Coverage?
Do we see any additional coverage when we do non-functional testing (example: load testing with the same inputs used in functional testing)? If so, How?
Software/Hardware used:
Software/Hardware used:
ASKED:
December 24, 2008 4:55 AM
UPDATED:
February 4, 2011 5:07 AM
Answer Wiki:
We can never test a product 100%. After doing functional testing and other non-functional testing, there could still be some portion of the code that remains untouched. The most important part is to cover the code that is most used by the end user. Risk based approach has to be applied here to make sure testing coverage is adequate, No less and no more.
http://itknowledgeexchange.techtarget.com/software-testing-big-picture/qa-sharp-3-is-functional-testing-sufficient-to-determine-the-code-coverage/
To see all answers submitted to the Answer Wiki: View Answer History.
Functional testing means, to test functionality / integrity of software. And its a Black box testing method while Code coverage is the one of the white box testing method. But both methods are complementary to each other. As far as my best knowledge, functional testing helps to determine code coverage for small project or SBS. Code coverage is not the 100% sure (as Shillu said earlier) in case of functionality test. Because, it is not possible, to test this with full guarantee all the time as somewhere the infrastructures are not up to date. As the time goes, the test will pass and after that it will be marketable.