4 Containerized test environment to run functional tests on CAAS deployments. Test cases are written in python,
\r
5 executed with Robot Framework using Pabot parallel executor for robot.
\r
7 The container will contain the test resources including the helm charts and container images for the test applications,
\r
8 test cases and the scripts needed for the execution.
\r
14 Few config parameters should be set in resources/scripts/include/robot_container.env
\r
16 | ROBOT_CONTAINER_TAG: tag of the executor container
\r
17 | TC_TAG: test cases will be executed indicated with this tag
\r
18 | SUT_IP: controller-1 node IP of the deployment
\r
19 | SKIP_BM_ONBOARD if false test applications onboard will be skipped (this is useful for re-execution)
\r
20 | PASSWORD: password for cloudadmin user
\r
22 These parameters should be set for manual execution, otherwise these are set by the jenkins test job
\r
23 (currently http://jenkins2.mtlab.att-akraino.org/job/Test_cloudtaf_modifications/)
\r
26 Building the environment
\r
27 ------------------------
\r
29 resources/scripts/build-test-containers.sh script builds the test containers located in resources/test_containers/ folder.
\r
31 resources/scripts/robot-test-build.sh script builds the robot executor container
\r
37 resources/scripts/robot-test-run.sh script starts the robot container. The entrypoint is the robot-deployment-test.sh
\r
38 script, this will perform the onboarding of the test application, and execute the test suites parallelly from folder
\r
39 testcases/parallel_suites/.
\r
40 The robot logs will be available in pabot_logs folder.
\r
42 Test cases can be executed separately with command like
\r
43 python -m robot -t "CAAS_BASIC_FUNC_002" --variable floating_ip:<SUT_IP> --loglevel trace ssh_check.robot
\r
44 In this case please check the installed packages in the Dockerfile.
\r
46 Another option is to start the executor container based on the resources/scripts/robot-test-run.sh script overriding the
\r
47 entrypoint with option --entrypoint=/bin/bash