kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
CMake/Tests/MumpsCoverage/VistA-FOIA/Packages/Uncategorized/ZZCOVTST.m

44 lines
1.1 KiB
Mathematica
Raw Normal View History

CTest: Fix MUMPS coverage parsing and test Fix the MUMPS coverage parser: * Account for tabs after entry points * Stop double incrementing lines that have explicit calls to the 0 line * If a line has been previously marked as non executable, but then contains a count, increment it an extra one to push it back into the executable code set. Add a custom routine and corresponding coverage files in the test case. This file is smaller and has cmcov/mcov files that have data for only that routine.
2014-05-14 17:28:07 +04:00
ZZCOVTST;OSEHRA/JPS -- Test routine for Coverage Parsing;4/28/2014
; (tab) This is series of comments
; (tab) it should all be not executable
; (spaces) one of these sets might be a problem
; (spaces) we will have to see.
EN ; This entry point shouldn't be found without fixing
N D
S D=1 ;An executable line
D T1^ZZCOVTST
I '$$T5 W "RETURNED FROM t5",!
Q
; This line not executable
CTEST: Fix MUMPS file parser and update test The current file parser for a MUMPS routine uses a period "." as the one of the signals that a line of MUMPS code is executable. This is not a correct assumption. Add the period to the list of characters that CTest will not consider the start of a line of code. Update the test routine to have an entry point with code to match the scenario mentioned above.
2014-08-15 18:50:36 +04:00
D T6^ZZCOVTST
CTest: Fix MUMPS coverage parsing and test Fix the MUMPS coverage parser: * Account for tabs after entry points * Stop double incrementing lines that have explicit calls to the 0 line * If a line has been previously marked as non executable, but then contains a count, increment it an extra one to push it back into the executable code set. Add a custom routine and corresponding coverage files in the test case. This file is smaller and has cmcov/mcov files that have data for only that routine.
2014-05-14 17:28:07 +04:00
;
T1 ; This line should always be found
N D
S D=2
W !,D,!,"This is the second entry point",!
D T2^ZZCOVTST(D)
Q
;
T2(EQ) ; This is debatable and only called with ENT^ROU notation
N D
S D=3
W !,D,!,EQ,"This is the third entry point",!
D T3^ZZCOVTST
Q
;
T3 N D S D=4 W D,!,"Fourth Entry point",! Q
;
T4 N D S D=5 W "Shouldn't be executed"
W "Lots to not do"
Q
T5(EQ) ;this entry point is called with a $$ notation
W "THIS IS THE $$ NOTATION!",!
Q 0
CTEST: Fix MUMPS file parser and update test The current file parser for a MUMPS routine uses a period "." as the one of the signals that a line of MUMPS code is executable. This is not a correct assumption. Add the period to the list of characters that CTest will not consider the start of a line of code. Update the test routine to have an entry point with code to match the scenario mentioned above.
2014-08-15 18:50:36 +04:00
T6 ; An entry point to show comments inside of "DO" blocks
D
. W "This is executable code",!
. ;This is a comment inside the do block, not executable
. S ZZBLAH="blah"
W "Ending T6",!
CTest: Fix MUMPS coverage parsing and test Fix the MUMPS coverage parser: * Account for tabs after entry points * Stop double incrementing lines that have explicit calls to the 0 line * If a line has been previously marked as non executable, but then contains a count, increment it an extra one to push it back into the executable code set. Add a custom routine and corresponding coverage files in the test case. This file is smaller and has cmcov/mcov files that have data for only that routine.
2014-05-14 17:28:07 +04:00
;