Sign in Start testing
Softsurance/Database testingRoadmap

Read the schema. Leave the data.

Connect PostgreSQL with least-privilege, read-only credentials. Softsurance inspects schema and runs bounded integrity checks — production access is optional and never the default.

Start testing Read the docs

At a glance

EnginePostgreSQL first
DefaultRead-only role
QueriesBounded, templated
StatusRoadmap

Read-only by default, bounded by statement limits, and built on the same evidence record as every other test.

Schema · read-only roleapp_db / staging
customers
iduuid pk
emailtext unique
created_attimestamptz
orders
iduuid pk
customer_idfk →
totalnumeric
statustext
order_items
iduuid pk
order_idfk →
qtyint
  • PASSorders.customer_id references customers.idmeta
  • PASSorder_items.order_id is NOT NULLmeta
  • FAILorders.status lacks expected CHECK constraintexpect
  • PASSOrphaned order_items: 0 · limit 10,000 rows1.4s

01 / Capabilities

What it checks8 items

What it checks.

Everything a run checks, and the evidence it keeps when something fails.

  • Connectivity checkRoadmap
  • Schema and table discoveryRoadmap
  • Column and type inspectionRoadmap
  • Foreign key and relationship checksRoadmap
  • Constraint expectationsRoadmap
  • Read-only validation queriesRoadmap
  • Expected vs observed schema diffRoadmap
  • Isolated test-database integration checksRoadmap

02 / How it works

Step by step5 steps

  1. Create a read-only role

    We provide the SQL to create a least-privilege role limited to the schemas you choose.

  2. Connect

    Credentials are encrypted. The connection is verified and the permitted tables and columns are listed.

  3. Declare expectations

    Required tables, columns, types, keys and constraints — or accept proposals derived from the current schema.

  4. Run checks

    Metadata checks and templated read-only queries run with statement timeouts and row limits.

  5. Track drift

    Scheduled runs show when the schema stops matching what you expect.

03 / Guardrails

Enforced by the backendNot optional

The limits come first.

These rules are enforced by the execution backend. The interface can’t switch them off, and neither can an AI.

G-01

Read-only by default

Production access is optional and uses a read-only role. Write access is only for a separate test database.

G-02

No AI-written SQL on production

Models never generate and execute unrestricted SQL. Checks come from fixed templates.

G-03

Statement limits

Timeouts, row limits, connection limits and statement-type restrictions on every query.

G-04

Minimal exposure

Row contents aren’t sent to an AI provider, and production data is never copied into test environments.

04 / Questions

Database testing3 entries
Q.01Do you need production access?

No. Staging or a schema-only replica works. Production is an explicit, optional choice.

Q.02Can tests modify data?

Only against a separate test database with restricted privileges and explicit cleanup steps.

Q.03When is it available?

It follows API testing.

Start

Your first runStaging URL required

Add a staging URL. Read your first real result today.

Start testing Read the docs