adjust readme and red.xml

the readme should not duplicate the dev guide, and the red.xml should
have all the stuff that we offer

Change-Id: I459b6bae7fdd6c2060e5662f34b9ea4a163ce109
Issue-ID: TEST-146
Signed-off-by: DR695H <dr695h@att.com>

1 files changed, 2 insertions, 35 deletions

diff --git a/README.md b/README.md
index f580a494..75c7d67a 100644
--- a/README.md
+++ b/README.md
@@ -2,6 +2,8 @@
 ## Prerequisites
 This guide assumes you have run git clone on https://gerrit.onap.org/r/p/testsuite.git
 
+For more info please see the [Development Guide](https://wiki.onap.org/display/DW/Robot+Framework+Development+Guide)
+
 ## Development Environment Setup
 ### Python Installation
 You should install 2.7.12: [https://www.python.org/downloads/release/python-2712](https://www.python.org/downloads/release/python-2712)
@@ -59,41 +61,6 @@ Windows and Mac hosts will download into the current working directory. Windows
 in the execution PATH.
 
 
-## Robot Project Structure
-### Overview
-ProjectName - robot
-
-```
-`-- robot
-    |-- assets - put anything you need as input like json files, cert keys, heat templates
-    |   |-- templates - put any json templates in here, you can include subfolders for each component
-    |-- library - put any python libraries need to run tests in here
-    |   |-- eteutils - put any python code libraries we write in here
-    |-- resources - put any robot resource files aka libraries we write in here
-    |   |-- aai
-    |   `-- vid
-    `-- testsuites - put any robot test suites we write in here
-```    
-
-### Tag Strucutre
-Robot uses tags to separate out test cases to run. below are the tags we use
-
-* garbage - use this for test cases that should be cleaned up before go live date
-* health - use this for test cases that perform a health check of the environment
-* smoke - use this for test cases that perform a basic check of a component
-* ete - use this for the test cases that are performing an end to end test
-
-## Branching Structure
-### Overview
-Repository Name: testsuite
-
-Branching strategy:
-```
-`-- testsuite
-    |-- master - the main branch and always the latest deployable code. Send a pull to here from feature and Dan or Jerry will approve.
-    |-- feature-[XXXXXX] - when you want to make changes you make them here, when you are satisfied send pull request to master
-```    
-
 ## Executing ETE Testcases
 ### Overview
 Two scripts have been provided in the root of the ete-testsuite project to enable test execution