[TESTCASES] Update xtesting testcases.yaml

After the backporting of several patches, the list
of supported use cases in guilin must be updated.
If not the test cannot be triggered

Issue-ID: INT-1884

Signed-off-by: morganrol <morgan.richomme@orange.com>
Change-Id: Ie3320ad783bed4c7068d4125c7c60dedfabbe21c

diff --git a/smoke-usecases-pythonsdk/docker/testcases.yaml b/smoke-usecases-pythonsdk/docker/testcases.yaml
index 2d95d27..3ba0a9b 100644 (file)
--- a/smoke-usecases-pythonsdk/docker/testcases.yaml
+++ b/smoke-usecases-pythonsdk/docker/testcases.yaml
@@ -13,21 +13,23 @@ tiers:
                 criteria: 100
                 blocking: false
                 description: >-
-                    Onboard and instantiate a simple ubuntu16.04 VM VNF
+                    Onboard and instantiate a simple ubuntu20.04 VM
+                    using a_la_carte bpmn
                 dependencies:
                 run:
                     name: basic_vm
             -
-                case_name: clearwater_ims
+                case_name: basic_vm_macro
                 project_name: integration
                 enabled: true
                 criteria: 100
                 blocking: false
                 description: >-
-                    Onboard and instantiate a clearwater IMS VNF
+                    Onboard and instantiate a simple ubuntu20.04 VM
+                    using macro bpmn
                 dependencies:
                 run:
-                    name: clearwater_ims
+                    name: basic_vm_macro
             -
                 case_name: basic_network
                 project_name: integration
@@ -63,3 +65,40 @@ tiers:
                 dependencies:
                 run:
                     name: basic_cds
+            -
+                case_name: basic_onboard
+                project_name: integration
+                enabled: true
+                criteria: 100
+                blocking: false
+                description: >-
+                    Subset of basic_vm that performs only the onbaording part. A random service
+                    name is created to be sure that all the onboard oiperations are performed
+                    The main intereste is for stability tests, we can distinguish onboarding only and full tests.
+                    First basic test on CDS, including the creation of a Nodeport to expose
+                dependencies:
+                run:
+                    name: basic_onboard
+            -
+                case_name: pnf_macro
+                project_name: integration
+                enabled: true
+                criteria: 100
+                blocking: false
+                description: >-
+                    Instantiate a PNF using macro flow. It requires the use of the pnf simulator.
+                dependencies:
+                run:
+                    name: pnf_macro
+            -
+                case_name: basic_clamp
+                project_name: integration
+                enabled: true
+                criteria: 100
+                blocking: false
+                description: >-
+                    Onboard and enrich a model with TCA. Create a loop using
+                    clamp. Distribute the loop to Policy and DCAE.
+                dependencies:
+                run:
+                    name: basic_clamp