Function Test Environment
Introduction
Function test is conducted to verify the functionality of the ONAP A1 Policy functions and other Non-RT RIC as well as the individual components.
A test engine and a number of test script is used as a foundation for the test environment.
The test environment uses docker images both the Non-RT RIC components as well as for the the needed simulators (from OSC). The test scripts support execution both in docker and kubernetes environment.
The basic idea of function test is to run the ONAP A1 Policy functions, test the exposed interfaces, and verify their behaviour using simulators. The test engine and the test scripts controls the behaviour of the simulators but also use the exposed interfaces for test and monitoring.
The test scripts are designed in a way so that the same script can be used for testing of the functionality in the master branch as well as previous release(s).
The majority of the test scripts test one or several aspects of the functionality but there is also test scripts for stability tests over longer period of time (currently 3 days max intensity test).
Test scripts/Test cases
The below table is a list of test cases. All scripts beginning with the letters "FTC" (Function Test Case) are considered test scripts to test functionality. The remaining test scripts are primarily used for demo purposes.
Test case | Policy | Slogan |
---|---|---|
FTC1 | Policy | Sanity test, create service and then create, update and delete a policy using http/https and A1PMS REST with/without SDNC controller |
FTC1_A1PMS_ADAPTER | Policy | Sanity test, create service and then create,update and delete a policy with A1PMS adapter using http/https and A1PMS REST with/without SDNC controller |
FTC10 | Policy | Basic use case, register service, create/update policy, delete policy, de-register service using both STD and OSC interface while mixing REST |
FTC100 | Policy | Full a1pms API walkthrough using a1pms REST and with/without SDNC A1 Controller |
FTC110 | Policy | Testing of service registration timeouts and keepalive |
FTC150 | Policy | Sample tests of the SDNC A1 controller restconf API using http/https (no a1pms) |
FTC300 | Policy | Resync 10000 policies using OSC and STD interface |
FTC310 | Policy | Resync of RIC via changes in the pushed config |
FTC350 | Policy | Change supported policy types and reconfigure rics |
FTC800 | Policy | Create 10000 policies in sequence using http/https and a1pms REST with/without SDNC controller |
FTC805 | Policy | A1PMS Create 10000 policies and restart, test polices persistency |
FTC810 | Policy | Repeatedly create and delete policies in each RICs for 24h (or configured number of days). Via a1pms REST and with SDNC using http or https |
FTC850 | Policy | Create/delete policies in parallel over a number of rics using a number of child process |
FTC900 | Policy | Preparation for test of the Control Panel and the Health Check app - populating a number of ric simulators with types and instances |
PM_DEMO | Policy | Preparation demo setup - populating a number of ric simulators with types and instances |
ONAP_UC | Policy | ONAP Use case REQ-626 |
Note: All test scripts and the associated test environment setup for ONAP is currently jointly managed in the this repo, see subdir "test/auto.test". New tests are added frequently so make sure to check out the repo.