...
Test plans and test suites are source controlled in the integration repo, under integration/test/csit/its own GIT repository located in integration/csit.git (https://gerrit.onap.org/r/gitweb?p=integration/csit.git;a=summary). To get started and follow along, please clone the integration repo to your local environment. If you want to run the CSIT test suites locally, you will also need to have have docker and python installed.
...
- run-csit.sh: the shell script that executes a particular CSIT test suite
- plans/: contains the definitions of what is invoked by each test plan
- tests/: contains the test suites written using the Robot Framework
- scripts/: contains various shared shell scripts that support the test plans
Video Tutorial
System Prerequisites
Make sure that your environment has the following packages installed:
| Code Block | ||
|---|---|---|
| ||
sudo apt install python-pip virtualenv unzip sshuttle netcat libffi-dev libssl-dev docker-compose
sudo pip install robotframework
sudo pip install -U requests
sudo pip install -U robotframework-requests
sudo pip install -U robotframework-httplibrary |
Setting Up the Test
Test plans are defined under the plans/ directory.
...
The CSIT job defined for the sample test plan above is at https://jenkins.onap.org/view/CSIT/job/integration-master-csit-functionality1/.
Please refer to Jenkins -> Configuring Jenkins Jobs on the background information on setting up Jenkins jobs. Roughly speaking, you need to check in a JJB YAML definition for your Jenkins job into the ci-management repo under ci-management/jjb/.
...
And update the project name (line 97) and functionality name (line 1210) as appropriate.
The entries under trigger_jobs lists the jobs whose completion will automatically trigger the execution of this particular CSIT job. You should change this list to include the list of merge jobs that may potentially affect the CSIT test results of this particular test plan.