This page details the test specification for ACM for all new and existing functionality.
Prerequisites
- Access to a development laptop capable of running many docker containers
- Access to a Kubernetes cluster, either locally or remotely (if carrying out kubernetes participant tests)
Environment Setup
The immediate components like, acm, participants, databases etc will be deployed in your local environment using docker compose configurations from the policy/docker repo details are in the documentation here. However, we want to add mock participants for http, k8s and policy participants. So, we have to replace the docker-compose.yaml
in the policy/docker `/compose` directory with this one
Once this change is made, we can bring up all our required components with `./start-compose.sh policy-clamp-runtime-acm`
Test Group Setup Steps
Steps for Scenario Setup | Scenario Finish Steps | |
---|---|---|
Successful Endpoint Interaction |
| |
Non-Successful Endpoint Interaction | ||
Failure Handling Scenario |
| |
Participant Set Properties Scenario |
| |
Participant Restart Scenario |
| |
Multiple Simultaneous Message Scenario | Relevant instructions give in the below section | |
Timeout Scenario | ||
Update Scenario |
| |
Check Validation Scenario |
| |
Test Cases
In all test cases, that are calling rest endpoints, it is the ACM rest API that is being called. The url prefix to each rest call is: IP_ADDRESS:RUNTIME_PORT/onap/policy/clamp/acm/v2/. Use the provided POSTMAN collection to make the relevant calls.
Functionality Being Tested | Title | Test case | Steps | Expected Result | Test Result PASS/FAIL | Notes | Mock Participant | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Failure Handling | Prime AC Def and confirm test failure from http, k8s and policy participants | Prime AC def - http, k8s and policy participants should send back error message |
| 200 response In the response json, we should see – "state": "PRIMING" – and also a message in each element "Prime failed!" | HTTP Participant, K8s Participant, Policy Participant | Y | ||||||||||||||
Failure Handling | Deprime AC Def and confirm test failure from http, k8s and policy participants | Deprime AC def - http, k8s and policy participants should send back error message |
| 200 response In the response json, we should see – "state": "PRIMED" – and also a message in each element "Deprime failed!" | HTTP Participant, K8s Participant, Policy Participant | Y | ||||||||||||||
Failure Handling | Deploy AC instance and confirm test failure from http, k8s and policy participants | Deploy AC instance - http, k8s and policy participants should send back error message |
| 200 response with an "automationCompositionList" In the JSON returned, the instance deployState should be "DEPLOYING" Each element should contain the message "Deploy failed!" | HTTP Participant, K8s Participant, Policy Participant | Y | ||||||||||||||
Failure Handling | Undeploy AC instance and confirm test failure from http, k8s and policy participants | Undeploy AC instance - http, k8s and policy participants should send back error message |
| 200 response we should see the overall "deployState: UNDEPLOYING" with a message in each element that says "Deployed" | HTTP Participant, K8s Participant, Policy Participant | Y | ||||||||||||||
Failure Handling | Delete AC instance and confirm test failure from http, k8s and policy participants | Delete AC instance - http, k8s and policy participants should send back error message |
| 200 response with an "automationCompositionList" In the JSON returned, the instance deployState should be "DELETING" Each element should contain the message "Undeployed" | HTTP Participant, K8s Participant, Policy Participant | Y | ||||||||||||||
Failure Handling | Update AC instance and confirm test failure from http, k8s and policy participants | Update AC instance - http, k8s and policy participants should send back error message |
| 200 response with an "automationCompositionList" In the JSON returned, the instance deployState should be "UPDATING" Each element should contain the message "Update failed!" | HTTP Participant, K8s Participant, Policy Participant | Y | ||||||||||||||
Failure Handling | Unlock AC instance and confirm test failure from http, k8s and policy participants | Unlock AC instance - http, k8s and policy participants should send back error message |
| 200 response with an "automationCompositionList" In the JSON returned, the instance deployState should be "UNLOCKING" Each element should contain the message "Unlock failed!" | HTTP Participant, K8s Participant, Policy Participant | Y | ||||||||||||||
Failure Handling | Lock AC instance and confirm test failure from http, k8s and policy participants | Lock AC instance - http, k8s and policy participants should send back error message |
| 200 response with an "automationCompositionList" In the JSON returned, the instance deployState should be "LOCKING" Each element should contain the message "Unlocked" | HTTP Participant, K8s Participant, Policy Participant | Y | ||||||||||||||
Participant Out Properties | Set outProperties using the participant and retrieve them from the database | Any properties we set on the participant-side "outProperties" object should be retrievable from ACM |
| 200 response with an "automationCompositionList" The outProperties object should now look like the json illustrated in the next column | "outProperties": { | Y | ||||||||||||||
Participant Out Properties | Try to Set outProperties using the participant and retrieve them from the database before the instance is deployed | Any properties we set on the participant-side "outProperties" object should not be retrievable from ACM before the instance is deployed |
| 200 response with an "automationCompositionList" The outProperties object should be empty as before | Y | |||||||||||||||
Non-Successful Endpoint Interaction | Delete AC defintion after priming | Delete the commissioned defintion type2 after priming | Execute DELETE request on runtime acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId2}} | 400 Bad Request response. Should not allow to delete when primed | "ACM not in COMMISSIONED state, Update of ACM Definition not allowed" | |||||||||||||||
Non-Successful Endpoint Interaction | Update AC definition after priming | Update AC definition type 2 after priming | Execute PUT request on runtime acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId2}} | 406 Not acceptable response Should not allow to update when primed | ||||||||||||||||
Non-Successful Endpoint Interaction | Shut down participant and Deploy | Shutdown one of the participants and trigger deployment | Remove one of the participant. Execute PUT request on runtime acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId1}}/instances/{{instanceId1}} | 409 Conflict response. Verify if runtime is restricting the deploy operation when one or more associated particpant is OFFLINENeeds updating because of new validation that ppnt is online | ||||||||||||||||
Non-Successful Endpoint Interaction | Delete AC instance with OFFLINE participant | Delete the AC instance after removing participant | Execute DELETE request on runtime-acm {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId2}}/instances/{{instanceId2}} | 202 Response409 Conflict response. Verify if runtime accepts the delete AC instance request when the associated participant is in OFFLINE state The overall state is stuck in DELETING and updated to TIMEOUT after the configured timeout is reached Verify the user is allowed to order a state change after TIMEOUT is reached | Needs updating because of new validation that ppnt is online | is restricting the delete operation when one or more associated particpant is OFFLINE | ||||||||||||||
Non-Successful Endpoint Interaction | Deprime AC defintion with OFFLINE participant | Deprime AC defintion when the participant is OFFLINE | Make sure the AC instance is deleted and shutdown the participant again. Execute PUT request on runtime acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId}} | 202 Response409 Conflict response. Verify the runtime allows to Deprime the definitions from all the participants when one of the participant is OFFLINE Verify the AC state is stuck in DEPRIMING and updated to TIMEOUT after the configured timeout is reached.Needs updating because of new validation that ppnt is onlineif runtime is restricting the deprime operation when one or more associated particpant is OFFLINE | ||||||||||||||||
Non-Successful Endpoint Interaction | Verify restricted operations in deployed state | Try to perform the following operations Delete the AC instance2 Deprime the Ac definition 2 Update the AC instance 2 | All the perfomed operations should return 400 response. The instances should not be allowed to get deleted or deprimed in Deployed state. Update IS allowed now | |||||||||||||||||
Non-Successful Endpoint Interaction | Update AC instance property after participant shutdown | Shutdown participant and trigger UPDATE | Shutdown the participant and trigger the update property event on the runtime as per the steps specified above | Verify if the rest request is accepted with 202 response Verify the PROPERTIES_UPDATE event is sent to the participants from runtime-acm. The ACM instance state should be "UPDATING" until the properties update is completed in the participant. The AC state should be updated as TIMEOUT after the configured timeout in runtime | This should be updated because the operation will no longer be allowed by ACM if the participant is OFFLINE | |||||||||||||||
Non-Successful Endpoint Interaction | Shut down participant on UNLOCKED state | Shut down one of the participants on UNLOCKED state | Manually stop one of the participants | ??? Verify the behaviour of runtime when the participant is OFFLINE and the instances are deployed(it depend how restart will be implemented) | This should be updated because the operation will no longer be allowed by ACM if the participant is OFFLINE | |||||||||||||||
Restart Testing | Restart acm runtime | Restart runtime application | Manually restart the container or mvn application | Verify if the runtime comes up and running and get synced with the database. Retrieve participants and compositions from runtime endpoint. | microk8s kubectl delete pod policy-clamp-runtime-acm-7ff68ff9fd-kllb7 pod "policy-clamp-runtime-acm-7ff68ff9fd-kllb7" deleted | |||||||||||||||
Restart Testing | Shut down participant after priming | Restart any of the participant | Manually restart the container or mvn application Execute GET request on the runtime-acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/participants/ | Participants should get registered and get the primed definitions from runtime once they are up again. | ||||||||||||||||
Restart Testing | Shut down any of the participant | Delete one of the participants permanently. Execute GET request on the runtime-acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/participants/ | Verify the removed participants should have been marked OFFLINE by the runtime. Verify fetching the automation compositions where the element of removed participants should not have participant ids associated. (it depend how restart will be implemented) | It needs 10 minutes on my deployment after requesting a Participant Report from all participants | ||||||||||||||||
Restart Testing | Restart participant after Priming | Restart any of the participant | Manually restart the container or mvn application | Fetch participants list from runtime, restarted participant should get reregistered with runtime again. Fetch commisioned defintions, it should have elements with restarted participant id associated | ||||||||||||||||
Successful Endpoint Interaction | Verify Participant Registration | Verify all the participants |
| Verify all the deployed participants with their Ids and current status are retrieved | PASS | |||||||||||||||
Successful Endpoint Interaction | CRUD Automation Composition Types | Create Automation Composition Type 1 |
| 201 Response with compositionId | PASS | |||||||||||||||
Successful Endpoint Interaction | Create Automation composition Type 2 |
| 201 Response with compositionId | PASS | ||||||||||||||||
Successful Endpoint Interaction | Update AC definition | Update the AC type 1 with some changes in the common properties |
Execute PUT request on runtime acm endpoint | 201 Response with composition Id | ||||||||||||||||
Successful Endpoint Interaction | Delete AC definition | Delete the Ac type 2 |
| 200 Response | PASS | |||||||||||||||
Successful Endpoint Interaction | Fetch Commissioned definition before Priming | Get all the commisioned definitions from db |
| OK |
| |||||||||||||||
Successful Endpoint Interaction | Priming | Prime AC definition 1 |
| 202 response | PASS | |||||||||||||||
Successful Endpoint Interaction | Prime AC definition 2 |
| 202 response | PASS | Create the composition Type 2 again after it was deleted earlier | |||||||||||||||
Successful Endpoint Interaction | Fetch Commisioned definition after Priming | Get all the commisioned definitions from db |
| 200 response | OK |
| ||||||||||||||
Successful Endpoint Interaction | Create AC instance | Create AC instance 1 | Execute POST request on runtime-acm {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId1}}/instances | 200 Response with InstanceId | ||||||||||||||||
Successful Endpoint Interaction | Create AC instance 2 | Execute POST request on runtime-acm {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId2}}/instances | 200 Response with InstanceId | |||||||||||||||||
Successful Endpoint Interaction | Update AC instance | Update AC instance1 with wrong paramter | Execute PUT request on runtime-acm {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId1}}/instances | 200 Response with Instance id | ||||||||||||||||
Successful Endpoint Interaction | Undeploy AC instance | Undeploy AC instance 1 | Execute PUT request on runtime acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId1}}/instances/{{instanceId1}} Execute GET request on runtime acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId1}}/instances/{{instanceId1}} | 202 Response. Verify the AC instance's is "UNDEPLOYED" | ||||||||||||||||
Successful Endpoint Interaction | Update AC instance | Update AC instance1 with correct paramter | Execute PUT request on runtime-acm {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId1}}/instances | 200 Response with Instance id | ||||||||||||||||
Successful Endpoint Interaction | Delete AC instance | Delete AC instance2 | Execute DELETE request on runtime-acm {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId2}}/instances/{{instanceId2}} | 200 Response | ||||||||||||||||
Successful Endpoint Interaction | Deploy AC instance | Deploy AC instance 1 | Make sure AC instance 1 and 2 are created. Execute PUT request on runtime acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId1}}/instances/{{instanceId1}} Execute GET request on runtime acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId1}}/instances/{{instanceId1}} | 202 Response. Verify the AC instance's admin state is "LOCKED". No operation has been carried out by the participants. Depending on the participant being used and whether it has a specific implementation of lock and unlock. | ||||||||||||||||
Successful Endpoint Interaction | Deploy AC instance 2 | Execute PUT request on runtime acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId2}}/instances/{{instanceId2}} | 202 Response. Verify the AC instance's admin state is "LOCKED". No operation has been carried out by the participants. Depending on the participant being used and whether it has a specific implementation of lock and unlock. | |||||||||||||||||
Successful Endpoint Interaction | Get deployed instance by id | Execute GET request on runtime ACM {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId}}/instances/{{instanceId}} | Verify the instance is retrieved and present in LOCKED state. | |||||||||||||||||
Successful Endpoint Interaction | UNLOCK the AC instance | Execute PUT request on runtime acm endpoint {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId2}}/instances/{{instanceId2}} | 200 Response Verify the k8s , http and policy participants have performed the intended operations on UNLOCKED state | |||||||||||||||||
Successful Endpoint Interaction | Verify the operational state | Fetch the operational state of the AC instance | Verify the instance elements are reporting operational state "ACTIVE" in UNLOCKED state | |||||||||||||||||
Successful Endpoint Interaction | Verify the usage state | Fetch the usage state of the AC instance | Verify the instance elements are reporting usage state "IDLE/BUSY/AVAILABLE" in UNLOCKED state | |||||||||||||||||
Successful Endpoint Interaction | Verify the operational state | Fetch the operational state of the AC instance | Verify the instance elements are reporting operational state "INACTIVE" in LOCKED state | |||||||||||||||||
Successful Endpoint Interaction | Verify the usage state | Fetch the usage state of the AC instance | Verify the instance elements are reporting usage state "IDLE/BUSY/AVAILABLE" in LOCKED state | |||||||||||||||||
Successful Endpoint Interaction | Undeploy AC instance | LOCK the AC instance with instanceid | Make sure the AC instance is deployed and UNLOCKED successfully. Execute PUT request on runtime acm. {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId}}/instances/{{instanceId}} | 200 Response. The instance should be moved to LOCKED state. Participants should have removed the corresponding deployments from the system | ||||||||||||||||
Successful Endpoint Interaction | Delete AC instance | Execute DELETE request on runtime acm {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId}}/instances/{{instanceId}} | 202 Response. The AC instance should get deleted from the db. | |||||||||||||||||
Successful Endpoint Interaction | Deprime AC defintion | Execute PUT request on runtime ACM {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId}} Verify fetching the commisioned defintions and make sure the AC elements are unassigned from the participants | 202 Response. The AC instance should get deleted from the db. | |||||||||||||||||
Successful Endpoint Interaction | Delete AC defintion | Execute DELETE request on runtime ACM {{address}}:{{runtimeport}}/onap/policy/clamp/acm/v2/compositions/{{compositionId}} | 200 Response. The AC defintion should get deleted from the db | |||||||||||||||||
Timeout Scenario | Delay participant while DEPLOYING | Delay the participant when instances are deploying | Make sure the instance deployment takes longer time and shutdown the participant when the instances are being deployed. (Note: AcElement microservice can be used to alter the behaviour of deployment) | Verify the behaviour of runtime when the participant goes offline in the middle of deployment. Verify the instance state to go TIMEOUT after the configured timeout is reached. (it depend how restart will be implemented) | Mock participant must be called with configuration for how long to delay. Participant shoul be ONLINE | |||||||||||||||
Update Scenario | Update AC instance property on the deployed instance | Verify updating of AC properties in runtime | Make sure the AC instance is deployed successfully. - Verify the 'GET instance' Api shows the instance state as 'Deployed' Call "Instantiation AC" Api with the updated properties of the instance elements in the request body. - response should be 202 | Verify the runtime logs that the 'PROPERTIES_UPDATE' event is sent to the participants from runtime-acm. Call the 'GET instance' Api - should get the 200 response and the deploy state of the instance should be "UPDATING" The ACM instance state should be "UPDATING" until the properties update is completed in the participant. | ||||||||||||||||
Update Scenario | Update AC instance property on an Undeployed instance | Verify updating of instance properties on an undeployed instance | Make sure the AC instances are in UNDEPLOYED state. - Verify the 'GET instance' Api shows the instance state as 'Undeployed' Call "Instantiation AC" with the updated properties of the instance elements in the request body. - response should be 202 | Call "get Instantiated List" - should get a 200 response and we should see the properties updated for the instance in the runtime database. In this case, there should not be any PROPERTIES_UPDATE event sends out from the runtime as the instance is not yet deployed to the participant. | ||||||||||||||||
Restart Scenario | Restart participant after priming | Verify restarting of participant after the composition is primed. | Make sure the AC composition is commissioned and primed to the participants. Execute the test step 8 specified in the restart scenario section of this document. For the step 8d, execute the GET compositions to verify the Ac element info are primed to the restarted participant. | Verify the restarted participant is primed again by the runtime with the AC element info. | ||||||||||||||||
Restart Scenario | Restart after deployment | Verify restarting of participant after the deployment | Make sure an AC instance is deployed successfully and the GET instance Api returns 200 response with the deploy state 'Deployed' Execute the test step 8 specified in the restart scenario section of this document. For the step 8d, execute the GET instance Api to verify the Ac element info are in deployed state without any changes. | Verify the runtime logs for composition and instance events sent to the restarted participant. The AC instance state should be preserved as 'DEPLOYED' without any changes. | ||||||||||||||||
Restart Scenario | Restart during deployment | Verify restarting of participant when the deployment is in progress | Trigger the deployment of an AC instance and make sure the AC instance is in DEPLOYING state. This can be achieved by using mock participant by configuring appropriate delays. Execute the test step 8 specified in the restart scenario section of this document. Verify the runtime sends out composition and instance info to the participant through kafka events. | Execute GET AC instance to verify the deployment gets executed by the participant again and the over all state is updated accordingly with success/fail results | ||||||||||||||||
Restart Scenario | Restart during Undeployment | Verify restarting of participant when the undeployment is in progress | Trigger the undeployment of an AC instance and make sure the AC instance is in UNDEPLOYING state. This can be achieved by using mock participant by configuring appropriate delays. Execute the test step 8 specified in the restart scenario section of this document. Verify the runtime sends out composition and instance info to the participant through kafka events. | Execute GET AC instance to verify the undeployment gets executed by the participant again and the over all state is updated accordingly with success/fail results | ||||||||||||||||
Restart Scenario | Restart during UPDATE | Verify restarting behavior of participant when the update operation is in progress | Make sure an AC instance is deployed successfully and the GET instance API returns 200 response with the deploy state DEPLOYED. Trigger the update of an AC instance properties by executing the AC instantiation API call with updated properties on the request body. Make sure the AC instance is in UPDATING state. This can be achieved by using mock participant by configuring appropriate delays. Execute the test step 8 specified in the restart scenario section of this document. Verify the runtime sends out composition and instance info to the participant through kafka events. | Execute GET AC instance to verify the updating operation gets executed by the participant again and the over all state is updated accordingly with success/fail results Verify fetching the AC instance to confirm the properties of the AC instance are updated as per the update request. |
Handle multiple messages from ACM to Participant simultaneously
Description
Functionality to test | Test the ability for participants to Handle multiple messages. |
---|---|
Environment | CSIT with microk8s |
Requirements and preconditions | Containers have to be configured to work at least with 4 CPU: resources: |
How to test | Create two instances and deploy/undeploy at same time |
Expected result | Check into participants log, the threads that are executing deploy/undeploy at same time |
Flow for participantHttp and participantKubernetes
Postman collection: ACM DEMO Test 2.postman_collection.json
Step | Result | Note |
---|---|---|
Call "Create Commissioned AC definition" | Success | |
Call "Priming AC definition" | Success | |
Call "Create AC Instantiation Group A" | Success | |
Call "Create AC Instantiation Group B" | Success | |
Call "Deploy instantiated Group A" and "Deploy instantiated Group B" at same time | Success | |
Check the participants log during deployment | threads that are executing deploy at same time | |
Check that elements of both groups are getting deployed | starter-a, bridge-a and sink-a for group A and starter-b, bridge-b and sink-b for group B | |
Call "Get instantiated Group A" to check the final state | check deployState as DEPLOYED | |
Call "Get instantiated Group B" to check the final state | check deployState as DEPLOYED | |
Check elements are working as expected | Check into the sink log the "Cycle completed" | microk8s kubectl logs <acm-sink-....> | grep completed |
Call "Undeploy instantiated Group A" and "Undeploy instantiated Group B" at same time | Success | |
Check the participants log during undeployment | threads that are executing undeploy at same time | |
Check that elements of both groups are getting undeployed | ||
Call "Delete instantiated Group A" and "Delete instantiated Group B" at same time | Success | |
Depriming AC definition | Success | |
Delete AC definition | Success |
Timeout handling in AutomationComposition Definition and Instance
Description
Functionality to test | Test ACM runtime timeout handling during prime, deprime, delete, deploy, undeploy, update, lock and unlock |
---|---|
Environment | Custom Docker compose with three mock participants |
Requirements and preconditions | reduce the time in runtime: runtime: reduce the time in participant: participant: |
How to test | Configure mock participants to delay the operations of 30 seconds. The timeout will be triggered after 10 seconds |
Expected result | During a change state, user cannot do any actions, with timeout, the user is allowed to replay the action or go back |
Flow
Postman collection: DEMO Simulator.postman_collection.json
Step | Result | Note |
---|---|---|
Call "Create AC definition" | Success | |
Call "Post http-participant parameters" | Success | { |
Call "Priming AC definition" | Success | |
Call "Get commission" | state = "PRIMING", stateChangeResult = "NO_ERROR" | |
At the time the state is "PRIMING" call:
| Fail | User is not allowed to re-prime, deprime and delete |
Wait Timeout and call "Get commission" | state = "PRIMING", stateChangeResult = "TIMEOUT" | |
At the time the state is "PRIMING" and stateChangeResult is "TIMEOUT": call "Delete AC definition" | Fail | User is not allowed to delete when the composition is in priming |
At the time the state is "PRIMING" and stateChangeResult is "TIMEOUT": call "Priming AC definition" | Success | User is allowed to re-prime when the composition is in priming and timeout |
Call "Get commission" | state = "PRIMING", stateChangeResult = "NO_ERROR" | After re-prime action, stateChangeResult will be back to NO_ERROR |
At the time the state is "PRIMING" and stateChangeResult is "TIMEOUT": call "Depriming AC definition" | Success | User is allowed to deprime when the composition is in priming and timeout |
Call "Get commission" | state = "DEPRIMING", stateChangeResult = "NO_ERROR" | After deprime action, stateChangeResult will be back to NO_ERROR |
At the time the state is "DEPRIMING" call:
| Fail | User is not allowed to prime, deprime and delete |
At the time the state is "DEPRIMING" and stateChangeResult is "TIMEOUT": call "Delete AC definition" | Fail | User is not allowed to delete |
At the time the state is "DEPRIMING" and stateChangeResult is "TIMEOUT": call "Depriming AC definition" | Success | User is allowed to deprime |
Call "Get commission" | state = "DEPRIMING", stateChangeResult = "NO_ERROR" | After deprime action, stateChangeResult will be back to NO_ERROR |
At the time the state is "DEPRIMING" and stateChangeResult is "TIMEOUT": call "Priming AC definition" | Success | User is allowed to prime |
when state is "PRIMED" call "Get commission" | state = "PRIMED", stateChangeResult = "NO_ERROR" | |
Call "Instantiation AC" | Success | |
Call "Deploy instantiated" | Success | |
Call "Get instantiated by instanceId" | deployState = "DEPLOYING", stateChangeResult = "NO_ERROR" | |
At the time the deployState is "DEPLOYING" call:
| Fail | User is not allowed to re-deploy, undeploy, lock, unlock, update and delete |
Wait Timeout and call "Get instantiated by instanceId" | deployState = "DEPLOYING", stateChangeResult = "TIMEOUT" | |
At the time the deployState is "DEPLOYING" and stateChangeResult is "TIMEOUT":
| Fail | User is not allowed to lock, unlock, update and delete |
At the time the deployState is "DEPLOYING" and stateChangeResult is "TIMEOUT": call "Deploy instantiated" | Success | User is allowed to re-deploy when the instance is in deploying and timeout |
Call "Get instantiated by instanceId" | deployState = "DEPLOYING", stateChangeResult = "NO_ERROR" | After deploy action, stateChangeResult will be back to NO_ERROR |
At the time the deployState is "DEPLOYING" and stateChangeResult is "TIMEOUT": call "Undeploy instantiated" | Success | User is allowed to undeploy when the instance is in deploying and timeout |
Call "Get instantiated by instanceId" | deployState = "UNDEPLOYING", stateChangeResult = "NO_ERROR" | After undeploy action, stateChangeResult will be back to NO_ERROR |
At the time the deployState is "UNDEPLOYING" call:
| Fail | User is not allowed to deploy, undeploy, lock, unlock, update and delete |
Wait Timeout and call "Get instantiated by instanceId" | deployState = "UNDEPLOYING", stateChangeResult = "TIMEOUT" | |
At the time the deployState is "UNDEPLOYING" and stateChangeResult is "TIMEOUT":
| Fail | User is not allowed to lock, unlock, update and delete |
At the time the deployState is "UNDEPLOYING" and stateChangeResult is "TIMEOUT": call "Undeploy instantiated" | Success | User is allowed to undeploy when the instance is in undeploying and timeout |
Call "Get instantiated by instanceId" | deployState = "UNDEPLOYING", stateChangeResult = "NO_ERROR" | After undeploy action, stateChangeResult will be back to NO_ERROR |
At the time the deployState is "UNDEPLOYING" and stateChangeResult is "TIMEOUT": call "Deploy instantiated" | Success | User is allowed to deploy when the instance is in undeploying and timeout |
Wait DEPLOYED and call "Get instantiated by instanceId" | deployState = "DEPLOYED", stateChangeResult = "NO_ERROR" | |
Call "Update Instantiation AC" | Success | |
Call "Get instantiated by instanceId" | deployState = "UPDATING", stateChangeResult = "NO_ERROR" | |
At the time the lockState is "UPDATING" call:
| Fail | User is not allowed to deploy, undeploy, lock, unlock, update and delete |
Wait Timeout and call "Get instantiated by instanceId" | deployState = "UPDATING", stateChangeResult = "TIMEOUT" | |
At the time the lockState is "UPDATING" and stateChangeResult is "TIMEOUT" call:
| Fail | User is not allowed to deploy, undeploy, lock, unlock and delete |
Call "Update Instantiation AC" | Success | User is allowed to update when the instance is in updating and timeout |
Wait the completion of update and call "Get instantiated by instanceId" | deployState = "DEPLOYED", stateChangeResult = "NO_ERROR" | |
Call "Unlock instantiated" | Success | |
Call "Get instantiated by instanceId" | lockState = "UNLOCKING", stateChangeResult = "NO_ERROR" | |
At the time the lockState is "UNLOCKING" call:
| Fail | User is not allowed to deploy, undeploy, lock, unlock, update and delete |
Wait Timeout and call "Get instantiated by instanceId" | lockState = "UNLOCKING", stateChangeResult = "TIMEOUT" | |
At the time the lockState is "UNLOCKING" and stateChangeResult is "TIMEOUT" call:
| Fail | User is not allowed to deploy, undeploy, update and delete |
At the time the lockState is "UNLOCKING" and stateChangeResult is "TIMEOUT": call "Unlock instantiated" | Success | User is allowed to unlock when the instance is in unlocking and timeout |
Call "Get instantiated by instanceId" | lockState = "UNLOCKING", stateChangeResult = "NO_ERROR" | After unlock action, stateChangeResult will be back to NO_ERROR |
At the time the lockState is "UNLOCKING" and stateChangeResult is "TIMEOUT": call "Lock instantiated" | Success | User is allowed to lock when the instance is in unlocking and timeout |
Call "Get instantiated by instanceId" | lockState = "LOCKING", stateChangeResult = "NO_ERROR" | After lock action, stateChangeResult will be back to NO_ERROR |
At the time the lockState is "LOCKING" call:
| Fail | User is not allowed to deploy, undeploy, lock, unlock and delete |
Wait Timeout and call "Get instantiated by instanceId" | lockState = "LOCKING", stateChangeResult = "TIMEOUT" | |
At the time the lockState is "LOCKING" and stateChangeResult is "TIMEOUT" call:
| Fail | User is not allowed to deploy, undeploy and delete |
At the time the lockState is "LOCKING" and stateChangeResult is "TIMEOUT": call "Lock instantiated" | Success | User is allowed to lock when the instance is in locking and timeout |
Call "Get instantiated by instanceId" | lockState = "LOCKING", stateChangeResult = "NO_ERROR" | After lock action, stateChangeResult will be back to NO_ERROR |
At the time the lockState is "LOCKING" and stateChangeResult is "TIMEOUT": call "Unlock instantiated" | Success | User is allowed to unlock when the instance is in locking and timeout |
Call "Get instantiated by instanceId" | lockState = "UNLOCKING", stateChangeResult = "NO_ERROR" | After unlock action, stateChangeResult will be back to NO_ERROR |
Wait UNLOCKED and call "Get instantiated by instanceId" | lockState = "UNLOCKED", stateChangeResult = "NO_ERROR" | |
Call "Post http-participant parameters" | Success | { |
Call "Lock instantiated" | Success | |
Call "Get instantiated by instanceId" | lockState = "LOCKED", stateChangeResult = "NO_ERROR" | |
Call "Undeploy instantiated" | Success | |
Call "Get instantiated by instanceId" | deployState = "UNDEPLOYED", stateChangeResult = "NO_ERROR" | |
Call "Delete instantiated" | Success | |
Call "Get instantiated by instanceId" | deployState = "DELETING", stateChangeResult = "NO_ERROR" | |
At the time the deployState is "DELETING" call:
| Fail | User is not allowed to deploy, undeploy, lock, unlock, update and delete |
Wait Timeout and call "Get instantiated by instanceId" | deployState = "DELETING", stateChangeResult = "TIMEOUT" | |
At the time the deployState is "DELETING" and stateChangeResult is "TIMEOUT" call:
| Fail | User is not allowed to deploy, undeploy, lock, unlock and update |
Call "Delete instantiated" | Success | User is allowed to delete when the instance is in deleting and timeout |
Call "Get instantiated by instanceId" | deployState = "DELETING", stateChangeResult = "NO_ERROR" | After delete action, stateChangeResult will be back to NO_ERROR |
Wait for delete and call "Get instantiated list" | No instances | |
Call "Depriming AC definition" | Success | |
Call "Delete AC definition" | Success |