summaryrefslogtreecommitdiffstats
path: root/Tests/MumpsCoverage/ZZCOVTST.mcov
Commit message (Collapse)AuthorAgeFilesLines
* CTest: Fix GTM coverage handling of entry point named "%"Joseph Snyder2018-10-161-0/+3
| | | | | | | Removing the "%" character from the name of the routine in the line parser causes CTest to be unable to find a routine entry point that is only named "%". Instead leave it during line parsing and handle routine names ending in "%" explicitly when loading files.
* CTEST: Fix MUMPS file parser and update testJoseph Snyder2014-08-151-27/+35
| | | | | | | | | | 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.
* CTest: Fix MUMPS coverage parsing and testJoseph Snyder2014-05-161-0/+30
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.