Capture & Ingest
Records land in CEDX Test already linked to the canonical customer, employee, or vendor ID.
Test runs the estate's test operations: 360 cases in 64 suites across four layers, every flake scored and quarantined or healed, and coverage gaps tied to the incidents they predict.
"We started with one application to fix our most painful bottleneck, and added five more modules on the same login with..."
| Endpoint / Function / App | Bound Estate Resource | Owner & Deployment Env | Request Rate & Latency | Blast Radius & Quota | Build Status |
|---|---|---|---|---|---|
| POST /v2/quotes/approve-rampCEDX Test · Record #1040 | Quotes + Books + Sign Transaction | Core Commerce SDK · Prod | 1,420 req/m · 14ms p99 | ● Scoped Token · Tier-1 | Passing 100% |
| fn_custom_rebate_accrual.tsCEDX Test · Record #1041 | Serverless Edge Function · Node 22 | Finance Eng · Sandbox->Prod | 840 exec/m · 9ms cold | ● Read/Write: Books Subledger | Deterministic |
| Internal Field RMA Builder AppCEDX Test · Record #1042 | CEDX Builder Low-Code Surface | Ops Systems Team · 68 Users | Zero Maintenance Debt | ● Inherits Corporate SSO | Live v2.4 |
| CI/CD Canary Pipeline #8841CEDX Test · Record #1043 | Automated Flake-Scored Test Suite | Release Engineering | 412 Specs · 0 Flakes | ● Auto-Rollback Armed | Deployed 4m ago |
The top flake on the board fails 38% of its 12 attempts, holds inventory during a checkout race, and is not quarantined. The tool's first scored action is to quarantine it. That is what a test console is for.
Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.
64 suites split 26 unit, 16 integration, 15 E2E and 7 contract, each with cases, pass %, p95, flakes and an owner. pricing/edge runs 44 cases at 100% with a 4.1-second p95; billing/invoice-calc carries 54 at 98% with one flake. The layer chips cut the table to the stack you own.
360 cases with status, duration, retries and a flake score. POS offline queue flushes after reconnect tops the board at 94: quarantined, 1m 28s, 3 retries. rolls back if POS queue wears a healed chip. 156 cases are assistant-authored, marked AI on the row.
320 runs with branch, status, pass %, failures and duration. run_4821 on main failed 12 cases at 91% pass; run_4818 on feat/checkout-hold passed 97 with zero failures in 15m 20s. The cancelled run shows 0 and 0, recorded, not erased.
Every figure below is directly inspectable in the running CEDX Test application workspace with zero synthetic projections.
Click any screen below to inspect how CEDX Test moves from initial intake to verified cross-estate completion.
Pass rate 92%, 50 open flakes, 21 modules at high gap risk, 66% coverage, and alerts that connect the dots: payments-core sits at gap risk 88 with 4 recent incidents, and the main branch run failed 12 cases, 8 of them flaky. The do-this-next queue's first action is to quarantine the checkout race.
Every custom app in Builder, every Function, and every webhook runs inside the same identity, audit log, and transactional boundary as native CEDX apps.
Records land in CEDX Test already linked to the canonical customer, employee, or vendor ID.
Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.
Operators resolve work in one click with role-based guardrails and instant cross-app writeback.
Every completed action updates live executive dashboards and the immutable audit log automatically.
Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.
Owns the flake board: 50 open flakes, one quarantine decision at a time, and a pass rate that means something because the flakes are out of it.
Write and review the cases, including the 156 assistant-authored ones, which arrive marked AI and get read like any other contribution.
Watch runs by branch before a release cut: release/2026.8 at 88% with 22 failures is a conversation, not a merge.
CEDX Test is not an isolated point tool. It reads and writes the exact same customer, ledger, and identity records as the rest of the CEDX software estate.
Deploy's required checks are these suites. 13 deploys currently sit blocked behind failing ones, and both products say so.
E2E suites run against cloned environments. A failed seed apply explains a red suite before the code does.
Contract suites pin the routes and functions the runtime serves: api/routes-contract runs 48 cases at 97%.
Apps assembled in Builder inherit the same gates: publish risk and test health are two views of one question.
"We started with one application to fix our most painful bottleneck, and added five more modules on the same login without a single migration project."
"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."
"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."
Drag the seat slider to compare your current stitched stack (Retool Enterprise + Kong API Gateway + AWS Lambda + Postman + LaunchDarkly) against running CEDX Test natively on the unified CEDX estate.
Explore the live CEDX Test workspace on canonical demo data at /app/test, or book a 30-minute architecture session to map your first entity rollout.
Instant browser access to CEDX Test pre-loaded with canonical demo records and connected across the 132-application CEDX estate.