-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
Policy 2022-07-13->2022-07-27, Policy 2022-07-27->2022-08-10, Policy 2022-08-31->2022-08-17, Policy 2022-08-31->2022-09-14, Policy 2022-09-14->2022-09-28, Policy 2022-09-28->2022-10-12, Policy 2022-10-12->2022-10-26, Policy 2023-03-09->2023-03-22
Currently, testing of composition states in ACM is not comprehensive. The state machine should be comprehensively tested with automated tests:
- Test the instantiation of variables
- Test bringing up of compositions with multiple composition elements
- Test taking down compositions with multiple composition elements
- Test what happens when the ACM runtime shuts down and restarts, ensure recovery happens
- Test what happens when composition elements and participants fail and recover, does the composition handling recover in an orderly manner
To do this, we need to have suitable automation compositions that are developed to test ACM.
- Prepare a microservice that can be brought up and down with the K8S participant and configured with the HTTP participant
- The microservice can emit and receive events, so instances of the microservice can be chained together to create complex compositions
- Create policies that can receive events from one microservice instance and pass them onto another microservice instance
- Create a test plan describing the ACM scenarios to be tested
- Create automated tests to test the scenarios
- Run the tests
See https://wiki.onap.org/display/DW/Test+and+Verification+of+ACM+State+Management