jazz-testing

Set up in-memory Jazz test sync for unit and integration tests.

154|13|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/garden-co/jazz --skill jazz-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jazz-testing
Source: https://github.com/garden-co/jazz/tree/main/.cursor/skills/jazz-testing
Command: npx skills add https://github.com/garden-co/jazz --skill jazz-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Jazz testing can be hard due to multi-user synchronization, flaky mocks, and brittle test harness setups. This skill provides a safe, in-memory testing environment that simulates real Jazz synchronization and account contexts.

Core Features & Use Cases

  • In-memory test sync setup to model multi-user interactions without mocking.
  • Framework-agnostic test harness with access to account contexts and permissions.
  • Guidance and reusable patterns for unit/integration tests of Jazz apps.

Quick Start

Initialize the in-memory Jazz test sync and create test accounts to begin writing unit or integration tests.

Frequently Asked Questions about jazz-testing

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

FAQPage Schema
How do I test multi-user synchronization in Jazz apps without flaky mocks?▼

You can test multi-user synchronization in Jazz apps by using an in-memory environment that safely mimics real sync. This framework-agnostic test harness orchestrates account contexts and permissions, eliminating brittle mocks.

How do I set up a unit testing harness for Jazz workflows?▼

Set up a Jazz testing harness by initializing the in-memory test sync and creating test accounts. This provides a safe environment with access to account contexts for reliable unit and integration testing.

Does Jazz testing support permission and security validation across multiple users?▼

Yes, Jazz testing supports permission and security validation by providing a test harness with access to account contexts. You can simulate multi-user scenarios to validate security rules within your Jazz workflows.

What is the best way to write integration tests for Jazz applications?▼

The best way to write integration tests for Jazz applications is using an in-memory testing environment that simulates real synchronization. This approach provides reusable patterns and a test harness to orchestrate accounts and sync nodes.

Why are my Jazz test harness setups becoming brittle?▼

Jazz test harness setups become brittle due to flaky mocks and the complexity of multi-user synchronization. Using an in-memory test environment that mimics real sync provides a reliable alternative for orchestrating test accounts.