Topic Leader(s)

• Cedric Ollivier

Topic Overview

X-testing & X-testing CI is a framework is a simple way for developers to manage their test cases, without being a CI/CD expert.

Slides & Recording

xtestingci on steroids | opnfv  etherpad

XtestingCI_on_steroids.mp4

Minutes

Lots of new features in the January 2021 release.

• Less dependency on Ansible - 3 commands for deployment
• Debian Centos Ubuntu, ... support

Leverage dynamic and shared runners for containers

Cedric Ollivier is developing a Katacoda tutorial/course for running K8s Ref Conformance tests

Question about tools - the only dependency is the X-testing Framework. Many open source tools could be leveraged

Demo of the course - After install, run an Ansible playbook as proposed in Elbrus RC-2, currently using Jenkins helm chart but K8s equivalent possible

(Would be exactly the same for Open stack with changes to configuration files).

For the future, defining a way within X-testing to on-board CNF and VNF is critical (this has been done for OS and VNF)

• would mean switching from shell runners to X-testing runners to replace LF IT CI
• deploy K8s cluster for Anuket X-testing runners.
• question about cost and "where" we deploy the k8s cluster
• other LFN projects would want to deploy container builds

It is very easy to manage the test case list within our labs, by writing a test case list within a YAML file.

Some Next steps:

• to release all Helm charts for the last components (TestAPI, Cachet, Docker registry, etc.)
• to complete the continuous development part in all scenarios as in used in OPNFV (Jenkins): docker builds, unit tests, gates, etc.
• to finish Katacoda (your feedbacks are all welcome)

"Try it, you'll love it!" Cedric Ollivier

Action Items

• Type your task here, using "@" to assign to a user and "//" to select a due date