413eee94db
Signed-off-by: Roberto J Rojas <robertojrojas@gmail.com> Signed-off-by: Bernd Verst <github@bernd.dev> Co-authored-by: Alessandro (Ale) Segala <43508+ItalyPaleAle@users.noreply.github.com> Co-authored-by: Bernd Verst <github@bernd.dev> |
||
|---|---|---|
| .. | ||
| components/docker | ||
| README.md | ||
| config.yaml | ||
| docker-compose.yml | ||
| redis_test.go | ||
README.md
Redis State Store certification testing
This project aims to test the Redis State Store component under various conditions.
Test plan
Basic Test for CRUD operations:
- Able to create and test connection.
- Able to do set, fetch, update and delete.
- Negative test to fetch record with key, that is not present.
Test save or update data with different TTL settings:
- TTL not expiring
- TTL not a valid number
- Provide a TTL of 1 second: a. Fetch this record just after saving b. Sleep for 2 seconds c. Try to fetch again after a gap of 2 seconds, record shouldn't be found
Component must reconnect when server or network errors are encountered
Infra test:
1- When redis goes down and then comes back up - client is able to connect
eTag related:
a. Insert a Key-Value pair, eTag will be 1 b. Update Value v2 for this Key with eTag equal to 1 - new eTag wil be 2. c. Try to Update v3 for this Key with eTag equal to 4 - value should not get updated. d. Get and validate eTag for it should be 2 only.
Transaction related, like Upsert:
Upsert in Multi function, using 3 keys with updating values and TTL for 2 of the keys, down in the order.
enableTLS set to true & enableTLS not integer:
Testing by creating component with ignoreErrors: true and then trying to use it, by trying to save, which should error out as state store never got configured successfully.