Status of verification jobs related to Integration repositories
| Repository | Verification job | tests | linting | comments | Jira tasks | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| integration | No | No | No | manual pylint:1.75/10 code coverage: 0 |
| ||||||||||||||||
| integration/csit | Yes | Yes | No | launch CSIT tests of the project involved in the patch | |||||||||||||||||
| integration/docker | No | No | No | docker build, chains need created to build docker and push them to nexus or docker hub | |||||||||||||||||
| integration/xtesting | No | No | No | docker build chain needed to build docker and push them to nexus or docker hub | |||||||||||||||||
| testsuite | Yes | No | No | 3scm-docker-shell-daily? Build of the robot docker We could add robot lint | |||||||||||||||||
| testsuite/oom | No | Yes | No | no helm lint or tests JobDeployer (Gating) |
| ||||||||||||||||
| testsuite/heatbridge | Yes | Yes* | No | no helm lint or tests | |||||||||||||||||
| testsuite/testing-python-utils | Yes | Yes | No | *: test target but 0 test pylint available in tox pylint launched manually score 0.34/10 | |||||||||||||||||
| demo | Yes | ?? | No | verify-java launched manually score VES5.0: 4.4/10 DAaS: 1.65/10 |
Notes
- integration/benchmark and integration/devtool are archived
- integration/seccom is not managed by us
- integration/simulators/ran-simulator is empty for the moment (request from 5G-SON for Frankfurt)
- testsuite/properties to be archieved soon: files have been relocated
- in demo we can find python, java, c and lot of descriptor files, the README does not seem very up to date (ref to Beijing)
the pylint rate and code coverage is globally very low, lots of place for improvements... :)
Regarding more specifically the integration repository
- we have different type of files corresponding to different projects
python (vcpe, hpa, mocks, s3p) - the pylint rating correspond to the 4 modules - go (security)
- yaml
- bash
I just created a tox.ini for the python based project and run pylint + nosetests for the unit tests - but there are no unit tests in the different python directory :)
it seems that s3p is only for python2.7 which is no more supported.
...