+>```./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`
+
+The flag shall be followed by a space separated list of app names.
+Example of using a local image for A1 Policy Management Service :
+`--use-local-image A1PMS`
+
+The app names that can use other image are listed in the test engine configuration, see env var `AVAILABLE_IMAGES_OVERRIDE`in file `test/common/testengine-config.sh`
+
+### Temporary overriding env vars in a testprofile
+
+Each release has its own test profile, see files `common/test_env-<release-name>.sh`
+For debugging it is possible to override one or more settings in the profile given to the test script.
+Add the flag and file with env vars to override: `--override <override-environment-filename>`. The desired env vars shall be specified in the same way as in the test profile.
+
+### Use other image builds from external repo for A1PMS or other app
+It is possible to replace images with images from other external repos (other than oran and onap nexus repos).
+Modify the file `common/override_external_a1pms.sh` with the desired values. A login to the image repo may be required prior to running the test.
+Add the flag and the file: `--override common/override_external_a1pms.sh` to the command.
+In addition, tell the test script to use the overridden env vars by adding the flag `--use-external-image A1PMS`