...
Create a new use case
Code Block | ||
---|---|---|
| ||
singleNodeRepl:PRIMARY> db.testcases.insert({'name':'basic_cnf', 'project_name': 'integration', 'tier':'smoke-usecases', 'version': '>guilin', 'description':'Test the creation of simple cnf (nginx)', 'domains': 'onap', 'tags':'cnf,multicloud,so,k8splugin', 'catalog_description':'basic cnf'}) |
it is obviously possible to update, delete using usual mongo commands.
... and in the CI
Once everything is declared in the DB, you can add the test in the CI
...
sdsddschain.
This is done in the xtesting-onap project hosted in gitlab.com (as the CI is based on gitlab-ci)
You can create modify the gitlab-ci config and create a merge request
As the tests are embbeded in a xtesting dockers, in theory the integration in CI is simple because already done for other tests (robot, bash, python, ...)
Edit https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/blob/master/gitlab-ci/base.yml
Code Block | ||
---|---|---|
| ||
...
.MY_NEW_TEST: &MY_NEW_TEST
variables:
run_tiers: xtesting-smoke-usecases-robot
run_type: my_new_test_declared in the xtesting entrypoint (shall be declared also in the DB if you want to push the results to the DB)
run_timeout: 1200
stage: smoke-usecases
allow_failure: true
<<: *get_artifact
<<: *runner_tags
<<: *run_smoke_usecase_robot
<<: *manage_artifacts
...
MY_NEW_TEST:
<<: *MY_NEW_TEST
only:
refs:
- triggers
|
You can assign the test to one of the declared stage/category (infrastructure-healthcheck, healthcheck, smoke-usecases, onap-security)
Xtesting references:
- the official xtesting documentation: https://xtesting.readthedocs.io/en/latest/
Xtesting slide deck:http://testresults.opnfv.org/functest/xtesting/
Xtesting 2020 slide deck update: http://testresults.opnfv.org/functest/xtesting2020/
...