Agent skill

Testing

How to write and run tests in Celeriant. An agent skill from celeriant/celeriant-db.

Apache-2.0Auto-check passedTesting & QA

Install Testing

skills CLI

$ npx skills add celeriant/celeriant-db --skill testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install celeriant/celeriant-db testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/testing .claude/skills/testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "testing" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/testing into .claude/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/testing

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add celeriant/celeriant-db --skill testing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install celeriant/celeriant-db testing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/testing .agents/skills/testing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "testing" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/testing into .agents/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add celeriant/celeriant-db --skill testing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install celeriant/celeriant-db testing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/testing .cursor/skills/testing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "testing" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/testing into .cursor/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/celeriant/celeriant-db.git --path .claude/skills/testing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add celeriant/celeriant-db --skill testing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install celeriant/celeriant-db testing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/testing .gemini/skills/testing && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "testing" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/testing into .gemini/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install celeriant/celeriant-db testing

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add celeriant/celeriant-db --skill testing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/testing .github/skills/testing && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "testing" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/testing into .github/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add celeriant/celeriant-db --skill testing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install celeriant/celeriant-db testing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/testing .opencode/skills/testing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "testing" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/testing into .opencode/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: testing
GitHub stars: 114
Token cost: ~951 tokens
SKILL.md length: 246 words
Files: 1
Skills in repo: 13
Repo updated: Sep 28, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

How to write and run tests in Celeriant. An agent skill from celeriant/celeriant-db.

Works in 4 steps: Create… → Add pub mod my_test; to lib.rs → Add a TestEntry to registry.rs with… → …
Tasks that involve Integration testing
SKILL.md covers Unit Tests, Integration Tests and Benchmarks
Calls cargo

What it does

Testing is an agent skill from celeriant/celeriant-db. How to write and run tests in Celeriant. Unit tests with glommiotest! macro, integration tests via the test runner with category registry, Criterion benchmarks. Use when creating tests or benchmarks.

Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Integration testing and Unit testing. The repository describes itself as: Fast, distributed per-aggregate event log with strict ordering and optimistic concurrency control. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Integration testing
Tasks that involve Unit testing

Example prompts

“/testing”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Create celeriant_integration_tests/src/my_test.rs with pub async fn run() -> Result<(), Box>
Add pub mod my_test; to lib.rs
Add a TestEntry to registry.rs with name, description, estimated_secs, categories, and whether it requires distributed (MinIO + multi-node)
Add the dispatch arm in main.rs dispatch_test(): "my_test" => my_test::run().await

What it can do on your machine

Read from SKILL.md and the folder at commit d071a6d. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- cargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Testing loads about 951 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 246 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~52
When it runs · the whole SKILL.md, loaded when a task matches: ~951

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from celeriant/celeriant-db at commit d071a6d, republished under its Apache-2.0 licence (© celeriant). 246 words, ~951 tokens.

Download SKILL.mdSave it as .claude/skills/testing/SKILL.md (or your agent's skills folder).

name: testing
description: How to write and run tests in Celeriant. Unit tests with glommio_test! macro, integration tests via the test runner with category registry, Criterion benchmarks. Use when creating tests or benchmarks.

Testing

Unit Tests

Async code needs a Glommio executor. Use the glommio_test! macro defined locally in test modules:

rust

macro_rules! glommio_test {
    ($body:expr) => {
        LocalExecutorBuilder::new(Placement::Fixed(0))
            .spawn(|| async move { $body })
            .unwrap()
            .join()
            .unwrap()
    };
}

#[test]
fn my_async_test() {
    glommio_test!({
        let result = some_async_fn().await;
        assert!(result.is_ok());
    });
}

The macro is defined per test module (not crate-wide). See celeriant_shard/src/shard_wal_sync.rs, celeriant_rotating_log/src/log_segment_file.rs, celeriant_watch/src/tests.rs for examples.

Test philosophy: test observable behavior, not implementation details. Understand the design spec before writing tests. Extract common helpers (test_dir(), test_config(), make_aggregate_key()). Descriptive function names (write_with_empty_events_returns_error).

Integration Tests

Single binary with a test runner and category-based registry. Not separate binaries.

Each test is a module with pub async fn run() that spawns real server processes via TestServer, connects with CeleriantClient, and gets a fresh temp dir. The runner dispatches via --run-test <name> as subprocess, capturing output to /tmp/celeriant_test_<name>.log.

Build First

Integration tests spawn the Celeriant server as a subprocess. Build it before running tests:

bash

cargo build -p celeriant --release
cargo build -p celeriant_wal_inspect --release   # some tests (e.g. stale_lease_restart_split_brain) shell out to it

Running

bash

# Run all standalone tests
cargo run -p celeriant_integration_tests --release -- --standalone

# Run a specific test
cargo run -p celeriant_integration_tests --release -- --test single

# Filter by category (AND)
cargo run -p celeriant_integration_tests --release -- --include core,correctness

# Filter by category (OR)
cargo run -p celeriant_integration_tests --release -- --include-or edge,invariant

# List matching tests without running
cargo run -p celeriant_integration_tests --release -- --standalone --list

# List all categories
cargo run -p celeriant_integration_tests --release -- --list-categories

Adding a New Integration Test

Create celeriant_integration_tests/src/my_test.rs with pub async fn run() -> Result<(), Box<dyn std::error::Error>>
Add pub mod my_test; to lib.rs
Add a TestEntry to registry.rs with name, description, estimated_secs, categories, and whether it requires distributed (MinIO + multi-node)
Add the dispatch arm in main.rs dispatch_test(): "my_test" => my_test::run().await

Categories: Core, Replication, Election, Fencing, Invariant, Edge, Correctness, Durability, Performance, Operations, Security, Schema, Compaction, Debug.

Benchmarks

Criterion for statistical measurement, Glommio for async execution. Use iter_custom with manual timing since Criterion's iter() doesn't work with async. Fresh Glommio executor per iteration for clean state. black_box to prevent optimisation.

Existing benchmarks live under celeriant_shard/benches/ and celeriant_wire/benches/. Look at them for patterns including wave-based arrival and concurrent spawn_local.

Baseline workflow:

bash

cargo bench --package celeriant_shard --bench aggregate_count_benchmark -- --save-baseline my_baseline
critcmp --export my_baseline > ./celeriant_shard/benches/my_baseline.json
critcmp my_baseline > ./celeriant_shard/benches/my_baseline.txt

Files

Just SKILL.md in .claude/skills/testing of celeriant/celeriant-db.

Open the folder on GitHubat commit d071a6d

Compare with similar skills

Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Testing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Testing this skillceleriant/celeriant-db	114	—	~951	Automated safety check: Pass	Apache-2.0	9 days ago
JS-in-HTML Testingliaohch3/claude-tap	3.3k	—	~924	Automated safety check: Pass	MIT	15 days ago
Crosvm Testinggoogle/crosvm	1.3k	—	~847	Automated safety check: Pass	BSD-3-Clause	today
Add Acceptance Testtalkincode/toughradius	691	—	~827	Automated safety check: Pass	MIT	4 days ago
Testing Patternslangchain-ai/skills-benchmarks	118	—	~447	Automated safety check: Pass	MIT	16 days ago
Atmos Testscloudposse/atmos	1.4k	—	~1.9k	Automated safety check: Pass	Apache-2.0	today

Similar skills

JS-in-HTML Testing
liaohch3/claude-tap
Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.
3.3k GitHub stars~924 tokensUpdated 15 days ago
Testing & QAAuto-check passed
Crosvm Testing
google/crosvm
Official
Skill to assist with running tests and managing test VMs in the crosvm repository.
1.3k GitHub stars~847 tokensUpdated today
Testing & QAAuto-check passed
Add Acceptance Test
talkincode/toughradius
Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022).
691 GitHub stars~827 tokensUpdated 4 days ago
Testing & QAAuto-check passed
Testing Patterns
langchain-ai/skills-benchmarks
Official
Unit testing and integration testing best practices. An agent skill from langchain-ai/skills-benchmarks.
118 GitHub stars~447 tokensUpdated 16 days ago
Testing & QAAuto-check passed
Atmos Tests
cloudposse/atmos
Author Atmos smoke tests, post-deployment stack checks, and integration tests using type: test, HTTP assertions, shell or script/interpreter checks, require gates, parallel dependencies, matrix…
1.4k GitHub stars~1.9k tokensUpdated today
Testing & QAAuto-check passed
Memstack Development Test Writer
cwinvestments/memstack
A skill your agent uses when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with…
423 GitHub stars~3.7k tokensUpdated 11 days ago
Testing & QAAuto-check passed

Questions about Testing

What does Testing do?

How to write and run tests in Celeriant. An agent skill from celeriant/celeriant-db. Testing is an agent skill from celeriant/celeriant-db. How to write and run tests in Celeriant.

When should I use Testing?

Testing fits situations like: tasks that involve Integration testing; tasks that involve Unit testing.

How do I install Testing in Claude Code?

Run `npx skills add celeriant/celeriant-db --skill testing -a claude-code`. Or copy the skill folder (.claude/skills/testing in celeriant/celeriant-db) into .claude/skills/testing in your project. Claude Code loads it when a task matches its description.

How do I install Testing in Codex?

Run `npx skills add celeriant/celeriant-db --skill testing -a codex`. Or copy the skill folder (.claude/skills/testing in celeriant/celeriant-db) into .agents/skills/testing in your project. Codex loads it when a task matches its description.

Can I use Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add celeriant/celeriant-db --skill testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing, .gemini/skills/testing, .github/skills/testing and .opencode/skills/testing in your project.

What does Testing need to run?

Going by SKILL.md and its folder, Testing needs the command-line tools its instructions call (cargo).

Does Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Testing use?

Testing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Testing use?

About 951 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Testing?

Skills that share tags, products or a category with Testing: JS-in-HTML Testing (liaohch3/claude-tap, 3.3k stars), Crosvm Testing (google/crosvm, 1.3k stars), Add Acceptance Test (talkincode/toughradius, 691 stars) and Testing Patterns (langchain-ai/skills-benchmarks, 118 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing?

celeriant (a GitHub organization) maintains it in celeriant/celeriant-db, which has 114 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 28, 2026.

Source: celeriant/celeriant-db on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Testing

Install Testing

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Testing

Unit Tests

Integration Tests

Build First

Running

Adding a New Integration Test

Benchmarks

Files

Compare with similar skills

Similar skills

JS-in-HTML Testing

Crosvm Testing

Add Acceptance Test

Testing Patterns

Atmos Tests

Memstack Development Test Writer

More from celeriant/celeriant-db

Error Handling

Understanding Celeriant Structure

Extract A Type

Client Server Protocol

Database Architecture

Glommio Locking Patterns

Questions about Testing

Install Testing

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Testing

Unit Tests

Integration Tests

Build First

Running

Adding a New Integration Test

Benchmarks

Files

Compare with similar skills

Similar skills

More from celeriant/celeriant-db

Related

Questions about Testing