Create Smoke/ E2E robot testcase ensuring that blueprint deployment is successful with usage of config map in kubernetes environment.

Goal:

• add new test suite with 3 new robot test cases to test suite repo
  • first - deploy DCAE simple application without config map in config spec json - This test checks if old functionality is working well. If operator is able to deploy DCAE application using DCAE MOD without config map definition
  • second - deploy DCAE simple application with config map in config spec json but not present in k8s - This test checks if new functionality is working well. If operator is able to deploy DCAE application using DCAE MOD with config map definition in config spec json but not in k8s. Verify if deployed DCAE application hasn't got mounted config map.
  • third - deploy DCAE simple application with config map in config spec json and in k8s - This test checks if new functionality is working well. If operator is able to deploy DCAE application using DCAE MOD with config map definition and config map present in k8s. Verify if deployed DCAE application has mounted config map and verify data in mounted config map.
• add test cases with tag DCAE_MOD
• add appropriate keywords and assets to testsuite repo
• config map in k8s can be created using kubectl commandline, that is present in robot pod
• add DCAE mod endpoints, users, passwords global variables if they are not defined in robot pod (add them to robot_resources.py configmap in OOM repo dedicated for robot)
• reuse already existing keywords for blueprint inventory and deployment.
• after test cases execution tear down all artifacts created during test case run: DCAE applications, blueprints etc..

COS:

• all chnges in xtesting repo, OOM repo, test suite repo are reviewed and merged and working
• E2E DCAE MOD test cases present and successfully executed using robot tool in ONAP in Honolulu release.