This is a draft page to be discussed with Integration team to define priorities for Guilin

X-projects

Repositories

Adopt the approach to create a repo for new use cases / simulators
Add linters to all the new repositories
Add new linters (tobot, bashate, rst)
How to get a consistent view on all the repositories, shall we tag all the repositories,..
update xtesting repo and put in place the build chain in ONAP (move from gitlab.com to ONAP)
update jave/python3.8 in ONAP (move from gitlab.com to ONAP)

Write an documentation 'Use case guideline"
Test creation of an override.yaml per use case to be able to deploy adhoc environment in windriver

update the tests
harden the simulators/emulators (no more in xfail lists)
clean? are all the tests still maintained?
archive CIST? => projects can bring back their tests in their repository but jenkins CSIT not needed anymore
move some of the CIST tests in Daily CI
introduction of python_sdk for new tests (deprecate onap-tests)
improve security tests (Integration and Built Tests For Releases)
How to measure the test coverage?
How to get better healthcheck tests and "force" project to update them when they provide a new version of their code
Support OOM on a use case for Core on F→ G migration