Fix #2360, Adds utassert message descriptions to README_Functionaltes…

…t.md

docs/README_functionaltest.md

@@ -36,3 +36,21 @@ It is important that `cfe_assert` is loaded first, as all other test application
 symbols provided in this library.  The order of loading other test cases should not
 matter with respect to symbol resolution, but note that test apps may be executed in
 a different order than they are listed in the startup script.
+
+## Utassert messages
+
+Below are various types of messages that can be generated by a test.
+
+    "ABORT", /**< Test sequence abort (major failure, cannot continue) */
+    "FAIL",  /**< Test case failure status messages */
+    "TSF",   /**< Test Setup Failure (TSF) status messages */
+    "TTF",   /**< Test Teardown Failure (TTF) status messages */
+    "MIR",   /**< Manual Inspection Required (MIR) status messages */
+    "WARN",  /**< Test was unable to run (WARN) status messages (e.g. initial condition wrong) */
+    "N/A",   /**< Test Not Applicable (NA) status messages */
+    "BEGIN", /**< Beginning of test status messages */
+    "END",   /**< End of test status messages */
+    "INFO",  /**< All other informational status messages */
+    "PASS",  /**< Test case passed (normal) status messages */
+    "FLOW",  /**< Other condition checks/messages that record test flow, but are not assertions */
+    "DEBUG", /**< Debugging messages */