Tests in Gods Eye View Repository: Automated Suite Coverage Guide

Yes, the gods-eye-view repository ships with an extensive automated test suite comprising over 70 ECMAScript module test files that verify voice AI integration, real-time data layers, scene management, and rendering systems.

The gods-eye-view project maintains a robust testing infrastructure designed to ensure reliability across its complex real-time visualization stack. These automated tests validate everything from OpenAI Realtime API integrations to live flight data ingestion, providing comprehensive regression coverage for the entire client-side codebase.

Test Architecture and File Organization

The gods-eye-view test suite uses ECMAScript modules with the *.test.mjs naming convention. Unlike traditional frameworks that segregate tests into a separate directory, the project co-lates test files with their source counterparts under the src/ directory. This proximity ensures that tests remain synchronized with implementation changes.

The suite utilizes a lightweight custom test runner defined in src/unitTestRunner.test.mjs. This harness discovers and executes test modules without requiring external dependencies like Jest or Mocha, keeping the project's footprint minimal while maintaining full automated verification capabilities.

Core Testing Coverage Areas

The tests span virtually every subsystem of the application, from low-level data adapters to high-level UI orchestration.

Voice and AI Integration

The voice control subsystem includes dedicated tests for cost estimation and streaming behavior:

• src/voice/voiceCost.test.mjs – Validates calculations for estimated OpenAI Realtime usage costs.
• src/voice/gevRealtime.test.mjs – Verifies the OpenAI Realtime streaming client behavior and audio handling logic.

These tests ensure that the src/voice/gevRealtime.js implementation correctly manages WebRTC connections and API communication.

Real-Time Data Layer Validation

The data ingestion pipeline exercises multiple live feeds and caching mechanisms:

• src/data/flights.test.mjs – Ensures proper ingestion, filtering, and rendering logic for live aircraft data processed by src/data/flights.js.
• src/data/earthquakes.test.mjs – Verifies earthquake feed parsing and seismic visualization logic.
• src/data/aisLiveVessels.test.mjs – Tests maritime AIS (Automatic Identification System) vessel tracking integration.
• src/data/cctvProxy.test.mjs – Validates proxy handling and data transformation for public camera feeds.

Scene Management and Rendering Performance

Cinematic and rendering systems are validated for stability under varying load conditions:

• src/scenes/director.test.mjs – Checks the cinematic scene director actions, camera tours, and transitions implemented in src/scenes/director.js.
• src/renderGovernor.test.mjs – Confirms frame-budget throttling and adaptive quality control mechanisms in src/renderGovernor.js.
• src/weatherEffectsMath.test.mjs – Validates mathematical calculations for atmospheric visual effects.

UI and HUD Components

User interface elements undergo rigorous behavioral testing:

• src/hudAltitudeDatum.test.mjs – Validates altitude-datum display conversions and telemetry rendering.
• src/annotations/annotationEngine.test.mjs – Tests the user-drawn annotation system core engine.
• src/firstRunExperience.test.mjs – Verifies the onboarding flow and mission staging sequence for new users.

Running the Gods Eye View Test Suite

Executing the full test suite requires only standard Node.js tooling. The package.json defines a test script that invokes the internal runner to discover all *.test.mjs files throughout the src/ tree.

# Install dependencies

npm install

# Execute all tests

npm test

The runner automatically imports and executes each test module, reporting pass/fail status for the entire suite including src/hud.js, src/ui.js, and src/main.js integration points.

Summary

• Over 70 test modules provide comprehensive coverage across the gods-eye-view codebase.
• Tests utilize ESM format (*.test.mjs) co-located with source files under src/.
• Custom lightweight runner in src/unitTestRunner.test.mjs eliminates external testing framework dependencies.
• Critical subsystems validated include voice AI, live flight/earthquake/vessel data, scene direction, and rendering budgets.
• Execution is standardized via npm test following dependency installation.

Frequently Asked Questions

How many tests are included in the gods-eye-view repository?

The repository contains over 70 individual test modules, with each *.test.mjs file targeting specific functionality such as voice integration, data layer parsing, or UI component behavior.

What testing framework does gods-eye-view use?

Rather than Jest or Mocha, the project implements a custom lightweight test runner located at src/unitTestRunner.test.mjs. This bespoke harness uses native ECMAScript modules to load and execute tests, reducing external dependencies while maintaining comprehensive verification capabilities.

How do I execute the test suite locally?

Run npm test after installing dependencies with npm install. The npm script invokes the built-in runner that discovers all *.test.mjs files under src/, including critical tests for src/voice/gevRealtime.js and src/data/flights.js.

Does the test suite cover the OpenAI Realtime integration?

Yes, the voice subsystem is thoroughly tested via src/voice/gevRealtime.test.mjs for streaming client validation and src/voice/voiceCost.test.mjs for usage cost estimation, ensuring reliable operation of the Realtime API features.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}