Testsuite support component.
Provides additional functionality for testing, e.g. forced cache updates.
Static options:
| Name | Description | Default value |
| testsuite-periodic-update-enabled | whether caches update periodically | true |
| testsuite-pg-execute-timeout | execute timeout override for postgres | - |
| testsuite-pg-statement-timeout | statement timeout override for postgres | - |
| testsuite-pg-readonly-master-expected | mutes readonly master detection warning | false |
| testsuite-redis-timeout-connect | minimum connection timeout for redis | - |
| testsuite-redis-timeout-single | minimum single shard timeout for redis | - |
| testsuite-redis-timeout-all | minimum command timeout for redis | - |
| testsuite-tasks-enabled | enable testsuite tasks facility | false |
| testsuite-increased-timeout | increase timeouts for connections, statement executions, RPC timeouts to avoid timeouts happening in testing environments, where the hardware differs from production. Overrides postgres, redis and grpc timeouts if these are missing | 0ms |
| cache-update-execution | If 'sequential' the caches are updated by testsuite sequentially in the order for cache component registration, which makes sense if service has components that push value into a cache component. If 'concurrent' the caches are updated concurrently with respect to the cache component dependencies. | concurrent |
Static configuration example:
# yaml
testsuite-support:
testsuite-periodic-update-enabled: true
testsuite-pg-execute-timeout: 300ms
testsuite-pg-statement-timeout: 300ms
testsuite-pg-readonly-master-expected: false
testsuite-redis-timeout-connect: 5s
testsuite-redis-timeout-single: 1s
testsuite-redis-timeout-all: 750ms
testsuite-increased-timeout: 40s
cache-update-execution: concurrent
- Examples
- samples/grpc_service/main.cpp, samples/http_caching/main.cpp, and samples/kafka_service/main.cpp.
Definition at line 53 of file testsuite_support.hpp.
Inheritance diagram for components::TestsuiteSupport: