×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 4/30/2014 10:50 AM, Jeff Crosby wrote:
What is "Line level code coverage analysis capability"
Charles gave a good reference, but here's an example.
I have a massive S/38 style leviathan of a program. It's got dozens of
TAGs and probably a hundred GOTOs. It's got lines conditioned by
indicators, groups of indicators. It's got IF statements 9 levels deep.
I made some changed and now I want to test this thing. How do I know
that I've tested all the possibilities?
With line level coverage, I can see which IF statements did not get
executed during my test run. That probably means my test database is
missing some customers that trigger the special conditions, so I add
those to my test database and run it again.
Some of the lines that weren't hit may be irrelevant: they were put in
during the 90s when we bought that other company out. Hey, now I can
see that I'll never need those lines again and can take them out! But
some of those lines are going to be important, and if we want to be sure
we've processed all the possible combinations (it can seem like
N-factorial!) line level coverage is a great start.
--buck
midrange.com
