Project Description

ONAP Automation Testing - portal/SDC

SDC is the ONAP visual modeling and design tool. It creates internal metadata that describes assets used by all ONAP components, both at design time and run time.

The SDC manages the content of a catalog, and logical assemblies of selected catalog items --as needed-- to completely define how and when VNFs are realized in a target environment.  A complete virtual assembly of specific catalog items, together with selected workflows and instance configuration data,  completely defines how the deployment, activation, and life-cycle management of VNFs are accomplished.  Selected sub-assemblies may also be represented in the catalog and may be combined with other catalog items, including other sub-assemblies.

During the latest release retrospective, the ONAP Integration Team has identified 3 areas of improvements:

  1. Integration tests in target deployments using OOM.
  2. Improve robot health check across projects.
  3. More projects added to the CI pipeline and more project-specific testing.

This project will focus to address these improvements defined by the SDC/Portal Projects Teams. For more info have a look at this link.

Work Done During the mentorship program

  1. Preparing the Basic UI Test for SDC and WF-D.
  2. Integrated the Test with the CSIT repository. 
  3. Helped the SDC Team solving the issue  SDC-3181.
  4. Prepared the test for the SDC using the ONAP portal.
  5. Integrated the test with the test suite.         

Basic UI Test for SDC and WF-D:

I worked on SDC and workflow designer to create UI tests for them. The test basically was to test the functionality of the workflow designer with SDC. As working on workflow Designer alone is not sufficient it has to be integrated with the SDC. I spend some time to integrate both of them in my local environment and later created the test after having enough information about the problem. Following is the workflow of the test.

Integration of the test with the CSIT repository

CSIT repo handles all the automated tests and checks on Jenkins. To execute any test it follows a specific format where it creates a virtual environment for your test where it installs all the dependencies for the test, sets up everything automatically by executing the scripts, and then it runs the test and after executing the tests it destroys the environment. following is the Jira ticket and review link to the test.

SDC-3193 - Getting issue details... STATUS



Solving the issue  SDC-3181

SDC-3181 - Getting issue details... STATUS

As mentioned in the Jira ticket after finishing my first test I worked on this ticket for a couple of weeks. The issue was if someone imports the workflow file then Tosca and deployment artifacts were created automatically and workflow artifact chosen from the WF-D catalog should be inside the CSAR as a deployment artifact. But CSAR file was not getting any deployment artifact. I helped the SDC-team to figure out the issue.

Test for the ONAP-Portal

Firstly I was working with SDC and SDC simulator to work on my test but later I had to change the test which should work with the ONAP-Portal through oom gating. The main issue with this was the setup of the environment for OOM and running everything locally in my laptop.later after getting access to the portal I created the test which works through the portal.

Work Due

  1. Shifting all the Junit 4 tests to JUnit 5(half of it is already done by the SDC team)
  2. upgrading the selenium to the newest version in existing tests.

Workflow

  • SDC Setup environment stage.
  • Workflow Designer integration with SDC. 
  • Started Learning RobotFrameWork and selenium to create the tests.
  • Wrote the test for the workflow designer and SDC.
  • Wrote the scripts to integrate the tests with the CSIT repository.
  • Submitted ticket for the review.
  • Started working on the ticket SDC-3181 with the SDC team.
  • Writing tests for the SDC with the ONAP portal. 
  • Started doing set up in my local environment with oom.
  • Getting access for the Winlab and started testing my test on the portal
  • Solving some problem related to the test

Challenges Faced during the program

  • setup problem
  • physical  instrument restrictions
  • complex documentation
  • lab access problem

Insight Gained

The project was very huge and I was very new to the project but later with the help of my mentors, I was able to understand the project really well. lots of time I spend understanding the project, At every step, I encounter something new and mentors were always there to help. I learned about the lots of new technologies I didn't work on before. I learned how to work as a team and what is the best way to work on a large project like ONAP. I am really glad I enrolled in the LFN Mentorship program. I met lots of amazing people and gained a lot of experience from them. I would like to thanks all of my mentors, especially Christophe Closset Ofir Sonsino Xue Gao Julien Bertozzi Sébastien DetermeM Gervasi and all the SDC Community. Thanks for giving this amazing 3 months There was not even a single moment when I felt working alone. Because of your helping nature, I never hesitated to ask any silly question ever. Thanks all of you for always helping me out. 





  • No labels