Testing

This covers the testing workflow for a SQL database project that's migrating from TCL tests to a newer `.sqltest` format. You get specifics on when to use each test type (SQL compatibility tests, Rust integration tests, fuzz tests), how to run them with make commands or cargo, and concrete examples of the `.sqltest` syntax with its pipe-delimited output format. The conversion process is particularly detailed since you'll need to use a converter tool, manually fix warnings, then verify against generated databases with different seeds. The honest reality here is that test migration is messy work involving a lot of manual verification, but the guide at least tells you exactly which commands to run and where files should live.

skills.sh installs: 1.3K
GitHub stars: 25.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add tursodatabase/turso --skill testing --agent claude-code

Installs into .claude/skills of the current project.

Files

Testing Guide

Test Types & When to Use

Type	Location	Use Case
`.sqltest`	`sqlite/conformance/sqlite-sqltests/`	SQL compatibility. Preferred for new tests
`.sqltest`	`testing/shared-sqltests/`	SQL that both the SQLite and the PostgreSQL frontends run
TCL `.test`	`testing/`	Legacy SQL compat (being phased out)
Rust integration	`tests/integration/`	Regression tests, complex scenarios
Fuzz	`tests/fuzz/`	Complex features, edge case discovery

Note: TCL tests are being phased out in favor of the .sqltest suites in sqlite/conformance/. The .sqltest format allows the same test cases to run against multiple backends (CLI, Rust bindings, etc.).

Running Tests

# Main test suite (TCL compat, sqlite3 compat, Python wrappers)
make test

# Single TCL test
make test-single TEST=select.test

# SQL test runner
make -C sqlite/conformance run-cli

# OR
cargo run -p sqltest -- run <test-file or directory>

# Rust unit/integration tests (full workspace)
cargo test