+There are two types of scripts, filenames in the format FTCXXX.sh test one or more components of the Non-RT RIC. Filenames in the format SuiteZZZZ.sh tests a number of FTCXXX.sh script as one suite. (XXX is an integer selected from the categories described further below).
+FTC is short for Function Test Case. In addition, there are also other test scripts with other naming format used for demo setup etc (e.g PM_DEMO.sh).
+
+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 (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
+
+The test scripts uses configuration from a single profile file, found in `../common/test_env-*.sh`, which contains all needed configuration in terms of image names, image tags, ports, file paths, passwords etc. There is one profile file for system (ORAN/ONAP) and release.
+If temporary changes are needed to the settings in a profile file, use an override file containing only the variable to override.
+
+## How to run
+
+A test script, for example FTC1, is executed from the cmd line using the script filename and one or more parameters:
+
+ >```./FTC1.sh remote docker --env-file ../common/test_env-oran-i-release.sh```
+
+Note that this script will use the staging images. Once the release images are available,add the parameter "release" to run with released images.
+
+See the README.md in `../common/` for all details about available parameters and their meaning.
+
+Each test script prints out the overall result of the tests in the end of the execution.
+
+The test scripts produce quite a number of logs; all container logs, a log of all http/https calls from the test scripts including the payload, some configuration created during test and also a test case log (same as what is printed on the screen during execution). All these logs are stored in `logs/FTCXXX/` - basically in a dir with the same name as the script. So each test script is using its own log directory. If the same test is started again, any existing logs will be moved to a subdirectory called `previous`.
+
+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. Montreal contains onap images from Montreal and oran images (released images from i-release).
+
+In general, the test scripts support the current ongoing release as well as two previous releases.
+
+
+ORAN G-RELEASE
+=========
+>```./PM_EI_DEMO.sh remote-remove docker release --env-file ../common/test_env-oran-g-release.sh --use-release-image SDNC```
+
+>```./PM_EI_DEMO.sh remote-remove kube release --env-file ../common/test_env-oran-g-release.sh --use-release-image SDNC```
+
+ORAN H-RELEASE
+=========
+>```./PM_EI_DEMO.sh remote-remove docker release --env-file ../common/test_env-oran-h-release.sh --use-release-image SDNC```
+
+>```./PM_EI_DEMO.sh remote-remove kube release --env-file ../common/test_env-oran-h-release.sh --use-release-image SDNC```
+
+ORAN I-RELEASE
+=========
+>```./PM_EI_DEMO.sh remote-remove docker --env-file ../common/test_env-oran-i-release.sh --use-release-image SDNC```
+
+>```./PM_EI_DEMO.sh remote-remove kube --env-file ../common/test_env-oran-i-release.sh --use-release-image SDNC```
+
+
+ONAP KOHN
+=============
+>```./PM_EI_DEMO.sh remote-remove docker release --env-file ../common/test_env-onap-kohn.sh```
+
+>```./PM_EI_DEMO.sh remote-remove kube release --env-file ../common/test_env-onap-kohn.sh```
+
+
+ONAP LONDON
+=============
+>```./PM_EI_DEMO.sh remote-remove docker release --env-file ../common/test_env-onap-london.sh```
+
+>```./PM_EI_DEMO.sh remote-remove kube release --env-file ../common/test_env-onap-london.sh```
+
+
+ONAP MONTREAL
+=============
+>```./PM_EI_DEMO.sh remote-remove docker --env-file ../common/test_env-onap-montreal.sh```
+
+>```./PM_EI_DEMO.sh remote-remove kube --env-file ../common/test_env-onap-montreal.sh```
+
+
+## Useful features
+
+There are a fair amount of additional flags that can be used to configure the test setup. See a detailed descriptions of all flags in `test/common/README.md`.
+
+
+### Stop at first error
+In general, the test script will continue to try to make all tests even if there are failures. For debugging it might be needed to stop when the first test fails. In this case, add the flag below to stop test execution at the first failed test:
+`--stop-at-error`
+
+### Test released images
+
+Tests are normally carried out on staging images. However, for testing the released images (when the images are available in the nexus report) the flag `release` shall be added to command. See also the below section to further tailor which image version (local/staging/snapshot) to use.
+
+### Use other image builds
+As default, all tests of the project images are carried out on the staging images (unless the `release` flag is given - then released versions of the project images are used).
+In some cases, for example a locally built image or a snapshot image for one or more components can be used for testing together with staging or released images.
+
+The following flags can be used to switch image for one more individual components to use local image, remote snapshot image, remote staging image or or remote release image.
+
+`--use-local-image`
+`--use-snapshot-image`
+`--use-staging-image`
+`--use-release-image`