X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=test%2Fauto-test%2FREADME.md;h=76858fe8c711b9a41f25546ae6f41fccfd78cc3e;hb=dfdca185681554d67b63ec37ed19954654223e46;hp=1f8ef5d682321cfeb35b2f90a0d7aa67468b12c6;hpb=d0c7f9207203ce9a502fc15c09f9938eebfd44f7;p=nonrtric.git

diff --git a/test/auto-test/README.md b/test/auto-test/README.md
index 1f8ef5d6..76858fe8 100644
--- a/test/auto-test/README.md
+++ b/test/auto-test/README.md
@@ -48,9 +48,12 @@ ORAN D-RELEASE
 
 ORAN E-RELEASE
 =========
->```./PM_EI_DEMO.sh remote-remove  docker  --env-file ../common/test_env-oran-e-release.sh```
+>```./PM_EI_DEMO.sh remote-remove  docker  release  --env-file ../common/test_env-oran-e-release.sh```
 
->```./PM_EI_DEMO.sh remote-remove  kube  --env-file ../common/test_env-oran-e-release.sh```
+>```./PM_EI_DEMO.sh remote-remove  kube  release --env-file ../common/test_env-oran-e-release.sh```
+
+ORAN E-RELEASE with nonrtric deployed with helm charts for the "dep" repo
+>```../FTC_HELM_E_RELEASE.sh remote-remove  kube  release --env-file ../common/test_env-oran-e-release.sh --override override_ftc_helm_e_release.sh```
 
 ONAP GUILIN
 ===========
@@ -58,7 +61,7 @@ ONAP GUILIN
 
 >```./PM_DEMO.sh remote-remove  kube  release --env-file ../common/test_env-onap-guilin.sh```
 
-Note that ECS was not available before oran cherry so a test script without ECS is used.
+Note that ICS was not available before oran cherry so a test script without ICS is used.
 
 ONAP HONOLULU
 =============
@@ -72,11 +75,10 @@ ONAP ISTANBUL
 
 >```./PM_EI_DEMO.sh remote-remove  kube  release  --env-file ../common/test_env-onap-istanbul.sh```
 
-Note: When istanbul is released, add the 'release' arg to run released images.
 
 ## Test case categories
 
-The test script are number using these basic categories where 0-999 are releated to the policy managment and 1000-1999 are related to enrichment management. 2000-2999 are for southbound http proxy. There are also demo test cases that test more or less all components. These test scripts does not use the numbering scheme below.
+The test script are number using these basic categories where 0-999 are releated to the policy managment and 1000-1999 are related to information management. 2000-2999 are for southbound http proxy. There are also demo test cases that test more or less all components. These test scripts does not use the numbering scheme below.
 
 The numbering in each series corresponds to the following groupings
 1-99 - Basic sanity tests
@@ -89,9 +91,9 @@ The numbering in each series corresponds to the following groupings
 
 900-999 - Misc test
 
-11XX - ECS API Tests
+11XX - ICS API Tests
 
-18XX - ECS Stability and capacity test
+18XX - ICS Stability and capacity test
 
 2000 - Southbound http proxy tests
 
@@ -127,8 +129,7 @@ SUPPORTED_RUNMODES=<List of runmodes, DOCKER and/or KUBE>
 
 CONDITIONALLY_IGNORED_IMAGES=<list of images to exclude if it does not exist in the profile file>
 
-. ../common/testcase_common.sh  $@
-< other scripts need to be sourced for specific interfaces>
+. ../common/testcase_common.sh $@
 
 setup_testenvironment