From 31f4b25f081a09e7442035857aa65e23356535e4 Mon Sep 17 00:00:00 2001 From: morganrol Date: Thu, 6 Jan 2022 14:59:22 +0100 Subject: [PATCH] [TESTCASE] Declare basic_cnf_macro in xtesting New test case (replace basic_cnf) Issue-ID: TEST-379 Signed-off-by: morganrol Change-Id: I6b2b815f4b0d538cfb02dc70f824f77e80e0d112 --- smoke-usecases-pythonsdk/docker/testcases.yaml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/smoke-usecases-pythonsdk/docker/testcases.yaml b/smoke-usecases-pythonsdk/docker/testcases.yaml index a2d10ef..caa94e9 100644 --- a/smoke-usecases-pythonsdk/docker/testcases.yaml +++ b/smoke-usecases-pythonsdk/docker/testcases.yaml @@ -128,3 +128,21 @@ tiers: dependencies: run: name: cds_resource_resolution + - + case_name: basic_cnf_macro + project_name: integration + enabled: true + criteria: 100 + blocking: false + description: >- + Basic CNF macro test. Unlike the Basic Cnf use case, here + we utilize cnf-adapter orchestration path in SO, that does not + require MSB and creates k8s-resources information in AAI. + It has also VSP package that contains only helm package, + in this case Apache server. We utilize here already enriched + CBA and orchestration enables config-deploy process that + performs validation of the state of the deployed Apache + server and does the scaling of replica-count to 2 pods. + dependencies: + run: + name: basic_cnf_macro -- 2.16.6