Changes between Version 9 and Version 10 of SchedTechManual/ServerChanges1_7

Timestamp:

Jul 10, 2012, 8:27:16 PM (12 years ago)

Author:

Sam Habiel

Comment:

--

SchedTechManual/ServerChanges1_7

@@ -97 +97 @@
 
 === BSDX26 (Update Note on Appointment) ===
+Workflow:
  * Lock appointment
  * Save !^BSDXAPPT(BSDXAPTID) into !^TMP($J)
@@ -111 +112 @@
 
 === BSDX31 (No-show and Undo No-show) ===
+Workflow:
  * Lock appointment
  * Ask PIMS if it is okay to (un)no-show this patient. (Doesn't do anything currently; see TODO below)
@@ -121 +123 @@
 M Error Handling: none, except as a side effect of failure from BSDXAPI, while will trigger the PIMS failure rollback.
 == Unit Test Routines ==
+As part of the changes, comprehensive Unit Test routines were created. They are BSDXUT, BSDXUT1, and BSDXUT2. They assume the existence of patients with DFNs 1 through 5. They handle setting up the Scheduling GUI and Hospital Location files themselves. The Unit Tests are:
+ * UT07!^BSDXUT for Unit Testing BSDX07.
+ * UT08!^BSDXUT1 for Unit Testing BSDX08.
+ * UT26!^BSDXUT1 for Unit Testing BSDX26.
+ * UT29!^BSDXUT1 for Unit Testing BSDX29.
+ * UT31!^BSDXUT1 for Unit Testing BSDX31.
+ * UT25!^BSDXUT2 for Unit Testing BSDX25.
+ * PIMS!^BSDXUT2 for Unit Testing PIMS APIs in BSDXAPI.
+
+All Unit Tests will try to be as silent as possible. If there is an error, it will be printed to the screen.
+
+All tests in each Unit Test routine can be invoked from the top of each routine. To run all unit tests, execute the following. The expected output will be as follows:
+{{{
+GTM>D ^BSDXUT,^BSDXUT1,^BSDXUT2
+Error in -10 in Unlinked Section (existing bug)
+Waiting for 5 seconds for taskman to finish
+Waiting for 5 seconds for taskman to finish
+}}}
 
 == Other Enhancements ==