sqlitecpp-testing-practices

A collection of GoogleTest patterns for testing SQLiteCpp, the C++ interface for SQLite databases. It describes test layout, in-memory databases, build registration, and test commands.

In plain words
What is it for?
Use it when adding or organizing SQLiteCpp tests, choosing between in-memory and file databases, registering tests with CMake or Meson, and running the test suite.
Why use it?
It makes SQLiteCpp tests follow a consistent structure and ensures new test files are included in the project's build systems.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/srombauts/sqlitecpp/sqlitecpp-testing-practices
Any agent
npx skills add SRombauts/SQLiteCpp --skill sqlitecpp-testing-practices
Clone the repo
git clone --depth 1 https://github.com/SRombauts/SQLiteCpp

Made for: Claude Code, Codex.

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 455 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.00455
Opus 5 $0.00010 $0.00228
Sonnet 5 $0.00004 $0.00091
Haiku 4.5 $0.00002 $0.00046

Measured yesterday against content hash ecf54099d33f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sqlitecpp-testing-practices scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/sqlitecpp-testing-practices/SKILL.md · 60 lines

What it actually says

SQLiteCpp Testing Practices

Scope

  • Uses GoogleTest (system if found, otherwise googletest/ fallback).
  • Test files live in tests/*_test.cpp (see tests/Database_test.cpp).
  • File headers use @ingroup tests.

Test File Structure

#include <gtest/gtest.h>
#include <SQLiteCpp/Database.h>

TEST(DatabaseTest, CanOpenReadWriteDatabase)
{
    // Arrange: setup test database
    SQLite::Database db(":memory:", SQLite::OPEN_READWRITE | SQLite::OPEN_CREATE);

    // Act: perform operation
    db.exec("CREATE TABLE test (id INTEGER PRIMARY KEY)");

    // Assert: verify behavior
    EXPECT_EQ(1, db.exec("INSERT INTO test DEFAULT VALUES"));
}

Adding a New Test File

  • Create tests/NewClass_test.cpp.
  • Register it in CMakeLists.txt under SQLITECPP_TESTS.
  • Register it in meson.build under sqlitecpp_test_srcs.

Common Patterns

  • Prefer :memory: databases when possible.
  • Use file-based databases when testing file I/O behavior (see tests/Database_test.cpp).
  • Use TEST() for independent tests; use TEST_F() only when a shared fixture is needed.

Running Tests

# CMake (from build dir)
ctest --output-on-failure
bin/SQLiteCpp_tests --gtest_filter=Database.*

# Meson
meson test -C builddir
meson test -C builddir --test-args="--gtest_filter=Database.*"

Canonical References

  • Test style: tests/Database_test.cpp
  • CMake test list: CMakeLists.txt (SQLITECPP_TESTS)
  • Meson test list: meson.build (sqlitecpp_test_srcs)

Cross-References

  • Workflow checklist: sqlitecpp-workflow
  • Build configuration: sqlitecpp-build-cmake, sqlitecpp-build-meson
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 60 lines · 21 tokens per session scan A ecf54099d33f

Subscribe to this mod's changes

sqlitecpp-testing-practices is a skill published in the GitHub repository SRombauts/SQLiteCpp (2,781 stars, last pushed 6d ago), licensed MIT. It adds 21 tokens to every session and 455 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens