breeze-testing

Codify test-writing conventions and coverage requirements for Breeze RMM projects.

73|23|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/LanternOps/breeze --skill breeze-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breeze-testing
Source: https://github.com/LanternOps/breeze/tree/main/.claude/skills/breeze-testing
Command: npx skills add https://github.com/LanternOps/breeze --skill breeze-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing guidelines for Breeze RMM tests — API route (Vitest + Drizzle mocks), Go agent, shared validators, and the required coverage checklist for every new feature. Use when writing or modifying tests in this repo.

Core Features & Use Cases

  • API route tests with Vitest and Drizzle mocks
  • Go agent tests
  • Shared validators
  • Coverage contract for every new feature

Quick Start

Follow these Breeze testing guidelines when writing or modifying tests to ensure API route tests, Go agent tests, and validators meet the coverage contract.

Frequently Asked Questions about breeze-testing

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

FAQPage Schema
How do I mock Drizzle database queries in Vitest for API route tests?

To mock Drizzle database queries in Vitest, you must follow codified conventions that standardize API route tests, ensuring multi-tenant isolation checks and consistent query mocking patterns across the Breeze RMM codebase.

What should test coverage include for Breeze RMM API routes?

Test coverage for Breeze RMM API routes must follow a defined coverage contract covering the happy path, authentication, validation, and edge cases to ensure comprehensive quality checks for every new feature.

Can I use this to standardize Go agent tests alongside Vitest?

Yes, you can standardize Go agent tests alongside Vitest API tests. It codifies testing practices for both Go agent tests and shared validators within the Breeze RMM projects.

Why do I need multi-tenant isolation checks in my API route tests?

Multi-tenant isolation checks are required in API route tests to enforce testing conventions that prevent data leakage across tenants, ensuring the Breeze RMM multi-tenant architecture remains secure during validation.

Does this coverage contract apply to shared validators across the codebase?

Yes, the coverage contract applies to shared validators across the codebase. It enforces testing guidelines for shared validators alongside API route and Go agent tests to meet coverage requirements.