CS API Compliance Assessor

Status: v1.0 frozen 2026-04-27 — developer pre-flight tool, not certification-track. This Next.js web app gives implementers fast, automated CS API conformance feedback during development. The certification-track Java/TestNG Executable Test Suite for OGC TeamEngine is being developed in the sibling repository ets-ogcapi-connectedsystems10 (under construction — design spec at openspec/capabilities/ets-ogcapi-connectedsystems/). v1.0 HEAD is tagged v1.0-frozen at ab53658. Bug fixes welcome here; new feature work goes to the ETS repo.

A web application that performs comprehensive conformance assessment of endpoints implementing the OGC API - Connected Systems standard. Enter an endpoint URL, and the tool automatically discovers its capabilities, runs requirement-level tests against the OGC specification, and produces detailed compliance reports — useful as a developer pre-flight before submitting to the certification-track ETS.

What It Tests

Standard	Document	Requirements	Conformance Classes
OGC API - Common Part 1	OGC 19-072	Core building blocks	Landing page, conformance, JSON, OpenAPI
OGC API - Features Part 1	OGC 17-069	Feature collections	Collections, items, GeoJSON
CS API Part 1: Feature Resources	OGC 23-001	103 requirements	Systems, deployments, procedures, sampling features, properties, filtering, CRUD, GeoJSON, SensorML
CS API Part 2: Dynamic Data	OGC 23-002	130 requirements	Datastreams, observations, control streams, commands, feasibility, events, history, SWE encodings

233 OGC requirements tested across 28 conformance classes with 1003 unit tests + 25 Playwright E2E tests (22 always-run + 3 live-IUT, chromium + firefox verified).

Quick Start

Docker (recommended)

docker-compose up -d

Open http://localhost:3000 and enter a CS API endpoint URL.

From Source

Requires Node.js 20+.

# Install dependencies
npm install

# Fetch OGC schemas (build-time)
npm run fetch-schemas

# Start development server
npm run dev

Open http://localhost:3000.

Try It

Use the OGC demo server to test: https://api.georobotix.io/ogc/t18/api

How It Works

1. Discover -- Enter an endpoint URL. The tool fetches the landing page, reads the /conformance declaration, and maps declared conformance classes to testable requirements.

2. Configure -- Select which conformance classes to test. Optionally provide authentication (Bearer, API key, Basic) and adjust timeout/concurrency settings. Write-operation tests (CRUD/Update) require explicit opt-in.

3. Test -- The engine runs tests in dependency order with real-time progress via Server-Sent Events. Each test maps 1:1 to an OGC requirement URI. Failed tests include the specific assertion that failed and the full HTTP request/response exchange.

4. Report -- View results in an interactive dashboard with per-class breakdown, compliance percentage, and a test detail drawer showing HTTP traces. Export as JSON (versioned schema) or PDF.

Features

• 28 conformance class test modules covering OGC 23-001 (Part 1) and OGC 23-002 (Part 2)
• Requirement-level traceability -- every test maps to a canonical /req/ URI from the OGC standard
• Real-time progress via SSE with cancellation support
• Full HTTP capture with credential masking (first 4 + last 4 chars)
• JSON and PDF export with versioned schema and disclaimer
• SSRF protection -- blocks requests to private/internal IP ranges
• WCAG 2.1 AA accessible -- skip links, focus management, aria-live regions, non-color status indicators
• i18n ready -- 148 externalized strings with interpolation support
• Docker deployment -- single docker-compose up command

Development

# Run unit tests (1003 tests, ~3s)
npm test

# Run E2E tests (Playwright, Chromium)
npm run test:e2e

# Run across all browsers (chromium + firefox + webkit; webkit needs system deps via sudo)
npm run test:e2e:all-browsers

# Run E2E against a live Connected Systems IUT (exercises TC-E2E-001/004/005)
IUT_URL=https://api.georobotix.io/ogc/t18/api npm run test:e2e

# Type check
npm run typecheck

# Lint
npm run lint

# Performance benchmark against live server
npm run perf

# Smoke test discovery against OGC demo server
npx tsx scripts/smoke-test.ts

Project Structure

src/
  app/                    # Next.js pages (landing, config, progress, results)
  components/             # React components (wizard, results dashboard, drawer)
  engine/                 # Test engine core
    registry/             # 28 conformance class test modules
    test-runner.ts        # Orchestrator (dependency order, concurrency, progress)
    discovery-service.ts  # Endpoint discovery + conformance mapping
    schema-validator.ts   # Ajv-based JSON schema validation
    http-client.ts        # HTTP client with capture, auth, SSRF guard
  server/                 # Express server, API routes, middleware
  services/               # Frontend API + SSE clients
  lib/                    # Shared types, constants, i18n
schemas/                  # Bundled OGC JSON schemas (fetched at build time)
tests/                    # Unit tests (Vitest) + E2E tests (Playwright)

Built With

Layer	Technology
Frontend	Next.js 14, React 18, TypeScript, Tailwind CSS
Backend	Express, Node.js 22, TypeScript
Schema Validation	Ajv 8 with OGC OpenAPI schemas
PDF Export	PDFKit
Testing	Vitest (1003 unit tests), Playwright (25 E2E tests)
Deployment	Docker, docker-compose

Development Methodology

This project was built using spec-anchored development via the BMAD + OpenSpec framework:

• BMAD agents (Discovery, PM, Architect, Design, Developer, QA, Red Team, Scrum Master) each operate with fresh context windows, producing artifacts that feed the next stage
• Four quality gates enforced by scripts/orchestrate.py: Gate 1 (self-check: tests/types/lint), Gate 2 (Evaluator/Quinn independent QA), Gate 3 (Reconciliation), Gate 4 (Adversarial/Raze Red Team review — can override an Evaluator APPROVE)
• OpenSpec capabilities define testable requirements (REQ-*) and acceptance scenarios (SCENARIO-*) that trace from PRD through to tests
• Full traceability chain: User Need → PRD (59 FRs) → OpenSpec REQ-* → Stories (39) → Tests (1003) → Implementation

The complete specification, architecture, UX design, epics, stories, and traceability matrix live in the repository under _bmad/, openspec/, and epics/. Per-sprint Raze Gate 4 verdicts are archived under .harness/evaluations/.

Disclaimer

This tool is unofficial and does not constitute OGC certification. Results are based on automated testing against the OGC 23-001 and OGC 23-002 standards and may not cover all edge cases. For official OGC compliance certification, the certification path is the OGC TeamEngine + an Executable Test Suite — that ETS is being developed in the sibling repository ets-ogcapi-connectedsystems10. General OGC compliance information at ogc.org/compliance.

License

MIT