mirror of
https://github.com/redis/go-redis.git
synced 2025-10-20 09:52:25 +03:00
75ddeb3d5a
* e2e wip * cleanup * remove unused fault injector mock * errChan in test * remove log messages tests * cleanup log messages * s/hitless/maintnotifications/ * fix moving when none * better logs * test with second client after action has started * Fixes Signed-off-by: Elena Kolevska <elena@kolevska.com> * Test fix Signed-off-by: Elena Kolevska <elena@kolevska.com> * feat(e2e-test): Extended e2e tests * imroved e2e test resiliency --------- Signed-off-by: Elena Kolevska <elena@kolevska.com> Co-authored-by: Elena Kolevska <elena@kolevska.com> Co-authored-by: Elena Kolevska <elena-kolevska@users.noreply.github.com> Co-authored-by: Hristo Temelski <hristo.temelski@redis.com>
22 lines
1.1 KiB
Go
22 lines
1.1 KiB
Go
// Package e2e provides end-to-end testing scenarios for the maintenance notifications system.
|
|
//
|
|
// This package contains comprehensive test scenarios that validate the maintenance notifications
|
|
// functionality in realistic environments. The tests are designed to work with Redis Enterprise
|
|
// clusters and require specific environment configuration.
|
|
//
|
|
// Environment Variables:
|
|
// - E2E_SCENARIO_TESTS: Set to "true" to enable scenario tests
|
|
// - REDIS_ENDPOINTS_CONFIG_PATH: Path to endpoints configuration file
|
|
// - FAULT_INJECTION_API_URL: URL for fault injection API (optional)
|
|
//
|
|
// Test Scenarios:
|
|
// - Basic Push Notifications: Core functionality testing
|
|
// - Endpoint Types: Different endpoint resolution strategies
|
|
// - Timeout Configurations: Various timeout strategies
|
|
// - TLS Configurations: Different TLS setups
|
|
// - Stress Testing: Extreme load and concurrent operations
|
|
//
|
|
// Note: Maintenance notifications are currently supported only in standalone Redis clients.
|
|
// Cluster clients (ClusterClient, FailoverClient, etc.) do not yet support this functionality.
|
|
package e2e
|