This page contains a list of possible tests that can be generally used to test ACM and Participants HA functionality before delivery. The tests are listed below. After meeting about this document - several comments have been added, which give direction to some tests and eliminate others. A list will be added at the end of the page for tests that should be an immediate priority.
| Table of Contents |
|---|
Functional Tests
Basic Functionality Test:
- Verify that all microservices work correctly with a single replica.
- Increase the number of replicas and ensure all functionality still works as expected.
- Should temporarily be manual tests. Later this testing can be moved to Jenkins jobs with multiple replicas
Message Processing Test:
- Ensure that messages sent via Kafka are consumed and processed correctly by multiple replicas.
...
- Ensure sync topic sends to all replicas Verify sync of out properties – get instance
- Participant sim – whitebox test. Real participant black box test
Database Access Test: - Maybe
...
- Test that the data remains consistent across multiple replicas when performing CRUD operations for ACM through REST API.Covered by confirming outProperty sync across replicas
Performance Tests – add testing with replicas...
...
- Dynamically scale the number of replicas up and down and ensure the system continues to function correctly.
- Verify that new replicas start correctly and join the existing system seamlessly.
...
- Observe the system's behavior and ensure it degrades gracefully without crashing.
Priority Tests
List tests here