...
Ideally use case owner shall be able to provide the automatic procedure at this stage.
Please note that this part is the most important and represents about 95% of the work...writing good tests requires a good knowledge of the system under test.
2) ...and integrated in a docker based on Xtesting
...
This task can be done by the integration team - the most difficult is the test itself... If writing the test takes 90% of the the time, building a xtesting docker is about 4%.
Xtesting is a light framework aiming to harmonize test inputs and outputs, which is very helpful for integration.It has been developped in OPNFV and already proposed several infrastructure test dockers for Openstack and kubernetes, leveraging upstream tests (https://wiki.opnfv.org/pages/viewpage.action?pageId=13211751).
...
*: note that Xtesting is open source so if your favorite framework is missing you can add it
The CI part
This last part represent the missing 1%, it mainly deals with declaration of the case in the DB and in the CI system.
1) Your tests must be declared in the DB...
...
An account onap-integration has been created. Public SSH keys of the contributors have been pushed to grant access to this machine.
So to log in use
| Code Block | ||
|---|---|---|
| ||
$ ssh -i <key path> onap-integration@testresults.opnfv.org |
Once log you can directly access to the database
...