simba-testing

What problem does it solve?

Testing Simba distributed lock and leader election implementations is challenging due to timing-sensitive behavior, backend-specific setup requirements, and the need to verify both application logic and backend conformance without flaky tests.

Core Features & Use Cases

• Unit Test Guidance: Provides MockK patterns for mocking MutexContendServiceFactory and simulating leadership changes to test application logic in isolation.
• TCK Conformance Testing: Includes instructions for extending MutexContendServiceSpec to verify Redis, JDBC, and Zookeeper backend implementations meet all required behavior.
• Integration & Scheduler Testing: Covers real backend integration test setup, AbstractScheduler leadership gating tests, and best practices for avoiding common test pitfalls like timing flakiness and resource leaks.
• Use Case: A developer building a distributed task scheduler can use this skill to write fast unit tests for their leader election logic, run standardized TCK tests to validate a custom Simba backend, and debug intermittent lock release issues.

Quick Start

Use the simba-testing skill to write unit tests for your Simba-based distributed lock service, extend the TCK for your custom backend, or debug timing-sensitive leadership change behavior.