{ "test_users": [ { "email": "loadtest1@example.com", "password": "LoadTest123!", "user_id": "test-user-1", "description": "Primary load test user" }, { "email": "loadtest2@example.com", "password": "LoadTest123!", "user_id": "test-user-2", "description": "Secondary load test user" }, { "email": "loadtest3@example.com", "password": "LoadTest123!", "user_id": "test-user-3", "description": "Tertiary load test user" }, { "email": "stresstest1@example.com", "password": "StressTest123!", "user_id": "stress-user-1", "description": "Stress test user with higher limits" }, { "email": "stresstest2@example.com", "password": "StressTest123!", "user_id": "stress-user-2", "description": "Stress test user with higher limits" } ], "admin_users": [ { "email": "admin@example.com", "password": "AdminTest123!", "user_id": "admin-user-1", "description": "Admin user for testing admin endpoints", "permissions": ["admin", "read", "write", "execute"] } ], "service_accounts": [ { "name": "load-test-service", "description": "Service account for automated load testing", "permissions": ["read", "write", "execute"] } ], "notes": [ "⚠️ IMPORTANT: These are placeholder test users.", "📝 Before running tests, you must:", " 1. Create actual test accounts in your Supabase instance", " 2. Update the credentials in this file", " 3. Ensure test users have sufficient credits for testing", " 4. Set up appropriate rate limits for test accounts", " 5. Configure test data cleanup procedures", "", "🔒 Security Notes:", " - Never use production user credentials for testing", " - Use dedicated test environment and database", " - Implement proper test data isolation", " - Clean up test data after test completion", "", "💳 Credit Management:", " - Ensure test users have sufficient credits", " - Monitor credit consumption during tests", " - Set up auto-top-up for test accounts if needed", " - Track credit costs for load testing budget planning" ] }