aboutsummaryrefslogtreecommitdiffstats
path: root/test/postman/README.md
diff options
context:
space:
mode:
authorRene_Robert <rene.robert@orange.com>2019-07-30 17:11:26 +0200
committerRené ROBERT <rene.robert@orange.com>2019-08-01 06:42:30 +0000
commitf049426bfd8142f0ee9851d7ec6281b5c2b5f2e0 (patch)
tree3ccae4a6e74078824f53b6c49c0e19b2e16910af /test/postman/README.md
parent11b0d73014e1c680591f3989a8d54425f1383a15 (diff)
Issue-ID: INT-1178
updated Postman collection for Dublin Signed-off-by: Rene_Robert <rene.robert@orange.com> Change-Id: I94b9180e86b96f75780854211da67d85acc90d48 (cherry picked from commit 0ebd04f1cbce5640747b6791582c7b8db09ef8ea)
Diffstat (limited to 'test/postman/README.md')
-rw-r--r--test/postman/README.md14
1 files changed, 7 insertions, 7 deletions
diff --git a/test/postman/README.md b/test/postman/README.md
index 2d65158c7..649c5edda 100644
--- a/test/postman/README.md
+++ b/test/postman/README.md
@@ -2,10 +2,10 @@
## Using Postman
-That repository contains 9 Postman collections and 2 environment files.
+That repository contains several Postman collections and 2 environment files.
-They have been tested with Onap Casablanca (they are not compatible with
- Beijing, and there is not guaranty about ONAP "master" as API definition
+They have been tested with Onap Dublin (they are not compatible with
+ Casablanca, and there is not guaranty about ONAP "master" as API definition
can change)
You first need to import all those files into your Postman.
@@ -17,7 +17,7 @@ And you should see all the collections
Each collection is made of several API operations
![postman](./images/collection-detail.png)
-Running all those collections, in the order, from 1 to 8 will create a lot of
+Running all those collections, in the order, from 1 to 10 will create a lot of
objects in ONAP components :
- SDC : vendor, VSP, zip file upload, VF from VSP, Service, add VF to Service
@@ -26,7 +26,7 @@ objects in ONAP components :
- NBI : serviceOrder to add a service instance, serviceOrder to delete a service
instance
-The order is very important because a lot of API request will need the API
+The order is very important because a lot of API requests will need the API
response from the previous operation.
![postman](./images/collection-detail-test.png)
@@ -42,7 +42,7 @@ Before running those collections, once in Postman, you need to have a look
at "globals" environment parameters.
![postman](./images/globals.png)
-All variables that begin by "auto_" must not be change (they will be modified
+All variables that begin by "auto_" must NOT be changed (they will be modified
using API response)
All other variables must be adapted to your needs.
In particular, you need to put your own values for cloud_region_id, tenant_name
@@ -93,6 +93,6 @@ docker run --network="host" --volume="/home/debian/rene/onap-tests/postman:/etc/
docker run --network="host" --volume="/home/debian/rene/onap-tests/postman:/etc/newman" postman/newman:alpine run 10_Service_Order.postman_collection.json --environment integration_test_urls.postman_environment.json --globals globals.postman_globals.json --export-globals globals.postman_globals.json --reporters cli,json --reporter-cli-no-assertions --reporter-cli-no-console
```
-All collections are run, you can see results and you will also obtain result json files in the onap-tests/postamn/newman directory
+All collections are processed, then you can see results and you will also obtain result json files in the onap-tests/postamn/newman directory
Of course you can adapt globals variables in globals.postman_globals.json or change the USECASE=$'ubuntu16' value to onboard any heat template located in onap_tests/templates/heat_files directory