Integration Team,

Where is the documentation on how to add a robot test to external lab jobs?

I don’t see any documentation in the Integration wiki except for creating a CSIT for the project.

I don’t see any robot code in the integration repo. The integration/csit repo is only for individual projects.

I went back into the PTL meetings and could not find any details.

Regards,

Pam

Robot code has always been in the testsuite repo.

We havent had alot of requests for how to add new robot test cases outside of the integration team so here is a work in progress.

1. Start with what key words you want to add for your testing by looking at the project interface and create a new robot file if that makes sense to combine higher level function. For policy there is a testsuite/robot/resources/policy_interface.robot for basic communications of GET/PUT/POST etc.
2. For new functions we would like to create a sub-directory and put new project specific robot Keywords in robot files there.
   1. For example policy_csit_test.robot would be /testsuite/robot/resources/policy/policy_csit_test.robot
   2. We will likely move the policy_interface.robot to the sub-directory over time like we have done for AAI for its interface.
3. If you need a new template for PUT/POST buffers put them in testsuite/robot/assets/test_templates
4. If you need new global variables (should not be needed) they need to go in one of the 3 coniguration files and put into the resources in oom helm charts.
5. If you plan to use a test template they are in testsuites/robot/resources/test_templates
   1. These robot files are for re-useable logic like doing the same steps for different VNFs.
   2. I think this is less likely to be used for CSIT tests.
6. Tie the keywords into a test case in the testsuite/robot/testsuites directory
   1. For CSIT you probably should create a csit_policy.robot testsuite and add the TAG csit or policy_csit
7. The jenkins job would then run ./ete-k8s.sh onap csit or ./ete-k8.sh onap csit_policy

Questions/comments encouraged.

Brian

Pam,

I added one agenda about ONAP integration test (including Robot) in  the coming ONAP subcommittee meeting. Let me talk to Brian to see if we can arrange a separate meeting earlier to address the community needs.

Regards,

-Yang

Ahh- ok now I remember J

Thanks Brian!!

I will pass this on to my team and we will provide feedback back.

Thanks again!!

Pam

Robot code has always been in the testsuite repo.

We havent had alot of requests for how to add new robot test cases outside of the integration team so here is a work in progress.

1. Start with what key words you want to add for your testing by looking at the project interface and create a new robot file if that makes sense to combine higher level function. For policy there is a testsuite/robot/resources/policy_interface.robot for basic communications of GET/PUT/POST etc.
2. For new functions we would like to create a sub-directory and put new project specific robot Keywords in robot files there.
   1. For example policy_csit_test.robot would be /testsuite/robot/resources/policy/policy_csit_test.robot
   2. We will likely move the policy_interface.robot to the sub-directory over time like we have done for AAI for its interface.
3. If you need a new template for PUT/POST buffers put them in testsuite/robot/assets/test_templates
4. If you need new global variables (should not be needed) they need to go in one of the 3 coniguration files and put into the resources in oom helm charts.
5. If you plan to use a test template they are in testsuites/robot/resources/test_templates
   1. These robot files are for re-useable logic like doing the same steps for different VNFs.
   2. I think this is less likely to be used for CSIT tests.
6. Tie the keywords into a test case in the testsuite/robot/testsuites directory
   1. For CSIT you probably should create a csit_policy.robot testsuite and add the TAG csit or policy_csit
7. The jenkins job would then run ./ete-k8s.sh onap csit or ./ete-k8.sh onap csit_policy

Questions/comments encouraged.

Brian