Hacker News Reader

Comment by messe | Hacker News Reader

> 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.

View on HN

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

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.

This and this needs Jepsen testing.

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

Isn't that test suite private though?

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

Thanks for the clarification, I appreciate it.

> and the proprietary suite is 1055k CLOC.

Why is the code size of the proprietary test suite even public though?

You can buy access to it.

Any serious SQLite re-implementation should buy it and test against it.

The cost of TH3 is listed as "call".

It's much more likely the issue is one of cost, not of seriousity.

Given that the project and websites are entirely vibe-coded, I don't think they passed the call to get a quote.

Reply on news.ycombinator.com