SKAYBASETest ManagementConnect a database

A PRACTICAL START

Your database.
A clear setup.

One person prepares the database. The team joins with Google or email and works in the same shared projects.

Four steps to your own workspace.

One database owner completes setup. Teammates then join through an invitation.

01 / THE FOUNDATION

Prepare a Supabase project.

Create a project you control at Supabase, or use a compatible self-hosted Supabase installation. A dedicated project keeps testing separate from your production application.

  1. Open Connect your database. Enter the database owner’s email address in the setup section.
  2. Download or copy the generated setup SQL. Review it in your project’s SQL Editor before running it.
  3. Run it once. It creates tables prefixed stm_, row-level access policies and the functions used by the app. It grants project creation to the verified email you supplied.

The SQL is versioned and can be re-run. Back up a populated database before an upgrade. Do not turn off row-level security to resolve an access problem.

Public key, private access.

Use a publishable key, or the legacy anon key. Never paste a database password, service_role key or sb_secret_ key into this website. A public key identifies the project; verified accounts and database access policies control test data.

02 / SIGN-IN

Let the right people in.

Authentication belongs to your Supabase project. Existing Consult accounts do not automatically grant access to this separate workspace.

Redirect addresses

In Authentication → URL Configuration, use this Site URL:

https://testmanagement.skaybase.com

Add these exact Redirect URLs:

https://testmanagement.skaybase.com/auth/callback
https://testmanagement.skaybase.com/auth/callback?recovery=1

Email and password

Enable email sign-in and keep email confirmation enabled. Configure a custom SMTP provider before inviting ordinary users. Supabase’s default mail service is for testing and may only deliver to members of your Supabase organisation; it is not a production email service.

Configure sender identity, rate limits and email templates in your project. A 12-character minimum password is enforced for new accounts in this app; set the corresponding password policy in Supabase too. Keep sign-up protections and rate limits enabled.

Google sign-in

  1. In your own Google Cloud project, configure the OAuth consent screen and create a Web application OAuth client.
  2. Copy the callback URL shown by Supabase’s Google provider settings. It is normally https://YOUR-PROJECT.supabase.co/auth/v1/callback. Register that exact address in Google’s authorised redirect URIs.
  3. Enter the OAuth client ID and secret in Supabase’s Google provider settings, and enable the provider. The secret stays there; never enter it into this app.
  4. Finish any Google publishing or verification required for your organisation, audience and scopes. In testing mode, only configured test users may be able to sign in.

Use Supabase’s official Google setup guide and SMTP guide for current provider steps.

03 / YOUR TEAM

Connect once. Then start working.

  1. In the Supabase project’s Connect dialog or API settings, copy the project URL and publishable key.
  2. Enter both on the connection page. The app checks the installed schema before continuing.
  3. Sign up or sign in as the verified owner email configured in the setup SQL. Create your first project.
  4. In Database & team, create an invitation for a colleague’s email and select Editor or Viewer. Copy the link and share it privately yourself.
  5. Your colleague opens the link, checks the database address and signs in with that verified email to accept. The link expires in seven days and works once.

Invited members do not need to run SQL. Only approved project creators can create new projects; invited editors and viewers work in the projects shared with them.

Add another project creator

The database administrator can run this in the Supabase SQL Editor, replacing the example email:

insert into stm_private.project_creators (email)
values (lower('owner@example.com'))
on conflict do nothing;

Changing an app role does not change access to your Supabase dashboard. Keep database administrator accounts separate and protected.

04 / THE WORK

From a case to a decision.

  1. Define. Create a project and write a case with preconditions, actions and observable expected results. Use folders, priorities and tags to keep it organised.
  2. Execute. Create a run and select cases across pages. Each run preserves a snapshot, so later case edits do not rewrite history.
  3. Record. Choose Passed, Failed, Blocked, Skipped or Untested. Add what actually happened; failures and blockers require notes. Link an HTTPS issue or evidence page when useful.
  4. Review. Check the report and any outstanding results. Once every case has an outcome, complete the run to make it read-only. Completed does not mean approved or passed.

This workspace supports decisions. It does not certify software, replace specialist review or guarantee regulatory compliance.

Stay in the library

Open a case to edit it above the existing list. Closing it keeps your filters and position. Use Ctrl+Enter (Cmd+Enter on Mac) to save a case or test outcome. Esc closes a dialog; if there are unsaved changes, you choose whether to keep editing or discard.

Version history shows previous saved definitions. Schema 2 records each case revision; upgrading an older database starts history from its current definitions, not from past edits that were never recorded. Run snapshots remain independent of later case revisions.

Know what has been saved.

Save case and Save outcome write to your database. A recovery copy is also captured while you edit, in this browser tab. It is clearly labelled as local and is not a confirmed database save. After a reload, review Restore draft before applying it.

If saving fails or times out, keep the editor open and download the draft. A lost response can mean the database committed but the acknowledgement did not arrive. Retrying an unchanged case or outcome is safe; a conflicting revision is rejected rather than overwritten. Compare your draft with the current saved record before merging changes.

Recovery copies are removed after a confirmed save, explicit discard, sign-out or disconnection. Closing the tab, clearing browser data, storage limits or device failure can remove or prevent a local copy. Keep an exported draft when you need an independent copy. Local recovery does not replace database backups.

Upgrade with a recovery plan

The database owner should take a supported backup and test its restoration in an isolated environment before running updated setup SQL. The SQL migration is transactional. Review errors before retrying; never disable access policies to force it through. Publishing a new app does not modify your database.

Bring the cases you already have.

Import Excel (.xlsx or .xls), CSV, or XML from the case library. Files are read locally in a browser worker. Only the cases you confirm are sent to your connected database.

  1. Choose a file, up to 5 MB and 10,000 cases. For Excel, select the worksheet and header row. For CSV, adjust delimiter and encoding if needed.
  2. Match each source column to a case field. Title is required; unmapped fields get the defaults shown in the preview.
  3. Review validation errors and examples. Correct your file or explicitly choose to skip invalid rows. Duplicate detection uses title and folder, ignoring letter case and surrounding spaces.
  4. Confirm the import. The database commits the accepted cases together; an error rolls back that batch. Retrying the same confirmed batch does not create it twice.

Download templates from the import screen. XML supports case records named testcase, test_case, case or row, including TestLink-style nested steps. External entities, DTDs, XLSX files with VBA payloads and oversized workbooks are rejected. Spreadsheet formulas and macros are never executed.

Review converted content: arbitrary vendor formats can organise steps differently. Large imports are paginated in the library; use search and folders to find cases.

What stays where.

Skaybase
Hosts the app’s HTML, scripts, styles and setup files. It does not receive your test-content API requests.
Your browser
Runs the workspace, reads import files and stores your chosen project URL, public key and authentication session. Sign out on shared devices. Temporary recovery drafts and sample workspace records use browser-tab storage. A short-lived in-memory cache avoids repeatedly fetching the same records.
Your Supabase project
Stores accounts, test cases, run snapshots, results, memberships, invitations and activity records. Its administrator controls region, backups, retention, account removal and provider terms.

The app uses authenticated requests over HTTPS and database-enforced access rules. It is not end-to-end encryption: your browser and database process readable test content. As with other web applications, you trust the code delivered by the hosting service.

Backups and leaving

Export cases and run reports as CSV from the app. For a complete recovery plan, back up your PostgreSQL database, include the authentication data and test restoring it in a separate environment. Use your provider’s supported backup process. Keep copies under your organisation’s control.

Disconnecting the app removes this browser’s connection and session; it does not erase database records. The database owner handles record deletion, user removal and retention according to the team’s requirements.

What is free?

The Skaybase application has no subscription or seat fee. Supabase, an SMTP provider or your own server may have usage limits and charges. Skaybase does not operate or bill your database.

When something needs attention.

“Schema missing” or access-policy check failed

Check the project URL, then run the current setup SQL in that same project. Do not substitute an administrator API key. Refresh Supabase’s API schema cache if your deployment needs it.

My project list is empty

Confirm that you are connected to the expected database and signed in with the correct account. Accept an invitation, or have the database administrator add your verified email to the project-creators list.

Google sign-in or email delivery does not work

Check the provider configuration, exact redirect URLs, Google audience/test-user restrictions and SMTP logs in your own project. Skaybase cannot read those settings.

Someone else changed the same case or result

The app refuses to overwrite a newer version. Copy any draft text you need, reload the latest record and apply your changes to that version.

The connection dropped while saving

Keep the form open and retry after reconnecting. Imports and new runs use retry identifiers. If a case or result save reports a version conflict after a lost connection, reload it and check whether the original save succeeded.

Where do I get help?

Use Skaybase contact. Include the action and error text, but do not send passwords, tokens, private test data or database keys.