Versions Compared

Old Version 4

changes.mady.by.user Morgan Richomme

Saved on

compared with

New Version 5

changes.mady.by.user Morgan Richomme

Saved on

Key

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

...

If you follow the link you will reach the xtesting-onap gitlab page (on gitlab.com).

Note you need a gitlab account to access to these pages.


This link is unique and corresponds to the gating pipeline corresponding to the patch.

Image Added

You can download the artifact that corresponds to this specific test.Image Removed

If you download all the results, you will get an archive including the test results from the test pipeline:you need first to select the pipeline.

Image Added

You should see the following menu

Image Added

Then if you want to download the artifact with all the results, you must select the page stage, then click on download.Image Removed


TestDescriptionCriteriaResults
onap_healthcheck_k8s/onap-k8sWe check the status of the ONAP podsFAIL if 1 PODS in non Running state

logs available under results/healthcheck-k8s/k8s/xtesting.log

In the logs you will find

  • the list of pods
  • the list of deployments
  • the list of SVC
  • the describe of non Running pods
  • the events

results are also published in a public database:

http://testresults.opnfv.org/onap/api/v1/results?case_name=onap-k8s&build_tag=gitlab_ci-functest-rancher-baremetal-daily-master-<Gerrit_ID>

onap_healthcheck_k8s/onap-helmWe check the status of the ONAP helm chartFAIL if  1 chart is not DEPLOYED

logs available under results/healthcheck-k8s/k8s/xtesting.log

In the logs you will find

  • the list of heml charts and their status
  • the details on non DEPLOYED heml charts

results are also published in a public database:

http://testresults.opnfv.org/onap/api/v1/results?case_name=onap-helm&build_tag=gitlab_ci-functest-rancher-baremetal-daily-master-<Gerrit_ID>


healthcheck

  • core
  • small
  • medium
  • full

Traditionnal Robot healthcheck test suites with the label core, small, medium or full

the tesuites are run in parallel

FAIL if 1 of the helcheck if FAIL

logs available under results/healthcheck/<core|small|medium|full>/xtesting.log

Robot outputs are available in results/healthcheck/<core|small|medium|full>/<core|small|medium|full>

Results are also published in a public database:

http://testresults.opnfv.org/onap/api/v1/results?case_name=core&build_tag=gitlab_ci-functest-rancher-baremetal-daily-master-<Gerrit_ID>

End to End tests

  • basic_vm (ubuntu16)
  • freeradius (freeradius on basic_vm + use of NBI for instantiation)
  • clearwater_ims


They correspond to full onboard/instantation of some VNFs

They are triggered only if core and small healthcheck test suites aree successful


the test includes the creation and the cleaning of the resources

FAIL if VNF cannot be created at any stage (onboarding, distribution, instantiation,..)


if basic_vm Fails, other cases are not executed to save time

logs available under results/vnf/vnf/xtesting.log


Results are also published in a public database:

http://testresults.opnfv.org/onap/api/v1/results?case_name=basic_vm&build_tag=gitlab_ci-functest-rancher-baremetal-daily-master-<Gerrit_ID>

...