Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

As we are leveraging the xtesting framework, the results will be managed consistantly whatever the test framework used (robot, python, bash,..) and optionnaly it is possible to push the results in http://testresults.opnfv.org

We may distinguish 2 big families

1) the tests run with docker from outside the clusteryou need ONAP + the kube config

3 categories are run from outside the cluster:

...

...

...

  • 10003/onap/xtesting-security

The command is indicated in the README of the associated directory in These tests will be run through a docker run command with the needed volumes associated to the different tests. As an example infrastructure tests will need the kube config file, the pyhtonsdk tests will require the openstack project credentials..

Each docker includes a README file detailing the mandatory and optional options.

DockerREADME link
xtesting-infra-healthcheckhttps://

...

...

...

docker run -v <kube config>/root/.kube/config -v <result directory>:/var/lib/xtesting/results nexus3.onap.org:10001/onap/xtesting-infra-healthcheck:latest

...



2) the tests run from inside the cluster

Some tests (the historical robot tests) are run from inside the cluser thanks to a kubernetes job

...

  • 10003/onap/xtesting-

...

...

  • 10003/onap/xtesting-smoke-usecases-

...

  • robot

This docker are consumed by k8s job in the ONAp namespace. See also the README section in job triggers a pod executing the robot tests. The configuration is provided by the testuise configmap but the testsuite pod is not needed.

Please read the different README associated with the docker to get the mandatory/optional parameters to be adapted.

DockerREADME link
xtesting-healthcheckhttps://

...

...


A demo has been done on how to run healthcheck full, onap-k8s and basic_vm on an ONAP lab