Files
supabase__server/e2e/setup/token.ts
Katerina Skroumpelou 09a67506db test: add E2E tests for all four adapters against a local Supabase stack (#99)
* test: add E2E tests for all four adapters against a local Supabase stack

Adds an e2e vitest project (SDK-1143) covering what the mocked unit tests
cannot: real GoTrue-issued JWTs verified against the live JWKS endpoint,
real Supabase client operations via supabaseAdmin, resolveEnv() reading
process.env, and imports from dist/ so packaging regressions fail here.

One scenario set (auth + data access + isolation) runs over real HTTP
against minimal Hono, H3, Elysia, and NestJS apps. Elysia runs behind a
node:http server (srvx) so CI needs no Bun. A separate E2E workflow
starts the local stack with the Supabase CLI, builds, and runs the suite.

* test: grant explicit table privileges in the e2e notes migration

Newer Supabase stacks make new tables private by default — the API roles
(anon/authenticated/service_role) no longer receive DML grants on table
creation. CI installs the latest CLI, so all supabaseAdmin queries failed
with "permission denied for table notes" while JWT scenarios passed.
Reproduced locally on CLI 2.109.1; explicit grants fix it on both old and
new stacks.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* test: align NestJS missing-body handling and cover it in the scenarios

The NestJS app silently inserted an empty note when the body was missing,
while the other three adapters returned 400 — and no scenario exercised
those 400 branches. NestJS now throws BadRequestException like the rest,
and a shared missing-body scenario keeps all four aligned.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* test: cover forged JWTs, the RLS-scoped client, and optional-auth rejection

Closes the three gaps from PR review: the garbage-token scenario failed at
header decode without ever reaching signature verification, ctx.supabase
(the RLS-scoped client) was never exercised, and nothing pinned that a
present-but-invalid token on an optional route is rejected rather than
downgraded to anonymous.

- Mint a well-formed JWT with the live JWKS kid but a wrong signing key in
  global setup; every adapter must 401 it — proving signature verification
  end-to-end, not just structure checks.
- Add GET /my-notes reading through ctx.supabase with no WHERE clause,
  backed by a user_id = auth.uid() select policy — proving the caller's
  token reaches PostgREST and Postgres RLS scopes the rows.
- Assert GET /me-optional with an invalid token → 401.

10 → 14 scenarios per adapter (56 tests).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* test: add core-wrapper app, admin-bypass proof, and sign-in readability

Addresses PR review comments:

- New fifth app on the core withSupabase(config, handler) fetch wrapper —
  the exact programming model Supabase Edge Functions deploy — running the
  full scenario set behind node:http. A real Deno runtime e2e via
  `supabase functions serve` is tracked in SDK-1280.
- New GET /all-notes route (admin client, no filter) + scenario: user2's
  request sees user1's rows through supabaseAdmin, directly proving the
  admin client is not scoped to the caller's identity.
- Replace the `;({ data, error } = ...)` destructuring-reassignment in the
  sign-in helper with a plain result variable.

15 scenarios × 5 apps (75 tests).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-09 10:36:13 +03:00

56 lines
1.6 KiB
TypeScript

import { createClient } from '@supabase/supabase-js'
/** A signed-in test user with a real GoTrue-issued access token. */
export interface TestUser {
id: string
email: string
token: string
}
/**
* Signs in a test user against the local auth API and returns a real JWT.
* Creates the user on first run (email confirmations are disabled in
* e2e/supabase/config.toml, so signUp yields a session immediately).
*/
export async function signInTestUser(
email: string,
password: string,
): Promise<TestUser> {
const url = process.env.SUPABASE_URL
const anonKey =
process.env.SUPABASE_ANON_KEY ?? process.env.SUPABASE_PUBLISHABLE_KEY
if (!url || !anonKey) {
throw new Error(
'SUPABASE_URL / SUPABASE_ANON_KEY are not set — run `pnpm gen:env` first.',
)
}
const supabase = createClient(url, anonKey, {
auth: { persistSession: false },
})
let result = await supabase.auth.signInWithPassword({ email, password })
if (result.error) {
// First run: the user doesn't exist yet — create it, then sign in again.
const { error: signUpError } = await supabase.auth.signUp({
email,
password,
})
if (signUpError) {
throw new Error(
`could not create test user ${email}: ${signUpError.message}`,
)
}
result = await supabase.auth.signInWithPassword({ email, password })
}
const { data, error } = result
if (error || !data.session || !data.user) {
throw new Error(
`could not sign in test user ${email}: ${error?.message ?? 'no session returned'}`,
)
}
return { id: data.user.id, email, token: data.session.access_token }
}