Testing

Vezta has three subprojects with different test setups. All use TypeScript and share common patterns for mocking external APIs.

Frontend (Vitest)

The frontend uses Vitest with jsdom environment and globals enabled.

cd vezta-fe
pnpm test                                  # Run all tests
pnpm exec vitest run navbar                # Run a specific test file (pnpm test -- <path> does NOT filter)
pnpm test -- -t "test name"                # Run tests matching a name
pnpm test -- --coverage                    # Run with v8 coverage

Coverage thresholds: 80% statements/lines/functions, 75% branches. Coverage includes lib/, hooks/, features/, components/, and proxy.ts -- but excludes lib/api/gen/ and lib/mock/.

Test Utilities

• Query wrapper (test-utils/query-wrapper.tsx) -- creates a fresh QueryClient per test for TanStack Query
• Jotai wrapper (test-utils/jotai-wrapper.tsx) -- Provider wrapper for testing Jotai atoms
• Zustand auto-reset (__mocks__/zustand.ts) -- all Zustand stores reset between tests via vitest.setup.ts

MSW Mocking

MSW v2 intercepts all network requests during tests. Handlers are organized by domain in src/mocks/handlers/: alerts, comments, events, leaderboard, markets, notifications, portfolio, rewards, user. The MSW server is configured with onUnhandledRequest: 'error', meaning any unmocked API call will fail the test.

Playwright E2E

End-to-end tests live in e2e/ and run with Playwright (Chromium only). The dev server must be started manually before running tests -- Playwright does not start it.

pnpm dev                  # Start dev server first
npx playwright test       # Then run E2E tests

Backend (Jest)

The backend uses Jest with ts-jest transform. Unit tests are co-located as *.spec.ts files in src/.

cd vezta-be
pnpm test                                    # Run all unit tests
pnpm test -- --testPathPattern=order         # Run a specific test
pnpm test:watch                              # Watch mode
pnpm test:cov                                # With coverage
pnpm test:e2e                                # E2E tests

Test Utilities

Factories

Test data factories in test/factories/ generate realistic objects for tests:

• order.factory -- creates Order objects with valid state machine transitions
• market.factory -- creates Market objects with Polymarket or Kalshi source data
• user.factory -- creates User objects with wallet addresses
• position.factory -- creates Position objects with PnL calculations
• job.factory -- creates BullMQ Job mocks

Unit Test Pattern

import { Test } from '@nestjs/testing';
import { mock, MockProxy } from 'jest-mock-extended';

describe('OrderService', () => {
  let service: OrderService;
  let prisma: MockProxy<PrismaService>;

  beforeEach(async () => {
    const module = await Test.createTestingModule({
      providers: [
        OrderService,
        { provide: PrismaService, useValue: mock<PrismaService>() },
      ],
    }).compile();

    service = module.get(OrderService);
    prisma = module.get(PrismaService);
  });
});

E2E Test Infrastructure

E2E tests use Docker service containers to avoid conflicts with development databases:

The E2E config is in test/jest-e2e.json with a 30-second timeout.

Mobile

The mobile app is planned but not yet implemented. The intended testing stack is Jest 30 + React Native Testing Library, matching the rest of the ecosystem.

CI/CD Integration

CI workflows run on pull requests to dev / staging / main: