flo-bit.dev / contrail

0

[READ-ONLY] Mirror of https://github.com/flo-bit/contrail. atproto backend in a bottle flo-bit.dev/contrail/

0

contrail / apps / contrail-e2e /

at fix/cleanup-and-docs 3 folders 8 files

Florian Merge remote-tracking branch 'origin/main' into fix/cleanup-and-docs 3mo ago

add contrail-e2e app with end-to-end tests against a local ATProto stack New app under apps/contrail-e2e that brings up a full sealed local ATProto network (PDS, PLC, Jetstream, TAP, Postgres, maildev) via docker-compose and runs three end-to-end test files against it: - health.test.ts — service health checks - ingest-roundtrip.test.ts — publish → index roundtrip, verifying a calendar event and an RSVP land in the DB and that the grouped rsvpsGoingCount is populated via an in-process XRPC handler - cursor-resume.test.ts — regression for runPersistent's durable cursor. Publishes A, stops the ingester, publishes B + updates B + deletes A, restarts, and asserts the saved cursor replays the gap. The basic roundtrip can't catch a broken cursor because events always arrive while the ingester is live. Each test stands up its own runPersistent and XRPC handler in-process against an isolated pg schema (search_path pinned per test), so the suite works with just pnpm stack:up and doesn't fight a dogfooding ingester writing to public.

3 months ago

add contrail-e2e app with end-to-end tests against a local ATProto stack New app under apps/contrail-e2e that brings up a full sealed local ATProto network (PDS, PLC, Jetstream, TAP, Postgres, maildev) via docker-compose and runs three end-to-end test files against it: - health.test.ts — service health checks - ingest-roundtrip.test.ts — publish → index roundtrip, verifying a calendar event and an RSVP land in the DB and that the grouped rsvpsGoingCount is populated via an in-process XRPC handler - cursor-resume.test.ts — regression for runPersistent's durable cursor. Publishes A, stops the ingester, publishes B + updates B + deletes A, restarts, and asserts the saved cursor replays the gap. The basic roundtrip can't catch a broken cursor because events always arrive while the ingester is live. Each test stands up its own runPersistent and XRPC handler in-process against an isolated pg schema (search_path pinned per test), so the suite works with just pnpm stack:up and doesn't fight a dogfooding ingester writing to public.

3 months ago

Merge remote-tracking branch 'origin/main' into fix/cleanup-and-docs # Conflicts: # pnpm-lock.yaml

3 months ago

Merge remote-tracking branch 'origin/main' into fix/cleanup-and-docs # Conflicts: # pnpm-lock.yaml

3 months ago

add contrail-e2e app with end-to-end tests against a local ATProto stack New app under apps/contrail-e2e that brings up a full sealed local ATProto network (PDS, PLC, Jetstream, TAP, Postgres, maildev) via docker-compose and runs three end-to-end test files against it: - health.test.ts — service health checks - ingest-roundtrip.test.ts — publish → index roundtrip, verifying a calendar event and an RSVP land in the DB and that the grouped rsvpsGoingCount is populated via an in-process XRPC handler - cursor-resume.test.ts — regression for runPersistent's durable cursor. Publishes A, stops the ingester, publishes B + updates B + deletes A, restarts, and asserts the saved cursor replays the gap. The basic roundtrip can't catch a broken cursor because events always arrive while the ingester is live. Each test stands up its own runPersistent and XRPC handler in-process against an isolated pg schema (search_path pinned per test), so the suite works with just pnpm stack:up and doesn't fight a dogfooding ingester writing to public.

3 months ago

add contrail-e2e app with end-to-end tests against a local ATProto stack New app under apps/contrail-e2e that brings up a full sealed local ATProto network (PDS, PLC, Jetstream, TAP, Postgres, maildev) via docker-compose and runs three end-to-end test files against it: - health.test.ts — service health checks - ingest-roundtrip.test.ts — publish → index roundtrip, verifying a calendar event and an RSVP land in the DB and that the grouped rsvpsGoingCount is populated via an in-process XRPC handler - cursor-resume.test.ts — regression for runPersistent's durable cursor. Publishes A, stops the ingester, publishes B + updates B + deletes A, restarts, and asserts the saved cursor replays the gap. The basic roundtrip can't catch a broken cursor because events always arrive while the ingester is live. Each test stands up its own runPersistent and XRPC handler in-process against an isolated pg schema (search_path pinned per test), so the suite works with just pnpm stack:up and doesn't fight a dogfooding ingester writing to public.

3 months ago

add contrail-e2e app with end-to-end tests against a local ATProto stack New app under apps/contrail-e2e that brings up a full sealed local ATProto network (PDS, PLC, Jetstream, TAP, Postgres, maildev) via docker-compose and runs three end-to-end test files against it: - health.test.ts — service health checks - ingest-roundtrip.test.ts — publish → index roundtrip, verifying a calendar event and an RSVP land in the DB and that the grouped rsvpsGoingCount is populated via an in-process XRPC handler - cursor-resume.test.ts — regression for runPersistent's durable cursor. Publishes A, stops the ingester, publishes B + updates B + deletes A, restarts, and asserts the saved cursor replays the gap. The basic roundtrip can't catch a broken cursor because events always arrive while the ingester is live. Each test stands up its own runPersistent and XRPC handler in-process against an isolated pg schema (search_path pinned per test), so the suite works with just pnpm stack:up and doesn't fight a dogfooding ingester writing to public.

3 months ago

docker-compose.yml

add contrail-e2e app with end-to-end tests against a local ATProto stack New app under apps/contrail-e2e that brings up a full sealed local ATProto network (PDS, PLC, Jetstream, TAP, Postgres, maildev) via docker-compose and runs three end-to-end test files against it: - health.test.ts — service health checks - ingest-roundtrip.test.ts — publish → index roundtrip, verifying a calendar event and an RSVP land in the DB and that the grouped rsvpsGoingCount is populated via an in-process XRPC handler - cursor-resume.test.ts — regression for runPersistent's durable cursor. Publishes A, stops the ingester, publishes B + updates B + deletes A, restarts, and asserts the saved cursor replays the gap. The basic roundtrip can't catch a broken cursor because events always arrive while the ingester is live. Each test stands up its own runPersistent and XRPC handler in-process against an isolated pg schema (search_path pinned per test), so the suite works with just pnpm stack:up and doesn't fight a dogfooding ingester writing to public.

3 months ago

add e2e tests for spaces auth path and privacy invariants Three new tests in apps/contrail-e2e, each running in-process against a real devnet PDS + PLC + Postgres with spaces enabled: - spaces-auth.test.ts: real service-auth JWT minted via com.atproto.server.getServiceAuth is accepted; wrong aud and wrong lxm binding are rejected. Exercises the full verifier path (PDS signs with the user's PLC-published key, Contrail resolves the key from devnet PLC, @atcute/xrpc-server verifies the signature) — the existing package-level spaces tests all use a fakeAuth header and never touch this path. - spaces-firehose-invisibility.test.ts: records written via {ns}.space.putRecord do not appear on the ATProto firehose. Uses a direct-to-PDS createRecord as a positive control so a silently broken subscriber can't make the negative assertion vacuous. - spaces-table-isolation.test.ts: a space putRecord lands in spaces_records_<collection> with the public records_<collection> table empty for the same caller — proves the store-level separation that the spaces privacy model depends on. helpers.ts gains CONTRAIL_SERVICE_DID, createDevnetResolver (PlcDid- DocumentResolver pointed at devnet PLC), and mintServiceAuthJwt. Adds @atcute/identity-resolver, @atcute/jetstream, and @atcute/lexicons as direct devDependencies.

3 months ago

add contrail-e2e app with end-to-end tests against a local ATProto stack New app under apps/contrail-e2e that brings up a full sealed local ATProto network (PDS, PLC, Jetstream, TAP, Postgres, maildev) via docker-compose and runs three end-to-end test files against it: - health.test.ts — service health checks - ingest-roundtrip.test.ts — publish → index roundtrip, verifying a calendar event and an RSVP land in the DB and that the grouped rsvpsGoingCount is populated via an in-process XRPC handler - cursor-resume.test.ts — regression for runPersistent's durable cursor. Publishes A, stops the ingester, publishes B + updates B + deletes A, restarts, and asserts the saved cursor replays the gap. The basic roundtrip can't catch a broken cursor because events always arrive while the ingester is live. Each test stands up its own runPersistent and XRPC handler in-process against an isolated pg schema (search_path pinned per test), so the suite works with just pnpm stack:up and doesn't fight a dogfooding ingester writing to public.

3 months ago

vitest.config.ts

add contrail-e2e app with end-to-end tests against a local ATProto stack New app under apps/contrail-e2e that brings up a full sealed local ATProto network (PDS, PLC, Jetstream, TAP, Postgres, maildev) via docker-compose and runs three end-to-end test files against it: - health.test.ts — service health checks - ingest-roundtrip.test.ts — publish → index roundtrip, verifying a calendar event and an RSVP land in the DB and that the grouped rsvpsGoingCount is populated via an in-process XRPC handler - cursor-resume.test.ts — regression for runPersistent's durable cursor. Publishes A, stops the ingester, publishes B + updates B + deletes A, restarts, and asserts the saved cursor replays the gap. The basic roundtrip can't catch a broken cursor because events always arrive while the ingester is live. Each test stands up its own runPersistent and XRPC handler in-process against an isolated pg schema (search_path pinned per test), so the suite works with just pnpm stack:up and doesn't fight a dogfooding ingester writing to public.

3 months ago

README.md

contrail-e2e — end-to-end tests against a local ATProto stack#

End-to-end test suite for Contrail against a sealed local ATProto stack. Nothing touches the public ATProto — writes go to a local PDS, the local Jetstream reads that PDS's firehose, and each test stands up its own in-process Contrail ingester + XRPC handler to consume it.

What's inside#

Service	Port	Purpose
PDS	4000	Personal Data Server (user repos)
PLC	2582	DID registry
Jetstream	6008	Firehose relay in JSON
TAP	2480	Sync/backfill relay
PostgreSQL	5433	Shared by PLC + Contrail
Maildev	1080	PDS email verification catcher

Prerequisites#

Clone atproto-devnet as a sibling of this contrail repo:

some-workspace/
├── contrail/            (this repo)
└── atproto-devnet/

git clone https://github.com/OpenMeet-Team/atproto-devnet.git /path/to/atproto-devnet

Running the tests#

# From the monorepo root (one-time build of @atmo-dev/contrail)
pnpm install && pnpm build

# Bring the devnet stack up (creates .env from .env.example on first run)
cd apps/contrail-e2e
pnpm stack:up

# Run the suite
pnpm test:e2e          # once
pnpm test:e2e:watch    # re-run on change

Note: up and down are reserved by pnpm (aliases for update), so the stack scripts are prefixed stack: to disambiguate. The test scripts are named test:e2e so the monorepo-wide pnpm test skips them in CI (they need the live docker stack).

Tests#

tests/health.test.ts — service health checks (PLC, PDS, TAP, Jetstream)
tests/ingest-roundtrip.test.ts — publish → index roundtrip. Creates a fresh PDS account, publishes a calendar event and an RSVP, and verifies both the record and its rsvpsGoingCount via an in-process XRPC handler.
tests/cursor-resume.test.ts — regression for runPersistent's durable cursor. Starts the ingester, publishes A, stops the ingester, publishes B + updates B + deletes A, restarts, and verifies the saved cursor replays the gap.

Each test spins up its own runPersistent in-process against an isolated postgres schema, so tests don't interfere with each other or with any dogfooding ingester running in another terminal.

Teardown#

pnpm stack:down    # stops containers AND wipes volumes for a clean slate

Namespace#

These tests use rsvp.atmo as the Contrail namespace — same as atmo-events, so the fixtures are compatible with that frontend. If you're running your own namespace, edit config.ts.

Why not use `apps/postgres/`?#

apps/postgres/ connects Contrail to the public Bluesky Jetstream — useful for indexing real events, unusable for writing test fixtures. This suite gives a sealed environment where the tests control every record.

Overrides#

Copy .env.example to .env and edit. All ports, database credentials, and devnet hostnames are overridable.