Cloud E2E Integration Test Guide

This guide provides step-by-step instructions for testing the full cloud-hosted Auto Code workflow.

Test Overview

This end-to-end test validates the complete cloud infrastructure:

User Signup - New user registration via API
User Login - Authentication and JWT token retrieval
OAuth Integration - GitHub OAuth connection flow
Usage Tracking - Redis-based API usage analytics
Database Operations - PostgreSQL user data persistence

Prerequisites

Before running the tests, ensure you have:

Docker and Docker Compose installed
Python 3.12+ with requests library
Git for repository operations
Ports available: 5432 (PostgreSQL), 6379 (Redis), 8000 (Backend API)

Quick Start

Step 1: Start the Cloud Stack

cd apps/web-backend

# Start all services (PostgreSQL, Redis, Backend)
docker-compose -f docker-compose.cloud.yml up -d

# Wait for services to become healthy (30-60 seconds)
docker-compose -f docker-compose.cloud.yml ps

# Expected output:
# autoclaude-postgres   ... Up (healthy)
# autoclaude-redis      ... Up (healthy)
# autoclaude-backend    ... Up (healthy)

Step 2: Initialize Database

# Run database migrations
docker exec autoclaude-backend alembic upgrade head

# Verify migrations
docker exec autoclaude-backend alembic current

# Expected output: 002_create_repositories (head)

Step 3: Run E2E Tests

# Option 1: Run Python test script
python tests/test_cloud_e2e.py

# Option 2: Run bash test script
bash tests/run_e2e_tests.sh

# Option 3: Manual API testing (see below)

Manual Testing Steps

Test 1: Health Check

curl -X GET http://localhost:8000/health

# Expected: 200 OK
# {"status":"ok","database":"connected","redis":"connected"}

Test 2: User Signup

curl -X POST http://localhost:8000/api/users/register \
  -H "Content-Type: application/json" \
  -d '{
    "email": "test@example.com",
    "password": "testpass123"
  }'

# Expected: 201 Created
# {
#   "id": 1,
#   "email": "test@example.com",
#   "is_active": true,
#   "is_verified": false,
#   "created_at": "2024-02-04T12:00:00Z"
# }

Test 3: User Login

curl -X POST http://localhost:8000/api/users/login \
  -H "Content-Type: application/json" \
  -d '{
    "email": "test@example.com",
    "password": "testpass123"
  }'

# Expected: 200 OK
# {
#   "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
#   "token_type": "bearer",
#   "user": {
#     "id": 1,
#     "email": "test@example.com"
#   }
# }

# Save the access_token for subsequent requests
export ACCESS_TOKEN="<token-from-response>"

Test 4: OAuth Status

curl -X GET http://localhost:8000/api/git/status

# Expected: 200 OK
# {
#   "github": {
#     "configured": true,
#     "client_id": "test_client_id"
#   },
#   "gitlab": {
#     "configured": false
#   }
# }

Test 5: GitHub OAuth Redirect

curl -X GET http://localhost:8000/api/git/github/authorize \
  -H "Cookie: session=..." \
  -L -v

# Expected: 302 Redirect to GitHub
# Location: https://github.com/login/oauth/authorize?client_id=...&redirect_uri=...&scope=...&state=...

Test 6: Usage Tracking Dashboard

curl -X GET "http://localhost:8000/api/usage/dashboard?user_id=1"

# Expected: 200 OK
# {
#   "user_id": 1,
#   "total_requests_today": 5,
#   "total_requests_this_month": 5,
#   "redis_healthy": true
# }

Test 7: Usage Statistics

curl -X GET "http://localhost:8000/api/usage/stats?user_id=1&period=daily&days_back=7"

# Expected: 200 OK
# {
#   "user_id": 1,
#   "period": "daily",
#   "days_back": 7,
#   "usage_data": [
#     {
#       "period_start": "2024-02-04T00:00:00Z",
#       "request_count": 5,
#       "unique_endpoints": 3
#     }
#   ],
#   "total_requests": 5,
#   "redis_healthy": true
# }

Test 8: Usage Health (Redis)

curl -X GET http://localhost:8000/api/usage/health

# Expected: 200 OK
# {
#   "status": "healthy",
#   "redis_healthy": true,
#   "message": "Usage tracking is operational"
# }

Database Verification

Check Users Table

docker exec -it autoclaude-postgres psql -U postgres -d autoclaude -c "SELECT id, email, is_active, created_at FROM users;"

# Expected:
#  id |       email        | is_active |         created_at
# ----+--------------------+-----------+----------------------------
#   1 | test@example.com   | t         | 2024-02-04 12:00:00.123456

Check Repositories Table

docker exec -it autoclaude-postgres psql -U postgres -d autoclaude -c "SELECT * FROM repositories;"

# Expected: Empty table (no OAuth connections yet)

Check Migration Status

docker exec autoclaude-backend alembic current

# Expected: 002_create_repositories (head)

Redis Verification

Check Usage Tracking Data

# Connect to Redis
docker exec -it autoclaude-redis redis-cli

# Inside Redis CLI:
KEYS usage:*

# Expected: Keys like:
# 1) "usage:user:1:daily:2024-02-04"
# 2) "usage:user:1:hourly:2024-02-04:12"
# 3) "usage:user:1:monthly:2024-02"

# Check specific key:
GET "usage:user:1:daily:2024-02-04"

# Expected: Number (request count for the day)

Frontend Testing

Test Sign-up Page

# Option 1: Open in browser
open http://localhost:3000/signup

# Option 2: Start frontend dev server
cd apps/web-frontend
npm run dev

# Navigate to http://localhost:3000/signup

Verification Steps:

Fill in email: test2@example.com
Fill in password: password123
Confirm password: password123
Click "Sign Up"
Verify success message or redirect

Test Login Page

# Navigate to http://localhost:3000/login
open http://localhost:3000/login

Verification Steps:

Fill in email: test@example.com
Fill in password: testpass123
Click "Log In"
Verify redirect to dashboard or home page

Test Usage Dashboard

# Navigate to http://localhost:3000/usage
open http://localhost:3000/usage

Verification Steps:

Verify summary cards display (Today, This Month, Total)
Verify usage chart renders
Verify usage details table shows data
Verify Redis health indicator

Test GitHub OAuth Connection

# Navigate to http://localhost:3000/settings/git
open http://localhost:3000/settings/git

Verification Steps:

Click "Connect GitHub Account"
Verify redirect to GitHub OAuth
Complete OAuth flow (requires real GitHub OAuth app)
Verify redirect back to settings page
Verify GitHub account shows as connected

Troubleshooting

Services Not Starting

# Check container logs
docker-compose -f docker-compose.cloud.yml logs postgres
docker-compose -f docker-compose.cloud.yml logs redis
docker-compose -f docker-compose.cloud.yml logs web-backend

# Restart services
docker-compose -f docker-compose.cloud.yml restart

Database Connection Issues

# Check PostgreSQL is running
docker exec autoclaude-postgres pg_isready -U postgres

# Check database exists
docker exec autoclaude-postgres psql -U postgres -c "\l"

# Recreate database if needed
docker exec autoclaude-postgres psql -U postgres -c "DROP DATABASE IF EXISTS autoclaude; CREATE DATABASE autoclaude;"

Redis Connection Issues

# Check Redis is running
docker exec autoclaude-redis redis-cli ping

# Expected: PONG

# Flush Redis data (if needed)
docker exec autoclaude-redis redis-cli FLUSHALL

Migration Errors

# Check current migration status
docker exec autoclaude-backend alembic current

# View migration history
docker exec autoclaude-backend alembic history

# Downgrade and re-apply
docker exec autoclaude-backend alembic downgrade base
docker exec autoclaude-backend alembic upgrade head

API Errors

# Check backend logs
docker logs autoclaude-backend --tail 100 -f

# Check for common issues:
# - Database not initialized (run migrations)
# - Redis not available (check redis container)
# - Missing environment variables (check .env file)

Clean Up

Stop Services

cd apps/web-backend
docker-compose -f docker-compose.cloud.yml down

Remove Data Volumes

# WARNING: This will delete all data!
docker-compose -f docker-compose.cloud.yml down -v

Complete Reset

# Stop and remove everything
docker-compose -f docker-compose.cloud.yml down -v --remove-orphans

# Remove test user from database
docker exec autoclaude-postgres psql -U postgres -d autoclaude -c "DELETE FROM users WHERE email = 'test@example.com';"

Test Success Criteria

All tests pass if:

✅ Backend API health check returns 200 OK
✅ PostgreSQL database is accessible and migrations applied
✅ Redis is accessible and tracking usage
✅ User signup creates new user in database
✅ User login returns valid JWT token
✅ OAuth status endpoint shows GitHub configured
✅ OAuth authorize redirects to GitHub (302)
✅ Usage dashboard returns statistics
✅ Usage health shows Redis connected
✅ Frontend pages render correctly (signup, login, usage, settings)

Next Steps

After successful E2E testing:

Create integration test suite (subtask-6-2)
Run security scan (verify no secrets in code)
Deploy to staging (test on real cloud infrastructure)
Performance testing (load testing with multiple users)
User acceptance testing (UAT with real users)

FilesExpand file tree

E2E_TEST_GUIDE.md

Latest commit

History

E2E_TEST_GUIDE.md

File metadata and controls

Cloud E2E Integration Test Guide

Test Overview

Prerequisites

Quick Start

Step 1: Start the Cloud Stack

Step 2: Initialize Database

Step 3: Run E2E Tests

Manual Testing Steps

Test 1: Health Check

Test 2: User Signup

Test 3: User Login

Test 4: OAuth Status

Test 5: GitHub OAuth Redirect

Test 6: Usage Tracking Dashboard

Test 7: Usage Statistics

Test 8: Usage Health (Redis)

Database Verification

Check Users Table

Check Repositories Table

Check Migration Status

Redis Verification

Check Usage Tracking Data

Frontend Testing

Test Sign-up Page

Test Login Page

Test Usage Dashboard

Test GitHub OAuth Connection

Troubleshooting

Services Not Starting

Database Connection Issues

Redis Connection Issues

Migration Errors

API Errors

Clean Up

Stop Services

Remove Data Volumes

Complete Reset

Test Success Criteria

Next Steps

Additional Resources