Introduction
<Details about Additional tests required for this Blue Print in addition to the Akraino Validation Feature Project>
Akarino Test Group Information
<The Testing Ecosystem>
Testing Working Group Resources
Table of Contents
Overall Test Architecture
The diagram depicts current CI process. For every new patch set Jenkins creates new Regional controller Controller and instance for deployment airship+tungstenfabric.
After the deployment all logs are uploaded Then Regional Controller initiates the process of deployment Airship-in-a-bottle and waits for the process to finish. Usually it takes 5-6 hours.
Then Jenkins collects all the deployment logs and uploads them to Nexus. The deployment is considered to be successful or failed according to the deployment logs.
Test
...
Test Framework
Traffic Generator
Test API description
<Akraino common tests>
The Test inputs
Test Procedure
Expected output
Test Results
<Blueprint extension tests>
The Test inputs
Test Procedure
Expected output
Test Results
<Feature Project Tests>
The Test inputs
Test Procedure
Expected output
...
Procedure
The internal airship sanity tests are used at the moment. They are the part of airship project.
At the end of airship-in-the-bottle deployment script shows state for every shipyard step.
Criteria of successful deployment:
All shipyard steps has state success. Please see the example bellow:
| Code Block | ||||
|---|---|---|---|---|
| ||||
Action Notes:
> action metadata:01DS13D4JB1YZVVA5ZWPQ4F976(2019-11-06 19:35:04.156720+00:00): Configdoc revision 2
action/01DS13D4JB1YZVVA5ZWPQ4F976 completed SUCCESSFULLY
Name: deploy_site
Action: action/01DS13D4JB1YZVVA5ZWPQ4F976
Lifecycle: Complete
Parameters: {}
Datetime: 2019-11-06 19:35:02.987188+00:00
Dag Status: success
Context Marker: 95f18fee-487c-4912-bcca-ccae130feebc
User: shipyard
Steps Index State Footnotes
step/01DS13D4JB1YZVVA5ZWPQ4F976/action_xcom 1 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/dag_concurrency_check 2 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/get_rendered_doc 3 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/deployment_configuration 4 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/preflight 5 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/validate_site_design 6 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/drydock_build 7 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/verify_site 8 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/armada_build 9 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/armada_get_status 10 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/prepare_site 11 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/armada_post_apply 12 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/create_action_tag 13 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/ucp_preflight_check 14 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/deployment_status 15 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/deckhand_validate_site_design 16 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/armada_validate_site_design 17 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/drydock_validate_site_design 18 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/promenade_validate_site_design 19 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/prepare_and_deploy_nodes 20 success (1)
step/01DS13D4JB1YZVVA5ZWPQ4F976/armada_get_releases 21 success
step/01DS13D4JB1YZVVA5ZWPQ4F976/final_deployment_status 22 success
Step Footnotes Note
(1) > Deployment Groups:deploy_site(2019-11-06 19:38:22.826335+00:00): Stage.DEPLOYED: masters(critical), workers(critical)
Commands User Datetime
invoke shipyard 2019-11-06 19:35:04.165353+00:00
|
Test Results
Example of successful CI log