jepsen-test

Execute Jepsen-style cluster tests to validate gossip-rs correctness under network partitions.

1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/ahrav/Gossip-rs --skill jepsen-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jepsen-test
Source: https://github.com/ahrav/Gossip-rs/tree/main/.claude/skills/jepsen-test
Command: npx skills add https://github.com/ahrav/Gossip-rs --skill jepsen-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill validates the correctness and robustness of the deployed gossip-rs system under real-world network conditions, complementing in-process deterministic testing.

Core Features & Use Cases

  • Cluster Testing: Run Jepsen-style tests to ensure system reliability.
  • Two Modes: Supports lightweight Maelstrom tests for development and heavyweight full Jepsen tests for pre-release validation.
  • Use Case: After implementing a new gossip protocol, use Maelstrom to quickly verify convergence under simulated network partitions, then switch to full Jepsen before release to test the deployed system with real network failures.

Quick Start

Run the jepsen-test skill using Maelstrom to test the broadcast workload with 5 nodes and a partition nemesis.

Frequently Asked Questions about jepsen-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate distributed system correctness under network partitions?

Lightweight Maelstrom tests validate protocol logic during development by simulating network partitions, while full Jepsen tests verify the deployed system end-to-end under real network failure scenarios before release.

What workloads can I test with Jepsen and Maelstrom for a gossip protocol?

Jepsen and Maelstrom testing for gossip protocols support broadcast, counter, unique IDs, and Kafka-style log workloads to validate cluster convergence, consistency, and fault tolerance under network partitions.

Do I need Docker or Vagrant to run Jepsen cluster tests?

You need Docker or Vagrant to run heavyweight full Jepsen tests for end-to-end system verification against real network failures, whereas lightweight Maelstrom protocol validation does not require them.

How do I test a gossip protocol for convergence under simulated network failures?

Test gossip protocol convergence by executing Maelstrom tests with a partition nemesis across multiple nodes, simulating network failures to quickly verify protocol behavior before escalating to full Jepsen validation.

When should I use Maelstrom testing versus full Jepsen testing?

Use Maelstrom testing for lightweight protocol validation during development after implementing changes, and switch to full Jepsen testing for pre-release validation of the deployed system against real network partition and failure scenarios.