Update to change version to 1.3

Changed version to 1.3.
This commit is contained in:
JOEL IVEY 2015-12-17 12:46:45 -08:00
parent 7165552a9b
commit 1043d299b0
20 changed files with 5359 additions and 5219 deletions

View File

@ -1,4 +1,16 @@
VISTA2A>D ^XUP
The following is a screen capture for installation, running
unit tests, and running coverage analysis on the m-unit
routines (%ut, %ut1, and %utcover) in the GT.M environment.
VISTA>S DUZ=1 D Q^DI,^%ZIS
VA FileMan 22.0
Select OPTION:
DEVICE: HOME// Console (Cache' on Windows) Right Margin: 80//
VISTA>D ^XUP
Setting up programmer environment
This is a TEST account.
@ -14,96 +26,88 @@ Select OPTION NAME: EVE
5 EVENT CAPTURE EXTRACT ECXEC Event Capture Extract
Press <RETURN> to see more, '^' to exit this list, OR
CHOOSE 1-5: 1 EVE Systems Manager Menu
Select Systems Manager Menu Option: PROgrammer Options
Select Programmer Options Option: KIDS Kernel Installation & Distribution Syste
m
Edits and Distribution ...
Utilities ...
Installation ...
Patch Monitor Main Menu ...
Select Kernel Installation & Distribution System Option: INSTallation
Select Kernel Installation & Distribution System Option: INStallation
Select Installation Option: LOAd a Distribution
Enter a Host File: C:\TEMP\M\MASH_1.3_0.KID
1 Load a Distribution
2 Verify Checksums in Transport Global
3 Print Transport Global
4 Compare Transport Global to Current System
5 Backup a Transport Global
6 Install Package(s)
Restart Install of Package(s)
Unload a Distribution
Select Installation Option: 1 Load a Distribution
Enter a Host File: C:\TEMP\M\MASH_0.3.0_151207.KID
KIDS Distribution saved on Dec 07, 2015@17:14:06
Comment: Update with coverage for Cache systems
KIDS Distribution saved on Dec 16, 2015@10:13:18
Comment: Updated version supporting coverage analysis in Cache systems.
This Distribution contains Transport Globals for the following Package(s):
MASH*0.3*0
MASH*1.3*0
Distribution OK!
Want to Continue with Load? YES//
Loading Distribution...
MASH*0.3*0
Use INSTALL NAME: MASH*0.3*0 to install this Distribution.
MASH*1.3*0
This Patch is for Version 1.3, you are running Version 1
1 Load a Distribution
2 Verify Checksums in Transport Global
3 Print Transport Global
4 Compare Transport Global to Current System
5 Backup a Transport Global
6 Install Package(s)
Restart Install of Package(s)
Unload a Distribution
Want to continue installing this build? NO// YES
Use INSTALL NAME: MASH*1.3*0 to install this Distribution.
Select Installation Option: 6 Install Package(s)
Select INSTALL NAME: MASH*0.3*0 Loaded from Distribution 12/8/15@09:23:
07
=> Update with coverage for Cache systems ;Created on Dec 07, 2015@17:14
This Distribution was loaded on Dec 08, 2015@09:23:07 with header of
Update with coverage for Cache systems ;Created on Dec 07, 2015@17:14:06
Select Installation Option: INSTall Package(s)
Select INSTALL NAME: MASH*1.3*0 Loaded from Distribution 12/16/15@11:03
:06
This Distribution was loaded on Dec 16, 2015@11:03:06 with header of
Updated version supporting coverage analysis in Cache systems. ;Created on D
ec 16, 2015@10:13:18
It consisted of the following Install(s):
MASH*0.3*0
Checking Install for Package MASH*0.3*0
MASH*1.3*0
Checking Install for Package MASH*1.3*0
This Patch is for Version 1.3, you are running Version 1
Install Questions for MASH*0.3*0
Want to continue installing this build? NO// YES
Install Questions for MASH*1.3*0
Incoming Files:
17.9001 M-UNIT TEST GROUP (including data)
Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO// NO
Want KIDS to INHIBIT LOGONs during the install? NO// NO
Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO// NO
Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//
Want KIDS to INHIBIT LOGONs during the install? NO//
Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//
Enter the Device you want to print the Install messages.
You can queue the install by enter a 'Q' at the device prompt.
Enter a '^' to abort the install.
DEVICE: HOME// Console (Cache' on Windows)
Install Started for MASH*0.3*0 :
Dec 08, 2015@09:57:53
Build Distribution Date: Dec 07, 2015
Install Started for MASH*1.3*0 :
Dec 16, 2015@11:04:04
Build Distribution Date: Dec 16, 2015
Installing Routines:
Dec 08, 2015@09:57:53
Dec 16, 2015@11:04:04
Running Pre-Install Routine: ^ZZUTPRE
Installing Data Dictionaries:
Dec 08, 2015@09:57:53
Dec 16, 2015@11:04:04
Installing Data:
Dec 08, 2015@09:57:53
Dec 16, 2015@11:04:04
Installing PACKAGE COMPONENTS:
Installing REMOTE PROCEDURE
Installing OPTION
Dec 08, 2015@09:57:53
Dec 16, 2015@11:04:04
Running Post-Install Routine: ^ZZUTPOST
Routine: ut Loaded, Saved as %ut
@ -121,31 +125,43 @@ Routine: uttcovr Loaded, Saved as %uttcovr
Updating KIDS files...
MASH*0.3*0 Installed.
Dec 08, 2015@09:57:53
MASH*1.3*0 Installed.
Dec 16, 2015@11:04:04
NO Install Message sent
Install Completed
1 Load a Distribution
2 Verify Checksums in Transport Global
3 Print Transport Global
4 Compare Transport Global to Current System
5 Backup a Transport Global
6 Install Package(s)
Restart Install of Package(s)
Unload a Distribution
Select Installation Option: ^PG Programmer mode
------------------ START OF ADDED COMMENT ----------------------
---- RUNNING THE BASIC UNIT TESTS - Note these do throw expected errors ----
----- Also, GTM invalid function names messages have been removed -----
----- they won't appear in subsequent runs -----
------------------- END OF ADDED COMMMENT ----------------------
VISTA>
VISTA2A>D ^%utt1
-------------------------- START OF COMMENT -------------------
The following runs the sequence of unit tests (DOing ^%utt1
from the top runs the code
D EN^%ut($T(+0),1) ; Run tests here, be verbose.
QUIT
which is a good way to set up both development code (e.g., %ut,
%ut1, and %utcover) and unit tests so that starting code from
the top runs the tests. The routines %uttcovr and %utt6 are
special, and run series of tests or coverages when run from
the top.
Once %utt1 is running, due to the routines following an XTROU
tag in it, it also runs the unit tests in %utt2, %utt4,
%utt5, %utt6, and %uttcovr. The XTROU tags could be in each
and a given unit test routine would still be run only once.
To test error handling, and handling of failed tests and other
problems, unlike most unit tests, there are 7 expected failures
and 1 expected error (dividing by zero) in these tests. All of
the other tests which are not indicated as expected failures or
tests, should pass without problems.
__________________________ END OF COMMENT -------------------
VISTA>D ^%utt1
T1 - - Make sure Start-up Ran.----------------------------------------- [OK]
T2 - - Make sure Set-up runs.------------------------------------------ [OK]
@ -218,130 +234,19 @@ ne from tag, and only not covered...........--------------------------- [OK]
Ran 6 Routines, 37 Entry Tags
Checked 113 tests, with 7 failures and encountered 1 error.
------------------ START OF ADDED COMMENT ----------------------
Running the %utt6 routine from the top runs a number of different
entry points as unit tests
------------------- END OF ADDED COMMMENT ----------------------
VISTA2A>D ^%utt6
RUNNING COMMAND LINE TESTS VIA DOSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
.
T5^%utt1 - Error count check - Intentionally throwing a failure
...............
T1 - Test 1.----------------------------------------------------------- [OK]
T2 - Test 2.----------------------------------------------------------- [OK]
Ran 1 Routine, 2 Entry Tags
Checked 2 tests, with 0 failures and encountered 0 errors.........
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
ON PURPOSE - SHOULD FAIL
BADCHKTF^%utt5 - CHKTF should fail on false value - SET FALSE (0) ON PURPOSE -
SHOULD FAIL
BADERROR^%utt5 - throws an error on purpose - Error: <UNDEFINED>BADERROR+6^%utt
5 *Q
CALLFAIL^%utt5 - called FAIL to test it - Called FAIL to test it
LEAKSBAD^%utt5 - check leaks with leak - LEAKSBAD TEST - X NOT SPECIFIED VARIABL
E LEAK: X
NVLDARG1^%utt5 - check invalid arg in CHKEQ - NO VALUES INPUT TO CHKEQ^%ut - no
evaluation possible
................................................................................
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
-------------------------- START OF COMMENT -------------------
%uttcovr runs a series of tests from both the regular code
(e.g., DO EN^%ut("routinename")) as well as by calling other
entry points (e.g., DO ^%ut), so that coverage can be included
for these other entry points. While it is recommended that
normally the unit tests be run when entering at the top, the
routines %utt6 instead run a series of different
unit tests and the routine %uttcovr runs coverage analysis
for all of the unit tests.
__________________________ END OF COMMENT -------------------
Running command line tests by RUNSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
.
T5^%utt1 - Error count check - Intentionally throwing a failure
...............
T1 - Test 1.----------------------------------------------------------- [OK]
T2 - Test 2.----------------------------------------------------------- [OK]
Ran 1 Routine, 2 Entry Tags
Checked 2 tests, with 0 failures and encountered 0 errors.........
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
ON PURPOSE - SHOULD FAIL
BADCHKTF^%utt5 - CHKTF should fail on false value - SET FALSE (0) ON PURPOSE -
SHOULD FAIL
BADERROR^%utt5 - throws an error on purpose - Error: <UNDEFINED>BADERROR+6^%utt
5 *Q
CALLFAIL^%utt5 - called FAIL to test it - Called FAIL to test it
LEAKSBAD^%utt5 - check leaks with leak - LEAKSBAD TEST - X NOT SPECIFIED VARIABL
E LEAK: X
NVLDARG1^%utt5 - check invalid arg in CHKEQ - NO VALUES INPUT TO CHKEQ^%ut - no
evaluation possible
................................................................................
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
ON PURPOSE - SHOULD FAIL
BADCHKTF^%utt5 - CHKTF should fail on false value - SET FALSE (0) ON PURPOSE -
SHOULD FAIL
BADERROR^%utt5 - throws an error on purpose - Error: <UNDEFINED>BADERROR+6^%utt
5 *Q
CALLFAIL^%utt5 - called FAIL to test it - Called FAIL to test it
LEAKSBAD^%utt5 - check leaks with leak - LEAKSBAD TEST - X NOT SPECIFIED VARIABL
E LEAK: X
NVLDARG1^%utt5 - check invalid arg in CHKEQ - NO VALUES INPUT TO CHKEQ^%ut - no
evaluation possible
.
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
NOW RUNNING UNIT TESTS FOR %uttcovr
......................................................................
Ran 1 Routine, 9 Entry Tags
Checked 70 tests, with 0 failures and encountered 0 errors.
NOW RUNNING UNIT TESTS FOR %utt6
.........
Ran 1 Routine, 5 Entry Tags
Checked 9 tests, with 0 failures and encountered 0 errors.
------------------ START OF ADDED COMMENT ----------------------
Running %uttcovr from the top of the routine runs coverage by
calling a number of unit tests from different entry points so
that each of them is included in the analysis. Looking at
this shows how to run many different entry points in one
coverage analysis, as well as removing unit tests that may
have the same base namespace from the displayed analysis.
------------------- END OF ADDED COMMMENT ----------------------
VISTA2A>d ^%uttcovr
VISTA>d ^%uttcovr
------------------- RUNNING %utt1 -------------------....
T5^%utt1 - Error count check - This is an intentional failure.
@ -379,6 +284,7 @@ Checked 70 tests, with 0 failures and encountered 0 errors.
LEAKSBAD TEST - X NOT SPECIFIED VARIABLE LEAK: X
xxxxxxxxxxxxxxxxxxxx GOING TO COV^%ut FOR %utt5 at 3
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
ON PURPOSE - SHOULD FAIL
@ -402,6 +308,7 @@ Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
xxxxxxxxxxxxxxxxxxxx GOING TO COV^%ut FOR %utt5 at -1
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
ON PURPOSE - SHOULD FAIL
@ -425,6 +332,9 @@ Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
xxxxxxxxxxxxxxxxxxxx GOING TO MULTAPIS for %utt4 and %ut
------------------- RUNNING ^%ut -------------------
RUNNING COMMAND LINE TESTS VIA DOSET^%ut
@ -492,6 +402,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
@ -515,8 +426,10 @@ evaluation possible
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
NOW RUNNING UNIT TESTS FOR %uttcovr
......................................................................
@ -542,11 +455,15 @@ Checked 2 tests, with 0 failures and encountered 0 errors.....--------- [OK]
Ran 1 Routine, 1 Entry Tag
Checked 4 tests, with 0 failures and encountered 0 errors.
------------ SUMMARY ------------
Ran 2 Routines, 6 Entry Tags
Checked 13 tests, with 0 failures and encountered 0 errors.
xxxxxxxxxxxxxxxxxxxx GOING TO COVERAGE for %utt4 and %ut at 3
------------------- RUNNING ^%ut -------------------
RUNNING COMMAND LINE TESTS VIA DOSET^%ut
@ -581,6 +498,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
Running command line tests by RUNSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
@ -613,6 +531,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
@ -636,8 +555,10 @@ evaluation possible
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
NOW RUNNING UNIT TESTS FOR %uttcovr
......................................................................
@ -652,12 +573,6 @@ NOW RUNNING UNIT TESTS FOR %utt6
Ran 1 Routine, 5 Entry Tags
Checked 9 tests, with 0 failures and encountered 0 errors.
------------------ START OF ADDED COMMENT ----------------------
%utt4 contains unit tests to run coverage analysis on the
%utt3 routine from the COV^%ut API, while %uttcovr runs
all of the analyses from the COVERAGE^%utcover API.
------------------- END OF ADDED COMMMENT ----------------------
------------------- RUNNING ^%utt4 -------------------
MAIN - - Test coverage calculations
T1 - Test 1.----------------------------------------------------------- [OK]
@ -669,10 +584,12 @@ Checked 2 tests, with 0 failures and encountered 0 errors.....--------- [OK]
Ran 1 Routine, 1 Entry Tag
Checked 4 tests, with 0 failures and encountered 0 errors.
------------ SUMMARY ------------
Ran 2 Routines, 6 Entry Tags
Checked 13 tests, with 0 failures and encountered 0 errors.
Routine %utt3 (73.68%) 14 out of 19 lines covered
- Detailed Breakdown
Tag %utt3^%utt3 ------ 0 out of 0 lines covered
@ -692,6 +609,7 @@ Routine %utt3 (73.68%) 14 out of 19 lines covered
Tag TEARDOWN^%utt3 (100.00%) 2 out of 2 lines covered
Tag XTMUNITV^%utt3 ------ 0 out of 0 lines covered
Routine %utt3 (73.68%) 14 out of 19 lines covered
- Summary
Tag %utt3^%utt3 ------ 0 out of 0 lines covered
@ -704,11 +622,17 @@ Routine %utt3 (73.68%) 14 out of 19 lines covered
Tag TEARDOWN^%utt3 (100.00%) 2 out of 2 lines covered
Tag XTMUNITV^%utt3 ------ 0 out of 0 lines covered
Routine %utt3 (73.68%) 14 out of 19 lines covered
Overall Analysis 14 out of 19 lines covered (73% coverage)
xxxxxxxxxxxxxxxxxxxx LISTING DATA VIA LIST
Routine %utt3 (73.68%) 14 out of 19 lines covered
- Detailed Breakdown
Tag %utt3^%utt3 ------ 0 out of 0 lines covered
@ -728,6 +652,7 @@ Routine %utt3 (73.68%) 14 out of 19 lines covered
Tag TEARDOWN^%utt3 (100.00%) 2 out of 2 lines covered
Tag XTMUNITV^%utt3 ------ 0 out of 0 lines covered
Routine %utt3 (73.68%) 14 out of 19 lines covered
- Summary
Tag %utt3^%utt3 ------ 0 out of 0 lines covered
@ -740,11 +665,16 @@ Routine %utt3 (73.68%) 14 out of 19 lines covered
Tag TEARDOWN^%utt3 (100.00%) 2 out of 2 lines covered
Tag XTMUNITV^%utt3 ------ 0 out of 0 lines covered
Routine %utt3 (73.68%) 14 out of 19 lines covered
Overall Analysis 14 out of 19 lines covered (73% coverage)
xxxxxxxxxxxxxxxxxxxx Finished in ENTRY^%uttcovr
------------------- RUNNING VERBOSE^%utt6 -------------------
RUNNING COMMAND LINE TESTS VIA DOSET^%ut
@ -822,6 +752,7 @@ ne from tag, and only not covered...........--------------------------- [OK]
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
Running command line tests by RUNSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
@ -854,6 +785,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
NEWSTYLE - identify new style test indicator functionality.------------ [OK]
@ -888,10 +820,13 @@ ISUTEST - check ISUTEST inside unit test.------------------------------ [OK]
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
NOW RUNNING UNIT TESTS FOR %uttcovr
RTNANAL - - routine analysis...---------------------------------------- [OK]
COVCOV - - check COVCOV - remove seen lines......---------------------- [OK]
COVRPT...........------------------------------------------------------ [OK]
@ -909,6 +844,7 @@ Checked 70 tests, with 0 failures and encountered 0 errors.
NOW RUNNING UNIT TESTS FOR %utt6
SETROUS - - generate array with indices of routines to exclude......--- [OK]
CHKCMDLN - check command line processing of %utt5---------------------- [OK]
CHKGUI - check GUI processing of %utt5--------------------------------- [OK]
@ -952,6 +888,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
Running command line tests by RUNSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
@ -984,6 +921,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
@ -1007,8 +945,10 @@ evaluation possible
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
NOW RUNNING UNIT TESTS FOR %uttcovr
......................................................................
@ -1057,6 +997,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
Running command line tests by RUNSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
@ -1089,6 +1030,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
@ -1112,8 +1054,10 @@ evaluation possible
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
NOW RUNNING UNIT TESTS FOR %uttcovr
......................................................................
@ -1273,6 +1217,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
@ -1296,6 +1241,7 @@ evaluation possible
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
@ -1313,10 +1259,12 @@ NOW RUNNING UNIT TESTS FOR %utt6
Ran 1 Routine, 5 Entry Tags
Checked 9 tests, with 0 failures and encountered 0 errors.
------------ SUMMARY ------------
Ran 18 Routines, 112 Entry Tags
Checked 398 tests, with 14 failures and encountered 2 errors.
Routine %ut (100.00%) 256 out of 256 lines covered
- Detailed Breakdown
Tag %ut^%ut (100.00%) 2 out of 2 lines covered
@ -1412,6 +1360,7 @@ RT",$J)),$NA(^TMP("%utCOVRESULT",$J)),VERBOSITY)
Tag TOTAGS^%ut1 (100.00%) 13 out of 13 lines covered
Tag UP^%ut1 (100.00%) 1 out of 1 lines covered
Routine %utcover (100.00%) 79 out of 79 lines covered
- Detailed Breakdown
Tag %utcover^%utcover (100.00%) 2 out of 2 lines covered
@ -1422,6 +1371,7 @@ Routine %utcover (100.00%) 79 out of 79 lines covered
Tag SETROUS^%utcover (100.00%) 4 out of 4 lines covered
Tag TRIMDATA^%utcover (100.00%) 3 out of 3 lines covered
Routine %ut (100.00%) 256 out of 256 lines covered
- Summary
Tag %ut^%ut (100.00%) 2 out of 2 lines covered
@ -1453,6 +1403,7 @@ Routine %ut (100.00%) 256 out of 256 lines covered
Tag VERBOSE^%ut (100.00%) 7 out of 7 lines covered
Tag VERBOSE1^%ut (100.00%) 4 out of 4 lines covered
Routine %ut1 (88.43%) 237 out of 268 lines covered
- Summary
Tag %ut1^%ut1 (100.00%) 2 out of 2 lines covered
@ -1478,6 +1429,7 @@ Routine %ut1 (88.43%) 237 out of 268 lines covered
Tag TOTAGS^%ut1 (100.00%) 13 out of 13 lines covered
Tag UP^%ut1 (100.00%) 1 out of 1 lines covered
Routine %utcover (100.00%) 79 out of 79 lines covered
- Summary
Tag %utcover^%utcover (100.00%) 2 out of 2 lines covered
@ -1488,10 +1440,90 @@ Routine %utcover (100.00%) 79 out of 79 lines covered
Tag SETROUS^%utcover (100.00%) 4 out of 4 lines covered
Tag TRIMDATA^%utcover (100.00%) 3 out of 3 lines covered
Routine %ut (100.00%) 256 out of 256 lines covered
Routine %ut1 (88.43%) 237 out of 268 lines covered
Routine %utcover (100.00%) 79 out of 79 lines covered
Overall Analysis 572 out of 603 lines covered (94% coverage)
VISTA2A>D H^XUS
Overall Analysis 572 out of 603 lines covered (94% coverage)
VISTA>
-------------------------- START OF COMMENT -------------------
The output presented by the use of COVERAGE^%ut (which is
called by running %uttcovr from the top) presents the overall
result as the last item in the output, with finer detail
available by backing up to earlier parts of the output.
For the verbosity variable values of zero or one only the
totals by routine and total for all routines is shown.
For a verbosity value of two, the coverage for tags within
the routines is shown followed by the totals for each routines
and for all routines. For a value of three (as used above)
the output first shows the routines with coverage by tags,
and if the coverage is less than 100%, then the lines that
were NOT covered during the analysis are listed as well
(as shown above for the routine %ut1), followed by the
output for tags only and for totals.
__________________________ END OF COMMENT -------------------
VISTA>D H^XUS
End of installation, unit tests, and coverage analysis
Logged out at Dec 16, 2015 11:08 am
VISTA>D H^XUISS
Logged out at Dec 16, 2015 11:08 am
<Session disconnected>

View File

@ -1,32 +1,36 @@
The following is a screen capture for installation, running
unit tests, and running coverage analysis on the m-unit
routines (%ut, %ut1, and %utcover) in the GT.M environment.
------------------ START OF ADDED COMMENT ----------------------
The KIDS file was loaded ionto the tmp directory, it was
then converted to unix line terminators with dos2unix.
The MUMPS instance was then started and
------------------- END OF ADDED COMMMENT ----------------------
-------------------------- START OF COMMENT -------------------
Since the KIDs build was created in a Cache environment, it
is necessary to convert the dos line terminator to those for
unix prior to installation. The KIDs build was in the tmp
directory.
__________________________ END OF COMMENT -------------------
[softhat@softhat-VirtualBox ~]$ cd tmp
[softhat@softhat-VirtualBox tmp]$ ls *.KID
MASH_1.3_0.KID
[softhat@softhat-VirtualBox tmp]$ dos2unix MASH_1.3_0.KID
dos2unix: converting file MASH_1.3_0.KID to Unix format ...
[softhat@softhat-VirtualBox tmp]$ cd ..
[jiveysoft@jiveysoft-VirtualBox ~]$ cd tmp
[jiveysoft@jiveysoft-VirtualBox tmp]$ dos2unix MASH_0.3_900_152120-7.KID
dos2unix: converting file MASH_0.3_0_151207.KID to Unix format ...
[jiveysoft@jiveysoft-VirtualBox tmp]$ cd ..
[jiveysoft@jiveysoft-VirtualBox ~]$ mumps -dir
VISTA2A>S DUZ=17 D Q^DI,^%ZIS
[softhat@softhat-VirtualBox ~]$ mumps -dir
GTM>S DUZ=1 D Q^DI,^%ZIS
VA FILEMAN 22.2V2
Select OPTION:
DEVICE: HOME// TELNET
VISTA2A>D ^XUP
GTM>D ^XUP
Setting up programmer environment
This is a TEST account.
Terminal Type set to: C-VT100
Terminal Type set to: C-VT220
Select OPTION NAME: EVE
1 EVE Systems Manager Menu
@ -38,109 +42,114 @@ Select OPTION NAME: EVE
Press <Enter> to see more, '^' to exit this list, OR
CHOOSE 1-5: 1 EVE Systems Manager Menu
Select Systems Manager Menu Option: PROGrammer Options
Select Programmer Options Option: KIDS Kernel Installation & Dis
Select Systems Manager Menu <TEST ACCOUNT> Option: PROgrammer Options
Select Programmer Options <TEST ACCOUNT> Option: KIDS Kernel Installation & Dis
tribution System
Edits and Distribution ...
Utilities ...
Installation ...
Patch Monitor Main Menu ...
Select Kernel Installation & Distribution System Option: INSTalla
Select Kernel Installation & Distribution System <TEST ACCOUNT> Option: INSTalla
tion
1 Load a Distribution
2 Verify Checksums in Transport Global
3 Print Transport Global
4 Compare Transport Global to Current System
5 Backup a Transport Global
6 Install Package(s)
Restart Install of Package(s)
Unload a Distribution
Select Installation <TEST ACCOUNT> Option: LOAd a Distribution
Enter a Host File: /home/softhat/tmp/MASH_1.3_0.KID
Select Installation Option: LOAd a Distribution
Enter a Host File: /home/jiveysoft/tmp/MASH_0.3_0_151207.KID
KIDS Distribution saved on Dec 07, 2015@17:14:06
Comment: Update with coverage for Cache systems
KIDS Distribution saved on Dec 16, 2015@10:13:18
Comment: Updated version supporting coverage analysis in Cache systems.
This Distribution contains Transport Globals for the following Package(s):
MASH*0.3*0
MASH*1.3*0
Distribution OK!
Want to Continue with Load? YES//
Loading Distribution...
MASH*0.3*0
Use INSTALL NAME: MASH*0.3*0 to install this Distribution.
1 Load a Distribution
2 Verify Checksums in Transport Global
3 Print Transport Global
4 Compare Transport Global to Current System
5 Backup a Transport Global
6 Install Package(s)
Restart Install of Package(s)
Unload a Distribution
MASH*1.3*0
This Patch is for Version 1.3, you are running Version 1
Select Installation Option: INstall Package(s)
Select INSTALL NAME: MASH*0.3*0 Loaded from Distribution 12/10/15@19:0
1:59
=> Update with coverage for Cache systems ;Created on Dec 07, 2015@17:14
Want to continue installing this build? NO// YES
Use INSTALL NAME: MASH*1.3*0 to install this Distribution.
This Distribution was loaded on Dec 10, 2015@19:01:59 with header of
Update with coverage for Cache systems ;Created on Dec 07, 2015@17:14:06
Select Installation <TEST ACCOUNT> Option: INSTall Package(s)
Select INSTALL NAME: MASH*1.3*0 Loaded from Distribution 12/16/15@14:22
:41
This Distribution was loaded on Dec 16, 2015@14:22:41 with header of
Updated version supporting coverage analysis in Cache systems. ;Created on D
ec 16, 2015@10:13:18
It consisted of the following Install(s):
MASH*0.3*0
Checking Install for Package MASH*0.3*0
MASH*1.3*0
Checking Install for Package MASH*1.3*0
This Patch is for Version 1.3, you are running Version 1
Install Questions for MASH*0.3*0
Want to continue installing this build? NO// YES
Install Questions for MASH*1.3*0
Incoming Files:
17.9001 M-UNIT TEST GROUP (including data)
Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//
Want KIDS to INHIBIT LOGONs during the install? NO//
Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//
Enter the Device you want to print the Install messages.
You can queue the install by enter a 'Q' at the device prompt.
Enter a '^' to abort the install.
DEVICE: HOME// TELNET
Install Started for MASH*1.3*0 :
Dec 16, 2015@14:23:29
Install Started for MASH*0.3*0 :
Dec 10, 2015@19:02:29
Build Distribution Date: Dec 07, 2015
Build Distribution Date: Dec 16, 2015
Installing Routines:
-------------------------- START OF COMMENT -------------------
GT.M, as it is loading routines, will note code that it does
not recognize these are the result of having supporting both
GT.M and Cache - the unrecognized code is protected with
checks for Cache or GT.M, and will not cause problems.
They may also appear the first time that GT.M runs a specific
routine, but will not appear after that. Only the first
couple are shown here but there are many others. They go
by very quickly as well.
__________________________ END OF COMMENT -------------------
------------------ START OF ADDED COMMENT ----------------------
At this point GT.M identifies functions that it does not
recognize - these are functions for Cache and are functional.
Also, similar listings may be seen the first time that the
routines are run - they will not be shown after that.
------------------- END OF ADDED COMMMENT ----------------------
I $P($P($ZV,") ",2),"(")<2012 S NMSP=$ZU(5)
^-----
At column 40, line 19, source module /home/softhat/VistA-Instance/r/ZZUTPRE.m
%GTM-E-INVFCN, Invalid function name
I $P($P($ZV,") ",2),"(")>2011 S NMSP=$NAMESPACE
^-----
At column 40, line 20, source module /home/softhat/VistA-Instance/r/ZZUTPRE.m
%GTM-E-INVSVN, Invalid special variable name
Dec 10, 2015@19:02:29
Dec 16, 2015@14:23:29
Running Pre-Install Routine: ^ZZUTPRE
Installing Data Dictionaries:
Dec 10, 2015@19:02:29
Dec 16, 2015@14:23:29
Installing Data:
Dec 10, 2015@19:02:29
Dec 16, 2015@14:23:29
Installing PACKAGE COMPONENTS:
Installing REMOTE PROCEDURE
Installing OPTION
Dec 10, 2015@19:02:30
Dec 16, 2015@14:23:30
Running Post-Install Routine: ^ZZUTPOST
-------------------------- START OF COMMENT -------------------
The following is present in the GT.M install, since in at least
one version of Linux the correct conversion the ut files to %ut
did not happen. In this capture it did happen correctly as
shown.
__________________________ END OF COMMENT -------------------
In the next section, as it tries to copy the ut* routines
to %ut* routines watch for text that indicates the following:
@ -151,67 +160,120 @@ If this is seen, respond Yes at the prompt after the attempt:
Press ENTER to continue:
Routine: ut Loaded, Saved as %ut
Routine: ut1 Loaded, Saved as %ut1
Routine: utcover Loaded, Saved as %utcover
Routine: utt1 Loaded, Saved as %utt1
Routine: utt2 Loaded, Saved as %utt2
Routine: utt3 Loaded, Saved as %utt3
Routine: utt4 Loaded, Saved as %utt4
Routine: utt5 Loaded, Saved as %utt5
Routine: utt6 Loaded, Saved as %utt6
Routine: uttcovr Loaded, Saved as %uttcovr
-------------------------- START OF COMMENT -------------------
While the conversion of files occurred correctly, the NO
response was still taken to show the output that explains
what the user should do if the files conversion did not
happen.
__________________________ END OF COMMENT -------------------
Your entry on the next line may not echo
If error text was seen enter Y (and RETURN): NO//
------------------ START OF ADDED COMMENT ----------------------
At this point if there were errors renaming the routines, the
following text is displayed. Normally, it will not appear.
------------------- END OF ADDED COMMMENT ----------------------
*** An error occurred during renaming of routines to %ut*.
*** The renaming has been seen to fail on one type of Linux system.
*** In this case, at the Linux command line copy each ut*.m routine
*** (ut.m, ut1.m, utcover.m, utt1.m, utt2.m, utt3.m, utt4.m, utt5.m, utt6.m,
*** and uttcovr.m) to _ut*.m (e.g., 'cp ut.m _ut.m', 'cp ut1.m _ut1.m',
*** 'cp utcover.m _utcover.m', etc., to 'cp uttcovr.m _uttcovr.m'). Then
*** in GT.M use the command 'ZLINK %ut', then 'ZLINK %ut1', etc., these may
*** (ut.m, ut1.m, utt1.m, utt2.m, utt3.m, utt4.m, utt5.m, utt6.m, and
*** uttcovr.m) to _ut*.m (e.g., 'cp ut.m _ut.m', 'cp ut1.m _ut1.m',
*** 'cp utt1.m _utt1.m', etc., to 'cp uttcovr.m _uttcovr.m'). Then in GT.M
*** use the command 'ZLINK %ut', then 'ZLINK %ut1', etc., these may
*** indicate an undefined local variable error, but continue doing it.
*** When complete, use the M command 'DO ^%utt1' to run the unit tests on
*** the %ut and %ut1 routines to confirm they are working
Press Enter to continue:
----------------- END OF HELP MESSAGE FOR PROBLEM -------------------
-------------------------- START OF COMMENT -------------------
That ends the section in which the routine names are being
converted, and what action to take if they aren't converted
correctly.
__________________________ END OF COMMENT -------------------
Updating Routine file...
Updating KIDS files...
MASH*0.3*0 Installed.
Dec 10, 2015@19:03:26
MASH*1.3*0 Installed.
Dec 16, 2015@14:23:52
NO Install Message sent
Install Completed
1 Load a Distribution
2 Verify Checksums in Transport Global
3 Print Transport Global
4 Compare Transport Global to Current System
5 Backup a Transport Global
6 Install Package(s)
Restart Install of Package(s)
Unload a Distribution
Select Installation Option: ^PG Programmer mode
Select Installation <TEST ACCOUNT> Option: ^PG Programmer mode
%GTM-I-BREAK, Break instruction encountered
At M source location PRGMODE+6^%ZOSV
------------------ START OF ADDED COMMENT ----------------------
---- RUNNING THE BASIC UNIT TESTS - Note these do throw expected errors ----
----- Also, GTM invalid function names messages have been removed -----
----- they won't appear in subsequent runs -----
------------------- END OF ADDED COMMMENT ----------------------
GTM>
-------------------------- START OF COMMENT -------------------
The following runs the sequence of unit tests (DOing ^%utt1
from the top runs the code
D EN^%ut($T(+0),1) ; Run tests here, be verbose.
QUIT
which is a good way to set up both development code (e.g., %ut,
%ut1, and %utcover) and unit tests so that starting code from
the top runs the tests. The routines %uttcovr and %utt6 are
special, and run series of tests or coverages when run from
the top.
Once %utt1 is running, due to the routines following an XTROU
tag in it, it also runs the unit tests in %utt2, %utt4,
%utt5, %utt6, and %uttcovr. The XTROU tags could be in each
and a given unit test routine would still be run only once.
To test error handling, and handling of failed tests and other
problems, unlike most unit tests, there are 7 expected failures
and 1 expected error (dividing by zero) in these tests. All of
the other tests which are not indicated as expected failures or
tests, should pass without problems.
__________________________ END OF COMMENT -------------------
GTM>D ^%utt1
-------------------------- START OF COMMENT -------------------
GT.M again identifies any functions, syntax errors, etc. that
it sees in lines of code when they are first run, only the
first few are shown here. They will not show up again when the
routine is run again, and should be ignored.
__________________________ END OF COMMENT -------------------
. I $ZVERSION(1)=2 S D=$SYSTEM.Util.GetEnviron("temp")_"\test.txt" I 1 ; Windows
^-----
At column 7, line 92, source module /home/softhat/VistA-Instance/r/_utt1.m
%GTM-E-INVFCN, Invalid function name
. I $ZVERSION(1)=2 S D=$SYSTEM.Util.GetEnviron("temp")_"\test.txt" I 1 ; Windows
^-----
At column 32, line 92, source module /home/softhat/VistA-Instance/r/_utt1.m
%GTM-E-SPOREOL, Either a space or an end-of-line was expected but not found
I +$SY=0 O D:"NWS" ; Cache new file
^-----
At column 15, line 94, source module /home/softhat/VistA-Instance/r/_utt1.m
%GTM-E-DEVPARUNK, Deviceparameter unknown
VISTA2A>D ^%utt1
T1 - - Make sure Start-up Ran.----------------------------------------- [OK]
T2 - - Make sure Set-up runs.------------------------------------------ [OK]
T3 - - Make sure Teardown runs.---------------------------------------- [OK]
@ -286,137 +348,20 @@ ne from tag, and only not covered...........--------------------------- [OK]
Ran 6 Routines, 37 Entry Tags
Checked 113 tests, with 7 failures and encountered 1 error.
GTM>
------------------ START OF ADDED COMMENT ----------------------
Running the %utt6 routine from the top runs a number of different
entry points as unit tests
------------------- END OF ADDED COMMMENT ----------------------
GTM>
VISTA2A>d ^%utt6
GTM>
--
-------------------------- START OF COMMENT -------------------
%uttcovr runs a series of tests from both the regular code
(e.g., DO EN^%ut("routinename")) as well as by calling other
entry points (e.g., DO ^%ut), so that coverage can be included
for these other entry points. While it is recommended that
__________________________ END OF COMMENT -------------------
RUNNING COMMAND LINE TESTS VIA DOSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
.
T5^%utt1 - Error count check - Intentionally throwing a failure
......
Loading routines to test coverage...
%utt3 .........
Loading routines to test coverage...
%utt3
T1 - Test 1.----------------------------------------------------------- [OK]
T2 - Test 2.----------------------------------------------------------- [OK]
Ran 1 Routine, 2 Entry Tags
Checked 2 tests, with 0 failures and encountered 0 errors.........
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
ON PURPOSE - SHOULD FAIL
BADCHKTF^%utt5 - CHKTF should fail on false value - SET FALSE (0) ON PURPOSE -
SHOULD FAIL
BADERROR^%utt5 - throws an error on purpose - Error: 150372778,BADERROR+6^%utt5
,%GTM-E-EXPR, Expression expected but not found
CALLFAIL^%utt5 - called FAIL to test it - Called FAIL to test it
LEAKSBAD^%utt5 - check leaks with leak - LEAKSBAD TEST - X NOT SPECIFIED VARIABL
E LEAK: X
NVLDARG1^%utt5 - check invalid arg in CHKEQ - NO VALUES INPUT TO CHKEQ^%ut - no
evaluation possible
................................................................................
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
Running command line tests by RUNSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
.
T5^%utt1 - Error count check - Intentionally throwing a failure
......
Loading routines to test coverage...
%utt3 .........
Loading routines to test coverage...
%utt3
T1 - Test 1.----------------------------------------------------------- [OK]
T2 - Test 2.----------------------------------------------------------- [OK]
Ran 1 Routine, 2 Entry Tags
Checked 2 tests, with 0 failures and encountered 0 errors.........
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
ON PURPOSE - SHOULD FAIL
BADCHKTF^%utt5 - CHKTF should fail on false value - SET FALSE (0) ON PURPOSE -
SHOULD FAIL
BADERROR^%utt5 - throws an error on purpose - Error: 150372778,BADERROR+6^%utt5
,%GTM-E-EXPR, Expression expected but not found
CALLFAIL^%utt5 - called FAIL to test it - Called FAIL to test it
LEAKSBAD^%utt5 - check leaks with leak - LEAKSBAD TEST - X NOT SPECIFIED VARIABL
E LEAK: X
NVLDARG1^%utt5 - check invalid arg in CHKEQ - NO VALUES INPUT TO CHKEQ^%ut - no
evaluation possible
................................................................................
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
ON PURPOSE - SHOULD FAIL
BADCHKTF^%utt5 - CHKTF should fail on false value - SET FALSE (0) ON PURPOSE -
SHOULD FAIL
BADERROR^%utt5 - throws an error on purpose - Error: 150372778,BADERROR+6^%utt5
,%GTM-E-EXPR, Expression expected but not found
CALLFAIL^%utt5 - called FAIL to test it - Called FAIL to test it
LEAKSBAD^%utt5 - check leaks with leak - LEAKSBAD TEST - X NOT SPECIFIED VARIABL
E LEAK: X
NVLDARG1^%utt5 - check invalid arg in CHKEQ - NO VALUES INPUT TO CHKEQ^%ut - no
evaluation possible
.
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
NOW RUNNING UNIT TESTS FOR %uttcovr
......................................................................
Ran 1 Routine, 9 Entry Tags
Checked 70 tests, with 0 failures and encountered 0 errors.
NOW RUNNING UNIT TESTS FOR %utt6
.........
Ran 1 Routine, 5 Entry Tags
Checked 9 tests, with 0 failures and encountered 0 errors.
------------------ START OF ADDED COMMENT ----------------------
Running %uttcovr from the top of the routine runs coverage by
calling a number of unit tests from different entry points so
that each of them is included in the analysis. Looking at
this shows how to run many different entry points in one
coverage analysis, as well as removing unit tests that may
have the same base namespace from the displayed analysis.
------------------- END OF ADDED COMMMENT ----------------------
VISTA2A>d ^%uttcovr
GTM>d ^%uttcovr
Loading routines to test coverage...
%ut %ut1 %utcover %utf2hex %utt1 %utt2 %utt3 %utt4 %utt5 %utt6 %uttcovr
@ -457,6 +402,8 @@ Checked 70 tests, with 0 failures and encountered 0 errors.
LEAKSBAD TEST - X NOT SPECIFIED VARIABLE LEAK: X
xxxxxxxxxxxxxxxxxxxx GOING TO COV^%ut FOR %utt5 at 3
Loading routines to test coverage...
%ut1 ....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
@ -481,6 +428,8 @@ Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
xxxxxxxxxxxxxxxxxxxx GOING TO COV^%ut FOR %utt5 at -1
Loading routines to test coverage...
%ut1 ....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
@ -505,6 +454,9 @@ Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
xxxxxxxxxxxxxxxxxxxx GOING TO MULTAPIS for %utt4 and %ut
------------------- RUNNING ^%ut -------------------
RUNNING COMMAND LINE TESTS VIA DOSET^%ut
@ -763,12 +715,6 @@ NOW RUNNING UNIT TESTS FOR %utt6
Ran 1 Routine, 5 Entry Tags
Checked 9 tests, with 0 failures and encountered 0 errors.
------------------ START OF ADDED COMMENT ----------------------
%utt4 contains unit tests to run coverage analysis on the
%utt3 routine from the COV^%ut API, while %uttcovr runs
all of the analyses from the COVERAGE^%utcover API.
------------------- END OF ADDED COMMMENT ----------------------
------------------- RUNNING ^%utt4 -------------------
MAIN - - Test coverage calculations
Loading routines to test coverage...
@ -782,10 +728,12 @@ Checked 2 tests, with 0 failures and encountered 0 errors.....--------- [OK]
Ran 1 Routine, 1 Entry Tag
Checked 4 tests, with 0 failures and encountered 0 errors.
------------ SUMMARY ------------
Ran 2 Routines, 6 Entry Tags
Checked 13 tests, with 0 failures and encountered 0 errors.
Routine %utt3 (73.68%) 14 out of 19 lines covered
- Detailed Breakdown
Tag INTERNAL^%utt3 (40.00%) 2 out of 5 lines covered
@ -804,6 +752,7 @@ Routine %utt3 (73.68%) 14 out of 19 lines covered
Tag TEARDOWN^%utt3 (100.00%) 2 out of 2 lines covered
Tag XTMUNITV^%utt3 ------ 0 out of 0 lines covered
Routine %utt3 (73.68%) 14 out of 19 lines covered
- Summary
Tag INTERNAL^%utt3 (40.00%) 2 out of 5 lines covered
@ -815,11 +764,17 @@ Routine %utt3 (73.68%) 14 out of 19 lines covered
Tag TEARDOWN^%utt3 (100.00%) 2 out of 2 lines covered
Tag XTMUNITV^%utt3 ------ 0 out of 0 lines covered
Routine %utt3 (73.68%) 14 out of 19 lines covered
Overall Analysis 14 out of 19 lines covered (73% coverage)
xxxxxxxxxxxxxxxxxxxx LISTING DATA VIA LIST
Routine %utt3 (73.68%) 14 out of 19 lines covered
- Detailed Breakdown
Tag INTERNAL^%utt3 (40.00%) 2 out of 5 lines covered
@ -838,6 +793,7 @@ Routine %utt3 (73.68%) 14 out of 19 lines covered
Tag TEARDOWN^%utt3 (100.00%) 2 out of 2 lines covered
Tag XTMUNITV^%utt3 ------ 0 out of 0 lines covered
Routine %utt3 (73.68%) 14 out of 19 lines covered
- Summary
Tag INTERNAL^%utt3 (40.00%) 2 out of 5 lines covered
@ -849,11 +805,16 @@ Routine %utt3 (73.68%) 14 out of 19 lines covered
Tag TEARDOWN^%utt3 (100.00%) 2 out of 2 lines covered
Tag XTMUNITV^%utt3 ------ 0 out of 0 lines covered
Routine %utt3 (73.68%) 14 out of 19 lines covered
Overall Analysis 14 out of 19 lines covered (73% coverage)
xxxxxxxxxxxxxxxxxxxx Finished in ENTRY^%uttcovr
------------------- RUNNING VERBOSE^%utt6 -------------------
RUNNING COMMAND LINE TESTS VIA DOSET^%ut
@ -935,6 +896,7 @@ ne from tag, and only not covered...........--------------------------- [OK]
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
Running command line tests by RUNSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
@ -971,6 +933,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
NEWSTYLE - identify new style test indicator functionality.------------ [OK]
@ -1005,10 +968,13 @@ ISUTEST - check ISUTEST inside unit test.------------------------------ [OK]
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
NOW RUNNING UNIT TESTS FOR %uttcovr
RTNANAL - - routine analysis...---------------------------------------- [OK]
COVCOV - - check COVCOV - remove seen lines......---------------------- [OK]
COVRPT...........------------------------------------------------------ [OK]
@ -1026,6 +992,7 @@ Checked 70 tests, with 0 failures and encountered 0 errors.
NOW RUNNING UNIT TESTS FOR %utt6
SETROUS - - generate array with indices of routines to exclude......--- [OK]
CHKCMDLN - check command line processing of %utt5---------------------- [OK]
CHKGUI - check GUI processing of %utt5--------------------------------- [OK]
@ -1073,6 +1040,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
Running command line tests by RUNSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
@ -1109,6 +1077,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
@ -1132,8 +1101,10 @@ evaluation possible
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
NOW RUNNING UNIT TESTS FOR %uttcovr
......................................................................
@ -1186,6 +1157,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
Running command line tests by RUNSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
@ -1222,6 +1194,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
@ -1245,8 +1218,10 @@ evaluation possible
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
NOW RUNNING UNIT TESTS FOR %uttcovr
......................................................................
@ -1381,6 +1356,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
Running command line tests by RUNSET^%ut
....
T5^%utt1 - Error count check - This is an intentional failure.
@ -1417,6 +1393,7 @@ evaluation possible
Ran 7 Routines, 39 Entry Tags
Checked 115 tests, with 7 failures and encountered 1 error.
RUNNING COMMAND LINE UNIT TESTS FOR %utt5
....
BADCHKEQ^%utt5 - CHKEQ should fail on unequal value - <4> vs <3> - SET UNEQUAL
@ -1440,8 +1417,10 @@ evaluation possible
Ran 1 Routine, 11 Entry Tags
Checked 10 tests, with 5 failures and encountered 1 error.
RUNNING UNIT TESTS FOR %utt5 VIA GUI CALLS - Silent
NOW RUNNING UNIT TESTS FOR %uttcovr
......................................................................
@ -1456,10 +1435,12 @@ NOW RUNNING UNIT TESTS FOR %utt6
Ran 1 Routine, 5 Entry Tags
Checked 9 tests, with 0 failures and encountered 0 errors.
------------ SUMMARY ------------
Ran 18 Routines, 112 Entry Tags
Checked 398 tests, with 14 failures and encountered 2 errors.
Routine %ut (100.00%) 256 out of 256 lines covered
- Detailed Breakdown
Tag %ut^%ut (100.00%) 2 out of 2 lines covered
@ -1491,6 +1472,7 @@ Routine %ut (100.00%) 256 out of 256 lines covered
Tag VERBOSE^%ut (100.00%) 7 out of 7 lines covered
Tag VERBOSE1^%ut (100.00%) 4 out of 4 lines covered
Routine %ut1 (84.70%) 227 out of 268 lines covered
- Detailed Breakdown
Tag %ut1^%ut1 (100.00%) 2 out of 2 lines covered
@ -1569,6 +1551,7 @@ otherwises positive number
Tag TOTAGS^%ut1 (100.00%) 13 out of 13 lines covered
Tag UP^%ut1 (100.00%) 1 out of 1 lines covered
Routine %utcover (100.00%) 79 out of 79 lines covered
- Detailed Breakdown
Tag %utcover^%utcover (100.00%) 2 out of 2 lines covered
@ -1579,6 +1562,7 @@ Routine %utcover (100.00%) 79 out of 79 lines covered
Tag SETROUS^%utcover (100.00%) 4 out of 4 lines covered
Tag TRIMDATA^%utcover (100.00%) 3 out of 3 lines covered
Routine %ut (100.00%) 256 out of 256 lines covered
- Summary
Tag %ut^%ut (100.00%) 2 out of 2 lines covered
@ -1610,6 +1594,7 @@ Routine %ut (100.00%) 256 out of 256 lines covered
Tag VERBOSE^%ut (100.00%) 7 out of 7 lines covered
Tag VERBOSE1^%ut (100.00%) 4 out of 4 lines covered
Routine %ut1 (84.70%) 227 out of 268 lines covered
- Summary
Tag %ut1^%ut1 (100.00%) 2 out of 2 lines covered
@ -1635,6 +1620,7 @@ Routine %ut1 (84.70%) 227 out of 268 lines covered
Tag TOTAGS^%ut1 (100.00%) 13 out of 13 lines covered
Tag UP^%ut1 (100.00%) 1 out of 1 lines covered
Routine %utcover (100.00%) 79 out of 79 lines covered
- Summary
Tag %utcover^%utcover (100.00%) 2 out of 2 lines covered
@ -1645,13 +1631,87 @@ Routine %utcover (100.00%) 79 out of 79 lines covered
Tag SETROUS^%utcover (100.00%) 4 out of 4 lines covered
Tag TRIMDATA^%utcover (100.00%) 3 out of 3 lines covered
Routine %ut (100.00%) 256 out of 256 lines covered
Routine %ut1 (84.70%) 227 out of 268 lines covered
Routine %utcover (100.00%) 79 out of 79 lines covered
Overall Analysis 562 out of 603 lines covered (93% coverage)
GTM>
VISTA2A>D H^XUS
-------------------------- START OF COMMENT -------------------
The output presented by the use of COVERAGE^%ut (which is
called by running %uttcovr from the top) presents the overall
result as the last item in the output, with finer detail
available by backing up to earlier parts of the output.
For the verbosity variable values of zero or one only the
totals by routine and total for all routines is shown.
For a verbosity value of two, the coverage for tags within
the routines is shown followed by the totals for each routines
and for all routines. For a value of three (as used above)
the output first shows the routines with coverage by tags,
and if the coverage is less than 100%, then the lines that
were NOT covered during the analysis are listed as well
(as shown above for the routine %ut1), followed by the
output for tags only and for totals.
__________________________ END OF COMMENT -------------------
Logged out at Dec 10, 2015 7:04 pm
VISTA2A>D H^XUS
GTM>d H^XUS
Logged out at Dec 16, 2015 2:24 pm
GTM>d Hz ^XUS
Logged out at Dec 16, 2015 2:24 pm[softhat@softhat-VirtualBox ~]$ exit
exit
Script done on Wed 16 Dec 2015 02:24:47 PM EST

Binary file not shown.

File diff suppressed because it is too large Load Diff

Binary file not shown.

View File

@ -1,8 +1,9 @@
%ut ;VEN-SMH/JLI - PRIMARY PROGRAM FOR M-UNIT TESTING ;12/07/15 15:32
;;0.2;MASH UTILITIES;;;Build 7
; Submitted to OSEHRA Sep 14, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
%ut ;VEN-SMH/JLI - PRIMARY PROGRAM FOR M-UNIT TESTING ;12/16/15 08:40
;;1.3;MASH UTILITIES;;Dec 16, 2015;Build 1
; Submitted to OSEHRA Dec 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Joel L. Ivey as XTMUNIT while working for U.S. Department of Veterans Affairs 2003-2012
; Includes addition of %utVERB and %utBREAK arguments and code related to them as well as other substantial additions authored by Sam Habiel 07/2013?04/2014
; Includes addition of %utVERB and %utBREAK arguments and code related to them as well as other substantial additions authored by Sam Habiel 07/2013-04/2014
; Additional work by Joel L. Ivey 05/14-12/15
;
; This routine and its companion, %ut1, provide the basic functionality for
; running unit tests on parts of M programs either at the command line level

View File

@ -1,9 +1,9 @@
%ut1 ;VEN/SMH/JLI - CONTINUATION OF M-UNIT PROCESSING ;12/07/15 15:34
;;0.3;MASH UTILITIES;;Dec 7, 2015;Build 1
; Submitted to OSEHRA Dec 07, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
%ut1 ;VEN/SMH/JLI - CONTINUATION OF M-UNIT PROCESSING ;12/16/15 08:38
;;1.3;MASH UTILITIES;;Dec 16, 2015;Build 1
; Submitted to OSEHRA Dec 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Joel L. Ivey as XTMUNIT1 while working for U.S. Department of Veterans Affairs 2003-2012
; Includes addition of original COV entry and code related coverage analysis as well as other substantial additions authored by Sam Habiel 07/2013?04/2014
; Additions and modifications made by Joel L. Ivey 05/2014-08/2015
; Additions and modifications made by Joel L. Ivey 05/2014-12/2015
;
D ^%utt6 ; runs unit tests from several perspectives
Q

View File

@ -1,7 +1,7 @@
%utcover ;JLI - generic coverage and unit test runner ;12/07/15 16:36
;;0.2;MASH UTILITIES;;Sep 14, 2015
; Submitted to OSEHRA Sep 14, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Joel L. Ivey
%utcover ;JLI - generic coverage and unit test runner ;12/16/15 08:42
;;1.3;MASH UTILITIES;;Dec 16, 2015;Build 1
; Submitted to OSEHRA Dec 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Joel L. Ivey 08/15. Additional work 08/15-12/15.
;
; Changes: (Moved from %ut and %ut1)
; 130726 SMH - Moved test collection logic from %utUNIT to here (multiple places)

View File

@ -1,8 +1,8 @@
%utt1 ; VEN/SMH-JLI - Testing routines for M-Unit;12/07/15 17:00
;;0.2;MASH UTILITIES;;Sep 14, 2015;Build 7
; Submitted to OSEHRA Sep 14, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Sam H. Habiel 07/2013?04/2014
; Additions and modifications made by Joel L. Ivey 05/2014-08/2015
%utt1 ; VEN/SMH-JLI - Testing routines for M-Unit;12/16/15 08:43
;;1.3;MASH UTILITIES;;Dec 16, 2015;Build 1
; Submitted to OSEHRA Dec 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Sam H. Habiel 07/2013-04/2014
; Additions and modifications made by Joel L. Ivey 05/2014-12/2015
;
; THIS ROUTINE IS THE UNIFIED UNIT TESTER FOR ALL OF M-UNIT.
;

View File

@ -1,8 +1,8 @@
%utt2 ; VEN/SMH - Bad Ass Continuation of Unit Tests;09/14/15 09:38
;;0.2;MASH UTILITIES;;Sep 14, 2015;Build 7
; Submitted to OSEHRA Sep 14, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
%utt2 ; VEN/SMH - Bad Ass Continuation of Unit Tests;12/16/15 08:44
;;1.3;MASH UTILITIES;;Dec 16, 2015;Build 1
; Submitted to OSEHRA Dec 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Sam H. Habiel
; Modifications made by Joel L. Ivey 05/2014-08/2015
; Modifications made by Joel L. Ivey 05/2014-09/2015
;
;
T11 ; @TEST An @TEST Entry point in Another Routine invoked through XTROU offsets

View File

@ -1,7 +1,7 @@
%utt3 ; VEN/SMH-JLI - Unit Tests Coverage Tests;09/14/15 09:38
;;0.2;MASH UTILITIES;;Sep 14, 2015;Build 7
; Submitted to OSEHRA Sep 14, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Sam H. Habiel 07/2013?04/2014
%utt3 ; VEN/SMH-JLI - Unit Tests Coverage Tests;12/16/15 08:45
;;1.3;MASH UTILITIES;;Dec 16, 2015;Build 1
; Submitted to OSEHRA Dec 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Sam H. Habiel 07/2013-04/2014
; Additions and modifications made by Joel L. Ivey 05/2014-08/2015
;
XTMUNITV ; VEN/SMH - Unit Tests Coverage Tests;2014-04-16 7:14 PM

View File

@ -1,7 +1,7 @@
%utt4 ; VEN/SMH/JLI - Coverage Test Runner;12/06/15 19:05
;;0.2;MASH UTILITIES;;Sep 14, 2015;Build 1
; Submitted to OSEHRA Sep 14, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Sam H. Habiel 07/2013?04/2014
%utt4 ; VEN/SMH/JLI - Coverage Test Runner;12/16/15 08:45
;;1.3;MASH UTILITIES;;Dec 16, 2015;Build 1
; Submitted to OSEHRA Dec 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Sam H. Habiel 07/2013-04/2014
; Additions and modifications made by Joel L. Ivey 05/2014-08/2015
;
XTMUNITW ; VEN/SMH - Coverage Test Runner;2014-04-17 3:30 PM

View File

@ -1,7 +1,7 @@
%utt5 ;JLI - test for aspects of MUnit functionality ;09/14/15 09:38
;;0.2;MASH UTILITIES;;Sep 14, 2015;Build 7
; Submitted to OSEHRA Sep 14, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Joel L. Ivey
%utt5 ;JLI - test for aspects of MUnit functionality ;12/16/15 08:47
;;1.3;MASH UTILITIES;;Dec 16, 2015;Build 1
; Submitted to OSEHRA Dec 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Joel L. Ivey 05/2014-12/2015.
;
Q
;

View File

@ -1,7 +1,7 @@
%utt6 ;JLI - Unit tests for MUnit functionality ;12/07/15 16:40
;;0.2;MASH UTILITIES;;Sep 14, 2015;Build 7
; Submitted to OSEHRA Sep 14, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Joel L. Ivey 05/2014-08/2015
%utt6 ;JLI - Unit tests for MUnit functionality ;12/16/15 08:47
;;1.3;MASH UTILITIES;;Dec 16, 2015;Build 1
; Submitted to OSEHRA Dec 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Joel L. Ivey 05/2014-12/2015
;
;
; This routine uses ZZUTJLI2 as a test routine, it does not include the routine as an extension,

View File

@ -1,7 +1,7 @@
%uttcovr ;JIVEYSOFT/JLI - runs coverage tests on %ut and %ut1 routines via unit tests ;12/07/15 16:46
;;0.3;MASH UTILITIES;;Dec 7, 2015;Build 1
; Submitted to OSEHRA Dec 07, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Joel L. Ivey
%uttcovr ;JIVEYSOFT/JLI - runs coverage tests on %ut and %ut1 routines via unit tests ;12/16/15 08:48
;;1.3;MASH UTILITIES;;Dec 16, 2015;Build 1
; Submitted to OSEHRA Dec 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Joel L. Ivey 05/2014-12/2015
;
;
; ZEXCEPT: DTIME - if present the value is Kernel timeout for reads

View File

@ -1,6 +1,6 @@
%utPOST ;VEN-SMH/JLI - post install for M-Unit Test software ;12/13/15 15:36
;;0.3;MASH UTILITIES;;;Build 1
; Submitted to OSEHRA Dec 07, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
%utPOST ;VEN-SMH/JLI - post install for M-Unit Test software ;12/16/15 08:58
;;1.3;MASH UTILITIES;;DEC 16,2015;Build 1
; Submitted to OSEHRA DEC 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Sam H. Habiel 07/2013-04/2014
; Additions and modifications made by Joel L. Ivey 05/2014-08/2015
;

View File

@ -1,7 +1,7 @@
%utPRE ;VEN/SMH/JLI - pre installation routine to set up MASH UTILITIES package and assign %ut routines and globals ;12/13/15 15:35
;;0.3;MASH UTILITIES;;;Build 1
; Submitted to OSEHRA Dec 07, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Sam H. Habiel 07/2013?04/2014
%utPRE ;VEN/SMH/JLI - pre installation routine to set up MASH UTILITIES package and assign %ut routines and globals ;12/16/15 08:59
;;1.3;MASH UTILITIES;;DEC 16, ;Build 1
; Submitted to OSEHRA Dec 16, 2015 by Joel L. Ivey under the Apache 2 license (http://www.apache.org/licenses/LICENSE-2.0.html)
; Original routine authored by Sam H. Habiel 07/2013-04/2014
;
;
; The following is used to create, if it does not exist, the MASH UTILITIES