-When building SDC dockers part of the dockers that will be built are the dockers that responsible for running automation tests in the local environment.
-
-In order to run the automation tests when starting the dockers on the machine there are 2 falgs to use:
-
-* -tad - Use this flag to run the default suite of API tests
-* -tud - Use this flag to run the default suite of UI tests
-
-You can go to this link to view all the commands in the vagrant-onap: [Vagrant Common Commands](https://wiki.onap.org/display/DW/SDC+Vagrant+Common+Commands)
-
-And to this guide regarding using the docker run script: [SDC docker_run Script Usage](https://wiki.onap.org/display/DW/SDC+docker_run+Script+Usage)
-
-For more information regarding testing the project please refer to the following guide: [SDC Sanity](https://wiki.onap.org/display/DW/SDC+Sanity)
+### Accessing the logs
+
+To access the logs, there are different options:
+* Connect to the docker container you want to inspect by doing `docker exec -it -u root sdc-XXXXXXXX-1 sh`
+ * Then look at the logs generally in /var/lib/jetty/logs or /var/log/onap (that may differ !)
+* A volume is shared between the BE, onboard-BE and FE containers, this volume is mapped to `/tmp/sdc-integration-tests`,
+ * In that folder you can obtain the logs of the different containers
+
+### Debugging SDC
+
+After having started SDC with the command `mvn clean install -P start-sdc`, different java remote debug ports are opened by default:
+* Onboard Backend - 4001 (jetty)
+* Backend - 4000 (jetty)
+* Frontend - 6000 (jetty)
+It's therefore possible to connect your IDE to those debug ports remotely to walk through the code and add some breakpoints.
+
+**Look at the pom.xml of the integration-tests module to have a better understanding of all the docker settings provided to start SDC.**
+
+### Integration tests
+The integration are composed of 2 parts, one to test the BE Apis and another one to test the FE with selenium.
+
+The selenium tests make use of the selenium/standalone-firefox:2.53.1 container.
+
+About BE APIs tests, onboarding E2E flow :
+Onboarding E2E flow cover following SDC functionality:
+
+ Onboard of VNF
+ Create VF from VSP
+ Certify VF
+ Create Service
+ Add VF to service
+
+ Certify Service
+ Export TOSCA and validate it structure using external TOSCA parser
+
+**as part of execution we open a connection to Titan and perform resources clean up both before and after tests execution (only resource with “ci” prefix will be deleted from the catalog)
+List of VNFs/PNFs that proceed by onboarding flow, located in `integration-tests/src/test/resources/Files/`)
+
+ sample-signed-pnf-cms-includes-cert-1.0.1-SNAPSHOT.zip
+ sample-signed-pnf-1.0.1-SNAPSHOT.zip
+ sample-pnf-1.0.1-SNAPSHOT.csar
+ sample-pnf-custom-type.csar
+ base_vfw.zi
+ base_vvg.zip
+ database-substitution-mappings.csar
+ helm.zip
+ Huawei_vHSS.csar
+ Huawei_vMME.csar
+ infra.zip
+ resource-ZteEpcMmeVf-csar_fix.csar
+ vbng.zip
+ vbrgemu.zip
+ vfw.zip
+ vgmux.zip
+ vgw.zip
+ vLB.zip
+ vLBMS.zip
+ vSBC_update_v03.csar
+ vsp-vgw.csar
+ vvg.zip
+ ZteEpcMmeVf.csar
+
+#### Start the integration tests manually
+
+Those tests execute the following
+There are 2 options to start them:
+* After having started SDC with the command `mvn clean install -P start-sdc`, run the command `mvn clean install -P run-integration-tests`
+* If you want to debug them and run them from your IDE, you must start them from the testNG Suites files, otherwise this won't work.
+ The test suites are located here:
+ * BE: `integration-tests/src/test/resources/ci/testSuites/backend`
+ * FE: `integration-tests/src/test/resources/ci/testSuites/frontend`
+
+#### Integration tests with Helm Validator
+
+Those tests use container built externally in other ONAP repository: [sdc/sdc-helm-validator](https://gerrit.onap.org/r/admin/repos/sdc/sdc-helm-validator)
+
+You can run those tests same as default integration tests by adding additional profile to maven commands:
+`integration-tests-with-helm-validator`
+* To start SDC with Helm Validator run: `mvn clean install -P start-sdc,integration-tests-with-helm-validator`
+* To execute tests that use Helm Validator use: `mvn clean install -P run-integration-tests,integration-tests-with-helm-validator`
+## Accessing SDC UI in Dev Mode (Legacy way)
+
+In order to access the SDC UI from your dev environment you need to do the following:
+
+1. Go to file `webpack.server.js` found under the catalog-ui folder in the main sdc project and update the "localhost" variable to be the ip of your local vagrant machine.
+2. Navigate to the catalog-ui folder and run the command: `npm start -- --env.role <wanted_role>` with the wanted role to login to SDC as.