jazz-testing
Jazz Testing
When to Use This Skill
- Writing unit or integration tests for apps using Jazz
- Simulating synchronisation for testing purposes
- Verifying permissions and security logic
- Testing UI components in various application states (Guest/Anonymous/Authenticated/Online/Offline)
- Debugging failing tests
Do NOT Use This Skill For
- Designing the initial data schema (use
jazz-schema-design - General React/Svelte UI layout questions unrelated to Jazz (for questions on Jazz integration with React/Svelte, use the
jazz-ui-developmentskill)
Key Heuristic for Agents
If you are about to suggest "mocking" any part of the data layer in the user's application, STOP and invoke this skill instead. This skill enforces the use of the official in-memory test sync node.
Core Concepts
More from garden-co/classic-jazz
spec
Implement features using Spec Driven Development (SDD) workflow. Creates design and task documents with approval gates.
1benchmarking
Use this skill when writing or running performance benchmarks for Jazz packages. Covers cronometro setup, file conventions, gotchas with worker threads, and how to compare implementations.
1jazz-schema-design
Design and implement collaborative data schemas using the Jazz framework. Use this skill when building or working with Jazz apps to define data structures using CoValues. This skill focuses exclusively on schema definition and data modeling logic.
1jazz-ui-development
Use this skill when building, debugging, or optimizing Jazz applications. It covers Jazz's bindings with various different UI frameworks, as well as how to use Jazz without a framework. Look here for details on providers and context, hooks and reactive data fetching, authentication, and specialized UI components for media and inspection.
1jazz-permissions-security
Use this skill when designing data schemas, implementing sharing workflows, or auditing access control in Jazz applications. It covers the hierarchy of Groups, Accounts, and CoValues, ensuring data is private by default and shared securely through cascading permissions and invitations.
1