← Back to context

Comment by messe

2 months ago

> TCL test harness. C SQLite's test suite is driven by ~90,000+ lines of TCL scripts deeply intertwined with the C API. These cannot be meaningfully ported. Instead, FrankenSQLite uses native Rust #[test] modules, proptest for property-based testing, a conformance harness comparing SQL output against C SQLite golden files, and asupersync's lab reactor for deterministic concurrency tests.

If you're not running against the SQLite test suite, then you haven't written a viable SQLite replacement.

9 comments

messe

Reply
manmal  2 months ago

I thought I read somewhere that their full test suite is not publicly available?

  • messe  2 months ago

    The TH3 test suite is proprietary, but the TCL test suite that they refer to is public domain.

    I'm not sure where they get their 90k CLOC count though, that seems like it might be an LLM induced hallucination given the rest of the project. The public domain TCL test suite is ~27k CLOC, and the proprietary suite is 1055k CLOC.

gigatexal  2 months ago

This and this needs Jepsen testing.

The value of SQLite is how robust it is and that’s because of the rigorous test suite.

littlestymaar  2 months ago

Isn't that test suite private though?

  • messe  2 months ago

    The TH3 test suite is proprietary, but the TCL test suite that they refer to is public domain.

    I'm not sure where they get their 90k CLOC count though, that seems like it might be an LLM induced hallucination given the rest of the project. The public domain TCL test suite is ~27k CLOC, and the proprietary suite is 1055k CLOC.