Update to 0.5.0.

README.md

@@ -2,7 +2,7 @@
 holoscan-test-suite provides a very simple web server that runs test scripts and
 publishes the results as HTML back to the calling browser.
 
-holoscan-test-controls leverages tools in holoscan-test-suite to provide an
+holoscan-test-suite-controls leverages tools in holoscan-test-suite to provide an
 interactive web UI to enable various runtime behaviors on demand.  This is
 useful in the context of, say, EMR or thermal characterization: you can start
 with a quiet system, measure RF emissions, then gradually turn on features, and
@@ -51,7 +51,7 @@ In the src directory, you'll find
   two command-line parameters: the name of the module with the identify()
   routine and the name of the pytest module (without the .py suffix):
 
-        python3 flask_wrapper (configuration)\_report test\_(configuration)
+        python3 flask_wrapper (configuration)_report test_(configuration)
 
     The web server is configured to listen on any local network interface on
     TCP port 8765.  Press control/C to terminate this application.
@@ -71,34 +71,28 @@ Adding a new test is easy:
 - Add that script to test\_(configuration).py
 - Kill and restart the run\_(configuration).sh script.
 
-For Yocto applications, you can include testing by
+For systems running the Holoscan Deployment stack using
+[meta-tegra-holoscan](https://github.com/nvidia-holoscan/meta-tegra-holoscan),
+you can include testing by adding
+`CORE_IMAGE_EXTRA_INSTALL:append = " holoscan-test-suite"` to
+build/conf/local.conf (don't forget the space after the double quote:
+" holoscan-test-suite").
 
-- Clone this project into a directory next to meta-tegra-clara-holoscan-mgx.
-  From the build container's perspective, this will be in
-  /workspace/holoscan-test-suite.
-- Add "/workspace/holoscan-test-suite/meta-holoscan-test-suite" to
-  build/conf/bblayers.conf
-- Add "CORE\_IMAGE\_EXTRA\_INSTALL:append = " holoscan-test-suite"" to
-  build/conf/local.conf (don't forget the space after the double quote:
-  " holoscan-test-suite")
-
-To add holoscan-test-controls,
-- Add "/workspace/holoscan-test-suite/meta-holoscan-test-controls" to
-  build/conf/bblayers.conf
-- Add "CORE\_IMAGE\_EXTRA\_INSTALL:append = " holoscan-test-controls"" to
-  build/conf/local.conf (don't forget the space after the double quote:
-  " holoscan-test-controls")
+To add holoscan-test-suite-controls, add
+`CORE_IMAGE_EXTRA_INSTALL:append = " holoscan-test-suite-controls"` to
+build/conf/local.conf (don't forget the space after the double quote:
+" holoscan-test-suite-controls").
 
 Then use your usual commands to build your image (e.g. bitbake.sh) and flash
 your system (e.g. flash.sh).
 
 With this, the server will start at boot; you can use your browser to run
-holoscan-test-suite by going to "http://\<ip\>:8765"; if you've enabled
-holoscan-test-controls, that is accessable by "http://\<ip\>:8767".  You can
+holoscan-test-suite by going to `http://<ip>:8765`; if you've enabled
+holoscan-test-suite-controls, that is accessable by `http://<ip>:8767`.  You can
 observe the console for holoscan-test-suite by running the command "screen -d -r
 holoscan-test-suite", which may be useful when developing new tests.  If you're
 developing new tests, you may want to "systemctl stop holoscan-test-suite", then
 you can directly execute "run\_(configuration).sh" in your shell.  The console
-for holoscan-test-controls is available by "screen -d -r
-holoscan-test-controls".
+for holoscan-test-suite-controls is available by "screen -d -r
+holoscan-test-suite-controls".