​

Testing Architecture

​

Overview

​

Test Frameworks

​

Frontend Testing (equa-web)

​

Unit Tests (Jest 29 + React Testing Library)

• Framework: Jest 29 with React Testing Library 14 (migrated from Jest 26 + Enzyme in PR #465)
• Location: Colocated *.test.ts / *.test.tsx files alongside source
• Mock pattern: Pattern library mocked via equa-web/src/shared/mocks/patternlibMock.js
• Coverage: No explicit thresholds configured
• Test count: 52 tests passing

​

E2E Tests (Playwright)

​

Visual Regression Tests (PR #509)

​

Running Tests

# Unit tests
cd ~/Documents/repos/equa-web
yarn test

# E2E tests (requires frontend + backend running)
yarn test:e2e

​

Backend Testing (equa-server)

• Framework: Varies by module (some use Jest, some use native Node test runner)
• S3Client mocking: Documented in equa-server/modules/api/README.md
• Database: Tests run against a test database (requires PostgreSQL)

​

Command Center Testing

• Framework: Playwright
• Config: command-center-so/playwright.config.ts
• Scope: Chat interface, gateway connection, settings, error reporting

​

CI Pipeline

​

Backend (GitHub Actions validation + legacy Cloud Build path)

1. GitHub Actions runs install, type checks, API tests, and a Docker build check on pushes to `main`, `staging`, and `prod-deploy`
2. Railway service config defines the current runtime target shape for `equa-server`
3. Cloud Build / Cloud Run config remains in the repo as a legacy deploy path, not as the primary browser-facing runtime story

​

Frontend (GitHub Actions)

1. Lint & Build (ESLint + webpack production build)
2. Unit Tests (Jest 29 + React Testing Library)
3. E2E Smoke (Playwright)
4. Regression Tests
5. Visual Regression Tests (screenshot comparison)

​

Frontend Deployment (Railway)

1. nixpacks detects Node.js
2. yarn install
3. yarn build (webpack production build)
4. Deploy

​

Test Data Management

• Development: Schema sync enabled (DATABASE_SYNC !== 'false' in development)
• Production: Schema migrations managed via TypeORM
• Seed data: No automated seed scripts found

​

Coverage Gaps

​

Recommended Improvements

1. Add coverage thresholds to Jest config (target: 70% lines/branches)
2. Create seed data scripts for consistent local testing
3. Expand E2E test coverage to all major user flows
4. Add API integration tests for endpoint validation
5. Implement performance benchmarks for critical paths