Testing

Rack Gateway uses unit, integration, and end-to-end tests across Go and web codebases. Use task commands to keep codegen, containers, and test dependencies in sync.

Test Overview

Test Type	Location	Command
Go Unit + Integration	`internal/**`	`task go:test`
Web Unit	`web/src/*/.test.ts*`	`task web:test`
Web E2E	`web/e2e/`	`task web:e2e`
CLI E2E	`scripts/cli-e2e.sh`	`task go:e2e`

Running Tests

Full Test Suite

task ci

Go Tests

task go:test

Web Tests

task web:test

E2E Tests

# Web E2E
task web:e2e

# CLI E2E
task go:e2e

Focused E2E Runs

Use --grep to run a single Playwright test:

task web:e2e -- --grep "manage MFA"

CLI E2E filters are exposed as task variants:

task go:e2e:admin
task go:e2e:api-token
task go:e2e:deployer
task go:e2e:viewer

Test Layout

internal/
├── gateway/          # Unit + integration tests alongside code
└── integration/      # Additional integration scenarios

web/
├── src/              # Vitest unit tests
└── e2e/              # Playwright tests

Writing Tests

Keep unit tests close to the code under test (*_test.go, *.test.tsx).
Use E2E tests for cross-service workflows (OAuth, RBAC, deploy approvals).
Prefer task commands so the local environment matches CI behavior.