Update Documentation for H-RELEASE

[nonrtric.git] / test / auto-test / README.md

diff --git a/test/auto-test/README.md b/test/auto-test/README.md
index bf43d46..5ea64bc 100644 (file)
--- a/test/auto-test/README.md
+++ b/test/auto-test/README.md
@@ -10,7 +10,7 @@ FTC is short for Function Test Case. In addition, there are also other test scri
 
 To list all test case files with a s short description, do `grep TC_ONELINE_DESCR *.sh` for a complete list.
 
-The requirements, in terms of the execution environment, to run a script or a suite is to have docker, docker-compose and python3 installed (the scripts warns if not installed). As an option, the scripts can also be executed in a Minikube or Kubernetes installation. The additional requirement is to have a clean minikube/kubernetes installation, preferably with the kube dashboard installed.
+The requirements, in terms of the execution environment, to run a script or a suite is to have docker, docker-compose (v2+) and python3 installed (the scripts warns if not installed). As an option, the scripts can also be executed in a Minikube or Kubernetes installation. The additional requirement is to have a clean minikube/kubernetes installation, preferably with the kube dashboard installed.
 The scripts have been tested to work on both MacOS and Ubuntu using docker. They should work also in git-bash on windows (for docker) but only partly verified. Running using minikube has only been verified on Ubuntu and running on kubernetes has been verified on MacOS and Ubuntu. Successful sample tests has been made on google cloud.
 
 ## Configuration
@@ -34,7 +34,7 @@ The test scripts produce quite a number of logs; all container logs, a log of al
 
 To test all components on a very basic level, run the demo test script(s) for the desired release.
 Note that oran tests only include components from oran (exception is the onap sdnc).
-Note that onap test uses components from onap combined with released oran components available at that onap release (e.g. London contains onap images from London and oran images (released images from g-release).
+Note that onap test uses components from onap combined with released oran components available at that onap release (e.g. London contains onap images from London and oran images (released images from h-release).
 
 In general, the test scripts support the current ongoing release as well as two previous releases.
 
@@ -51,11 +51,11 @@ ORAN G-RELEASE
 
 >```./PM_EI_DEMO.sh remote-remove  kube  release  --env-file ../common/test_env-oran-g-release.sh  --use-release-image SDNC```
 
-ORAN H-RELEASE - current on master (may 2023 - release image does not exist yet)
+ORAN H-RELEASE
 =========
->```./PM_EI_DEMO.sh remote-remove  docker  --env-file ../common/test_env-oran-h-release.sh```
+>```./PM_EI_DEMO.sh remote-remove  docker  --env-file ../common/test_env-oran-h-release.sh --use-release-image SDNC```
 
->```./PM_EI_DEMO.sh remote-remove  kube  --env-file ../common/test_env-oran-h-release.sh```
+>```./PM_EI_DEMO.sh remote-remove  kube  --env-file ../common/test_env-oran-h-release.sh --use-release-image SDNC```
 
 
 ONAP JAKARTA
@@ -72,7 +72,7 @@ ONAP KOHN
 >```./PM_EI_DEMO.sh remote-remove  kube  release  --env-file ../common/test_env-onap-kohn.sh```
 
 
-ONAP LONDON - current on master (may 2023 - release image does not exist yet)
+ONAP LONDON
 =============
 >```./PM_EI_DEMO.sh remote-remove  docker  --env-file ../common/test_env-onap-london.sh```