List of possible activities - to be prioritized and transformed into JIRA
Task | Category | Complexity 1: easy 5: very difficult | Priority 1: top priority 5: will probably not do | Load 1: no idea probably very long 5: less than 2 hours | Comments | Resources | Ticket |
---|---|---|---|---|---|---|---|
Rename tests names to be more self-described (like basic_cds -> cds_cba_enrichment) | Test refactoring | 1 | 4 | 5 | [TEST-374] Rename tests names to be more self-described (like basic_cds -> cds_cba_enrichment) - ONAP JIRA | ||
Review healthcheck core components | Test refactoring | 1 | 2 | 5 | [INT-2012] Review healthcheck core components - ONAP JIRA | ||
Switch to DCAE Helm (cloudify deprecation) | Test refactoring | 4 | 1 | 1 | [INT-1895] Migrate DCAE testsuite to use helm based component services - ONAP JIRA | ||
Add test for the loop (basic_loop working name) | New test | 5 | 2 | 1 | [TEST-375] Add test for the loop (basic_loop working name) - ONAP JIRA | ||
Add test for CNF macro instantiation | New test | 3 | 2 | 2 | [TEST-376] Add test for CNF macro instantiation - ONAP JIRA | ||
Test GUI endpoints & document available ONAP’s GUIs | New test | 1 | 3 | 4 | simple end point tests, require a clear agreed list of GUI - No browsing test (just check the GUI are there) | [INT-2013] Test GUI endpoints & document available ONAP’s GUIs - ONAP JIRA | |
Use kubescape tool – deprecate root_pods and unlimited_pods tests | New test | 2 | 3 | 4 | Include kubescape and deprecate old security tests covered by kubescape | [INT-1995] Use kubescape security scan in daily CI - ONAP JIRA | |
Run tests out of “onap” namespace | Test Refactoring | 3 | 3 | 3 | Easy for some tests (already tested), not for others => see Epic Role binding/SA management of the robot cm..still some open questions | [TEST-356] Create tests resources not in ONAP namespace - ONAP JIRA | |
Tern deprecation (use Scancode.io) | New test | 3 | 2 | 3 | Cleanup of Tern, setup web site for scan.io | [INT-2016] Tern deprecation - ONAP JIRA | |
Resiliency tests – memory/cpu node hog, node drain, backup & restore | Test enhancement | 3 | 4 | 3 | Tests provided natively by litmus not tuned and several other built in tests could be added | [INT-2017] Resiliency tests – memory/cpu node hog, node drain, backup & restore - ONAP JIRA | |
Add multi_vnf_ubuntu_macro test | New test | [TEST-370] test multivm is FAIL - ONAP JIRA | |||||
Use testsuite/cds in tests CI (prepare the pythonsdk-tests scenarios) | New test | [TEST-291] Include CDS test suite in Integration testing strategy - ONAP JIRA | |||||
Data-provider tool release | Tooling | Code is in gate, so almost already done...shall we create a test based on the tool? | [INT-2010] Release data-provider - ONAP JIRA | ||||
ONAP k8s CRDs | 5 | 4 | 1 | ||||
Automate use case SON in CI | New test | [INT-2020] Automate SON use case in CI - ONAP JIRA | |||||
Refactor SON use case doc | Doc | [INT-2024] Refactor SON use case doc - ONAP JIRA | |||||
Automate use case 5G Slicing in CI | New test | [INT-2021] Automate 5G Slicing use case in CI - ONAP JIRA | |||||
Refactor 5G Slicing use case doc | Doc | [INT-2025] Refactor 5G Slicing use case doc - ONAP JIRA | |||||
Automate use case CCVPN in CI | New tes | [INT-2022] Automate CCVPN use case in CI - ONAP JIRA | |||||
Refactor CCVPN use case doc | Doc | [INT-2026] Refactor CCVPN use case doc - ONAP JIRA | |||||
Refactor Robot | Test refactoring | long story...open since at least guilin.. | [TEST-318] Refactor robot pod - ONAP JIRA | ||||
AAI stability test | New test | 3 | 2 | 3 | May be faster if existing gatling test is shared with the community | ||
Generate new baseline image | Tooling | 2 | 1 | 4 | Look for seccom new reco, shall we regenerate the python baseline as user-98b79 did to remove GPLv3 components? | [INT-2015] Create python baseline image - ONAP JIRA [INT-2014] Create Java baseline image for Jakarta - ONAP JIRA | |
Update of the user doc | Doc | 1 | 4 | 3 | Update the list of official GUI, do we have an official list? linked ot teh GUI test | [INT-2027] Update of the user doc - ONAP JIRA | |
All ONAP docker contaiers should be run using docker images which are based on the images provided by the integration team | New test | 2 | 2 | 2 | New seccom recommendation is that all new ONAP images has to be based on the Integration images | [INT-2000] All ONAP docker contaiers should be run using docker images which are based on the images provided by the integration team - ONAP JIRA | |
Refactoring of tests due to kafka refactoring | 2 | 1 | 2 | hvves is using hardcoded config value, they shall be now dynamically retrieved from a secret | |||
.... |