diff --git a/docs/README_functionaltest.md b/docs/README_functionaltest.md
index dddb45484..0c9b7d5fd 100644
--- a/docs/README_functionaltest.md
+++ b/docs/README_functionaltest.md
@@ -29,10 +29,14 @@ cases.  It also must be loaded after `cfe_assert`.
 To execute tests at startup, the following lines can be added to `cfe_es_startup.scr` on the
 designated test target:
 
-    CFE_LIB, cfe_assert,     CFE_Assert_LibInit, ASSERT_LIB,     0,     0, 0x0, 0;
-    CFE_APP, cfe_testcase,   CFE_TestMain,       CFE_TEST_APP, 100, 16384, 0x0, 0;
+    CFE_LIB, cfe_assert,    CFE_Assert_LibInit,  ASSERT_LIB,    0,    0,      0x0,  0;
+    CFE_APP, cfe_testcase,  CFE_TestMain,        CFE_TEST_APP,  100,  16384,  0x0,  0;
+    CFE_LIB, sample_lib,    SAMPLE_LIB_Init,     SAMPLE_LIB,    0,    0,      0x0,  0;
+    CFE_APP, sample_app,    SAMPLE_APP_Main,     SAMPLE_APP,    50,   16384,  0x0,  0;
 
 It is important that `cfe_assert` is loaded first, as all other test applications depend on
 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.
+a different order than they are listed in the startup script.  It is also worth noting
+that sample_app is included in the startup script by default because the cFE functional
+tests are dependent on it for requirements verification.