1. Habit
  2. Skills
  3. Testing skill
tursodatabase · 1K installs

Testing skill
Runs by itself, nightly test conversion.

Legacy TCL tests move to sqltest.

Install the Testing skill and make it a habit: follow https://gethabit.dev/skills/tursodatabase/testing.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

1K installs25K starsMIT licenceSource on GitHub ↗

Testing

by tursodatabase · 1K installs

The skill

The testing skill from the Turso repo tells agents which test type to use, how to run them and how to write .sqltest, TCL and Rust integration tests, including converting TCL tests to .sqltest.

Only when you ask.

The habit

Legacy TCL tests move to sqltest.

↻ Runs by itselfnightly test conversion

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

nightly test conversion. Runs in Claude Code routine or cron.

  • ↻ nightly test conversion
  • 0 3 * * *

02

It checks its work

converted tests pass. If a check fails, it tries again.

  • ✓make -C sqlite/conformance run-rust passes for the new files
  • ✓SQL statements match the original TCL tests
  • ✓no converter warnings left unresolved
  • ✓converted test count is above zero

03

It remembers

conversion board. The next run reads it first: TCL files still to convert and files with open warnings.

loops/sqltest-conversion-loop/board.md

One run, step by step.
Then it stops.

Stop ruleStops after five TCL files per run.

  1. 01

    Pick TCL files

    Your agent takes the next legacy files from testing/ off the board.

  2. 02

    Run the converter

    It runs cargo run -- convert <TCL_test_path> -o <out_dir> from the test runner.

  3. 03

    Fix warnings by hand

    Where the converter warns, it writes the missing parts by hand, such as unrolled loops.

  4. 04

    Run the new tests

    It runs make -C sqlite/conformance run-rust on the converted files.

  5. 05

    Adjust expected output

    It updates expected results for the seeded database, never the SQL itself.

  6. 06

    Update the board

    It marks files converted or lists what still fails.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Testing skill helps.

Use it when

  • ✓ adding a test for a functional change
  • ✓ converting TCL tests to .sqltest
  • ✓ choosing between sqltest, Rust and fuzz tests

Skip it when

  • – you test an app built on Turso
  • – you work outside the Turso repo

Questions

Testing skill, answered.

Why move away from TCL tests?

TCL tests are being phased out, and .sqltest cases can run against several backends.

Why do expected results change?

TCL tests use hardcoded databases, while .sqltest generates the database with a different seed.

How do I install the Testing skill?

Copy the prompt at the top into your agent. It installs the skill from tursodatabase/turso and sets up the habit. Or run npx skills add tursodatabase/turso --skill testing.

Is the Testing skill free?

Yes. It is published under MIT. Habit is free too.

Testing. Now as a habit.

Install the Testing skill and make it a habit: follow https://gethabit.dev/skills/tursodatabase/testing.md

  • Free
  • No account
  • Undo in one line

All tursodatabase skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by tursodatabase, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.