Aye, there's the rub. If you still have leviathan programs with
left-hand indicators this tool may tell you that your test went through
that instruction, but I'm guessing it probably won't tell you that
indicators 41, 23 and 94 were off and indicators 54 and 87 were on,
therefore the instruction didn't actually execute. If it does - then
kudos!
Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck
Calabro
Sent: Wednesday, April 30, 2014 11:43 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDI 9.1 Availability
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
