#Testing & Quality Assurance

SyncingBoard enforces strict automated testing across security, rate limiting, URL parsing, and serverless API endpoints using Vitest.

#Testing Strategy & Infrastructure

SyncingBoard's test suite runs inside Vitest (yarn test) in zero-network isolation. All external Figma, Miro, Ably, and Upstash Redis network calls are mocked (or isolated behind pure functions) to ensure 100% deterministic test execution in seconds.

#Test Suites Breakdown

SyncingBoard includes 123 passing automated tests across 16 specialized test files:

#Running Tests Locally

Run the test suite during development using the following commands:

# Run all 123 tests once
yarn test

# Run tests in interactive watch mode
yarn test --watch

# Run tests with UI dashboard
yarn test --ui

# Verify TypeScript types and ESLint rules
yarn lint

# Verify full production build compilation
yarn build

#Mocking Principles & Zero-Network Guarantee

To ensure tests execute fast without requiring real API keys or external services:

1. Figma REST API: Mocked via global.fetch spies returning sample JSON frame hierarchies and binary PNG buffers.
2. Upstash Redis: Mocked using in-memory sliding window state stores (Map<string, { count, reset }>) so rate-limiting logic is tested without live Redis connections.
3. Miro Web SDK: Mocked using synthetic widget objects asserting isLocked, title, and scale properties.
4. Relay fairness (Redis Lua): The atomic Lua scripts are mirrored as exported pure functions (planAcquire, planTransfer, selectEvictionCandidate, planCompanionTokenAcquisition, planCompanionBinding) tested directly — the Redis behavior is verified without a live Upstash instance, and the Lua executes the same decision rules server-side.