With multiple languages being used in ONAP we need to have support for code-coverage for all of them. Even though we use some common called SONAR for the PTLS to view the code coverage not all languages are supported.
Since no one person will have the knowledge of tools and techniques in all the languages the plan we have is.
- Choose a pilot project for every language
- Work out a generic plan for that language which can be ported to all the projects under the same language
- Communicate the plan through ONAP discuss and the seccoom mailing list so that other projects with the same language can be sure that they can support it.
- Then the pilot project will implement the setup locally and then work with the PTL for the pilot project and LF to get the tools installed.
Responsibilities of the pilot project
- Come with a generic proposal to get the reports generated in SONAR.
- Come up with the tools and techniques that are required.
- Get the tools installed in LF.
We need to find a pilot project for all the languages if we need code coverage for that particular language. And having code coverage is a requirement for CII badging.
Benefits of being the pilot
The pilot project's recommendation and setup will be the one that is officially supported. So lead the way to get your preferred way of setup in.
This page is intended to capture the languages used in ONAP and the projects.
| Language | Pilot Project | Details |
|---|
| Python |
| |
| Clojure |
| |
| Javascript | CLAMP | |
| Golang |
| | Project | Contact |
|---|
| Multi VIM/Cloud | | | Secret Management Service | Kiran Code Coverage in Golang: Golang already provides some tools for capturing code coverage and reporting it. We already do that in the golang merge builds. See jenkins log for details. We also report the coverage in the project page. See here. |
|
| Java | N/A because sonar supports Java out of the box |
|
| C/C++ |
| | Project | Contact |
|---|
AAF PKCS11 based key protection | |
|
|
|
|