Add End-to-End Integration Tests for User Workflows

guisea commented

2025-07-01 14:53:12 +12:00

Owner

Overview

Create comprehensive end-to-end tests that verify complete user workflows from HTTP request through business logic to database persistence.

Current State

✅ Unit tests for individual components
✅ Basic API integration test framework (attachments)
❌ No end-to-end workflow testing
❌ No WebSocket testing
❌ No file storage integration testing

Required E2E Test Scenarios

Core User Workflows

New User Onboarding
- User registration → Email verification → Organization creation → Account setup
Transaction Recording Workflow
- Create accounts → Record transaction with splits → Verify balances
Multi-Currency Operations
- Set up currency accounts → Record foreign transactions → Price conversions
File Attachment Workflow
- Upload files → Link to transactions → Download/retrieve files

Advanced Workflows

Organization Management
- Create org → Invite users → Manage permissions → Data isolation
Budget Management
- Create budget categories → Track spending → Generate reports
API Key Authentication
- Generate API keys → Use for programmatic access → Revoke keys

System Integration

WebSocket Real-time Updates (if implemented)
File Storage Integration (upload directory management)
Authentication Session Management
Cross-browser Compatibility (if web frontend exists)

Implementation Strategy

Build on existing integration test framework
Use test containers for database isolation
Create test data factories for complex scenarios
Include performance testing for realistic data volumes
Test both happy path and error scenarios

Acceptance Criteria

Complete user workflows are tested end-to-end
Tests run against production-like environment
All major features have workflow coverage
Tests can be run in CI/CD pipeline
Performance benchmarks are established

## Overview Create comprehensive end-to-end tests that verify complete user workflows from HTTP request through business logic to database persistence. ## Current State - ✅ Unit tests for individual components - ✅ Basic API integration test framework (attachments) - ❌ No end-to-end workflow testing - ❌ No WebSocket testing - ❌ No file storage integration testing ## Required E2E Test Scenarios ### Core User Workflows - [ ] **New User Onboarding** - User registration → Email verification → Organization creation → Account setup - [ ] **Transaction Recording Workflow** - Create accounts → Record transaction with splits → Verify balances - [ ] **Multi-Currency Operations** - Set up currency accounts → Record foreign transactions → Price conversions - [ ] **File Attachment Workflow** - Upload files → Link to transactions → Download/retrieve files ### Advanced Workflows - [ ] **Organization Management** - Create org → Invite users → Manage permissions → Data isolation - [ ] **Budget Management** - Create budget categories → Track spending → Generate reports - [ ] **API Key Authentication** - Generate API keys → Use for programmatic access → Revoke keys ### System Integration - [ ] **WebSocket Real-time Updates** (if implemented) - [ ] **File Storage Integration** (upload directory management) - [ ] **Authentication Session Management** - [ ] **Cross-browser Compatibility** (if web frontend exists) ## Implementation Strategy 1. Build on existing integration test framework 2. Use test containers for database isolation 3. Create test data factories for complex scenarios 4. Include performance testing for realistic data volumes 5. Test both happy path and error scenarios ## Acceptance Criteria - [ ] Complete user workflows are tested end-to-end - [ ] Tests run against production-like environment - [ ] All major features have workflow coverage - [ ] Tests can be run in CI/CD pipeline - [ ] Performance benchmarks are established

guisea added the enhancement label 2025-07-01 14:53:12 +12:00

guisea self-assigned this 2025-07-01 14:53:12 +12:00

Add End-to-End Integration Tests for User Workflows #3