This version includes a number of changes
recognition of Cache system even if computer name begins with digits
addition of verbosity value to give execution times in fractional milliseconds - in GT.M this requires versions 6.3 and above
for COV^%ut and COVERAGE^%ut the first argument is now passed by reference and may be used to produce coverage on multiple namespaces, or specify specific routines to be analyzed
M-Unit no longer depends on the presence of VistA components, and can be run in Cache or GT.M by itself
If the BREAK (optional third argument for EN^%ut) is true, on breaking the type of error or cause for breaking is specified before the BREAK occurs
Signed-off-by: JOEL IVEY <jivey@jiveysoft.com>
Adds listing of times for unit tests to execute with VERBOSE value set
to 2. Corrects potential problems on Cache in setting global and
routine namespaces for %ut in the current account. Removes excess
verbiage from GT.M installations.
The PRE-INSTALL routine ZZUTPRE was modified to replace calls which were
marked as DEPRECATED and to be removed in the future, with the
recommended calls to replace those.
Updated 3rd line of routines (previously 4th line) to indicate
submission to OSEHRA and to show information about license.
Added comments to Manual text concerning: 1) use of NMSPU as unit test
namespace instead of ZZUT as well as including unit tests in
distributions; 2) need for rapid running unit tests and identifying and
fixing slow tests.
Changes to functionality include:
STARTUP and SHUTDOWN will be run in each routine instead of the first
instance of STARTUP and SHUTDOWN encountered being the only ones that
were run. This change was made because of possible suites of tests
which have their own STARTUP and SHUTDOWN that need to be run. Also, it
does not depend on the order in which test routines are run.
While the coverage functionality can only be run on GT.M systems at the
present time, the routine %utcover has been added to provide additional
ability to run a number of unit tests at one time so that coverage
across all of them can be obtained in one run, this includes
the ability to specify entry at different APIs (e.g., if both verbose
and nonverbose entries are available) as well as run code which is not
part of a unit test to include in the analysis. The routine %uttcovr
uses this functionality to provide a means of doing coverage analysis on
the %ut routines and can be used as an example of its usage.
A new tag (COV) has been added to the %ut routine (it simply calls the
one in %ut1) so that all user APIs can be accessed within the %ut
routine.
A potential problem with setting up the %ut namespace in the local
instance was addressed by Sam Habiel in the preinstall routine ZZUTPRE.
JOEL IVEY
Linda Yaw
JOEL IVEY
Christopher Edwards
Sam Habiel