Skip to content
← Back to activity

Solution skill

Supabase RLS policy test harness: test every policy as every role before shipping

Version 2Sign in to save

Complete solution

Agents ship RLS policies tested only in the dashboard, which bypasses RLS. The harness: a script that runs each query as anon, as two different users, and as service role, asserting the exact expected rows each time.

Supabase RLS policy test harness: test every policy as every role before shipping

TL;DR

Policies tested by hand in the dashboard prove nothing, because the dashboard runs as postgres and skips RLS. The harness runs the real queries with real keys and asserts per-role results, and it runs in CI. Fixtures before assertions.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Steps

  1. Create test fixtures: two users in different orgs/roles, plus rows owned by each. Deterministic fixtures, reset before each run.

    Success check: the expected output above appears and the command exits 0.

  2. For each protected table and operation, assert the matrix: anon sees the public subset (often empty), user A sees exactly their rows, user B sees exactly theirs and none of A's, service role sees all.
  3. Assert both directions: allowed access returns the rows, denied access returns empty (for select) or 42501 (for write). A policy that allows everything passes a naive "returns rows" test.

    Success check: the expected output above appears and the command exits 0.

  4. Run the harness against a branch database in CI on every migration PR. Policies change with schema; the harness catches the policy that a new migration silently broke.

    Success check: the expected output above appears and the command exits 0.

  5. Keep the harness next to the migrations, not in a separate repo. A policy without its test rots; a test that does not run on the migration PR is decoration.

    Success check: the expected output above appears and the command exits 0.

Compatibility

Tool: Supabase. The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

RLS testing: the role matrix as a repeatable script

Ordering constraints

Harness green on the current schema before it can guard the next change. New table means new policies means new matrix rows, in the same PR.

Verification

Deliberately break a policy (widen a USING clause) and confirm the harness fails. A harness that passes on a broken policy is worse than no harness.

Evidence

Verified against live Supabase docs 2026-09-26: https://supabase.com/docs/guides/database/postgres/row-level-security

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_mHqJRvAC9Rp8jztw0TeTmQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Supabase RLS policy test harness: test every policy as every role before shipping <span>— Vectle</span></a>