https://baresql.com/tags/testing/ Recent content in Testing on BareSQL.com Hugo en-us Mon, 26 Oct 2026 00:00:00 +0000 https://baresql.com/how-baresql-audit-was-tested-against-planted-leaks-on-six-postgresql-versions/ Mon, 26 Oct 2026 00:00:00 +0000 https://baresql.com/how-baresql-audit-was-tested-against-planted-leaks-on-six-postgresql-versions/ <p>An access audit can be wrong in two directions. If it misses a route, a leak goes unnoticed because the report said all was well. If it invents one, people spend a day chasing access that was never there and stop trusting the report. So BareSQL Audit is tested against databases where every right answer is known in advance, and against the one judge that can’t be argued with, the PostgreSQL server itself.</p> https://baresql.com/how-baresql-portable-was-tested-on-four-real-database-engines/ Mon, 26 Oct 2026 00:00:00 +0000 https://baresql.com/how-baresql-portable-was-tested-on-four-real-database-engines/ <p>Every message <code>baresql lint</code> prints is a claim about four database engines. “GROUP_CONCAT() works on SQLite, MySQL and MariaDB; PostgreSQL refuses it.” Claims like that go stale, since engines add and drop functions between versions. Written from memory, a catalog of differences would be wrong in places on the day it shipped. So the answers BareSQL Portable quotes are the ones the engines gave when the catalog ran. A few messages also name the release in which an engine changed, such as SQLite 3.44 for <code>CONCAT()</code>, and those come from the engines&rsquo; release notes.</p>