...
The Gating process can be described as follows:
In order to simplify the integration and avoid depenencies towars manifest or branches that become quickly out of sync a 3 steps gating was introduced and can be described as follows:
On patchset submission, the gating chain is triggered. It can be seen in the gerrit History windows.
...
Then if you want to download the artifact with all the results, you must select the page stage, then click download.
...
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:
...
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:
...
healthcheck
- core
- small
- medium
- full
...
Traditionnal Robot healthcheck test suites with the label core, small, medium or full
the tesuites are run in parallel
...
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:
...
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
...
Please see Where can I find the list of supported use cases? for the list of tests