MCPInstall

hybrid-cloud-test-gen

Generate hybrid cloud tests for the Sentry codebase. Use when asked to "generate HC test", "create hybrid cloud test", "write HC test", "add HC test", "write RPC test", "test RPC service", "silo test", "cross-silo test", "outbox test", "API gateway test", or "endpoint silo test". Covers RPC service tests, API gateway tests, outbox pattern tests, and API endpoint tests with silo decorators.

Installs
69
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/getsentry/sentry --skill hybrid-cloud-test-gen
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads hybrid-cloud-test-gen automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Hybrid Cloud Test Generation

This skill generates tests for Sentry's hybrid cloud architecture. It covers RPC services, API gateway proxying, outbox patterns, and endpoint silo decorators.

Critical Constraints

ALWAYS use factory methods (self.create_user(), self.create_organization()) — never Model.objects.create().

NEVER wrap factory method calls in assume_test_silo_mode or assume_test_silo_mode_of. Factories are silo-aware and handle silo mode internally. Only use silo mode context managers for direct ORM queries (Model.objects.get/filter/count/exists/delete).

ALWAYS use pytest-style assertions (assert x == y) — never self.assertEqual().

ALWAYS add tests to existing test files rather than creating new ones, unless no file exists for that module.

For cross-silo ORM access: use assume_test_silo_mode_of(Model) when accessing a single model (auto-detects silo). Use assume_test_silo_mode(SiloMode.X) when the block covers multiple models or non-model operations.

Use TestCase for most tests, including those using outbox_runner(). Only use TransactionTestCase when tests need real committed transactions (threading, concurrency, multi-process scenarios).

NEVER use from __future__ import annotations in test files that deal with RPC models.

Step 1: Identify Test Category

Determine which category of HC test to generate based on the user's request:

SignalCategoryGo To
RPC service, service method, serialization round-trip, dispatchRPC Service TestsStep 3
API gateway, proxy, middleware, forwardingAPI Gateway TestsStep 4
Outbox, cross-silo message, ControlOutbox, CellOutbox, outbox drainOutbox Pattern TestsStep 5
API endpoint with silo decorator, endpoint test, permission checkEndpoint Silo TestsStep 6

If the signal is ambiguous, ask the user to clarify which category.

Step 2: Gather Context

Before generating any test:

  1. Read the source module being tested. Determine its silo mode by checking for @cell_silo_endpoint, @control_silo_endpoint, local_mode = SiloMode.X, or @cell_silo_model/@control_silo_model decorators.

  2. Find the existing test file using the mirror path convention:

    • src/sentry/foo/bar.py → tests/sentry/foo/test_bar.py
    • src/sentry/foo/services/bar/service.py → tests/sentry/foo/services/test_bar.py
    • src/sentry/foo/services/bar/impl.py → tests/sentry/foo/services/test_bar.py
  3. Read the existing test file to understand what's already tested, what base classes are used, and what patterns are established.

  4. Read source method signatures to understand parameters, return types, and which RPC models are involved.

Step 3: Generate RPC Service Tests

Load references/rpc-service-tests.md for complete templates and patterns.

RPC service tests must cover:

  • Silo compatibility: @all_silo_test ensures the service works across all silo modes
  • Serialization round-trip: dispatch_to_local_service verifies args/return survive serialization
  • Field accuracy: Field-by-field comparison of RPC model against ORM object
  • Error handling: Not-found returns, disabled methods, remote exception wrapping
  • Cross-silo effects: outbox_runner() + assume_test_silo_mode for propagation checks

Quick Reference — Decorator & Base Class

ScenarioDecoratorBase Class
Standard RPC service@all_silo_testTestCase
RPC with named cells@all_silo_test(cells=create_test_cells("us"))TestCase
RPC with member mapping assertions@all_silo_testTestCase, HybridCloudTestMixin

Step 4: Generate API Gateway Tests

Load references/api-gateway-tests.md for complete templates and patterns.

API gateway tests verify that requests to control-silo endpoints are correctly proxied to the appropriate cell. They must cover:

  • Proxy pass-through: Requests forwarded with correct params, headers, body
  • Query parameter forwarding: Multi-value params preserved
  • Error proxying: Upstream errors forwarded correctly
  • Streaming responses: close_streaming_response() for reading proxied response body

Quick Reference — Decorator & Base Class

ScenarioDecoratorBase Class
Standard gateway test@control_silo_test(cells=[ApiGatewayTestCase.CELL], include_monolith_run=True)ApiGatewayTestCase

Step 5: Generate Outbox Pattern Tests

Load references/outbox-tests.md for complete templates and patterns.

Outbox tests verify that cross-silo messages are created, drained, and produce the expected side effects. They must cover:

  • Outbox creation: Verify correct outbox records with outbox_context(flush=False)
  • Outbox processing: outbox_runner() drains pending messages
  • Cross-silo side effects: assume_test_silo_mode_of(Model) to check replica/mapping state
  • Idempotency: Draining the same shard twice produces no duplicates

Quick Reference — Decorator & Base Class

ScenarioDecoratorBase Class
Control outbox test@control_silo_testTestCase
Cell outbox test@cell_silo_testTestCase
Outbox with threading/concurrency(none)TransactionTestCase

Step 6: Generate Endpoint Silo Tests

Load references/endpoint-silo-tests.md for complete templates and patterns.

Endpoint silo tests verify that API endpoints work correctly under their declared silo mode. They must cover:

  • Correct silo decorator: Match endpoint → test decorator
  • Cross-silo data setup: Create data using factory methods (no silo wrapper needed)
  • Permission checks: Verify 401/403 for unauthorized access
  • Response accuracy: Verify response body matches expected data

Quick Reference — Decorator Mapping

Endpoint DecoratorTest Decorator
@cell_silo_endpoint @cell_silo_test
@control_silo_endpoint@control_silo_test
@control_silo_endpoint (with proxy)@control_silo_test(cells=create_test_cells("us"))
No decorator (monolith-only)@no_silo_test

Step 7: Validate

Before presenting the generated test, verify against this checklist:

  • Correct silo decorator on test class
  • assume_test_silo_mode_of(Model) for single-model ORM access; assume_test_silo_mode(SiloMode.X) for multi-model/non-model ORM blocks
  • Factory methods (self.create_*) are NEVER wrapped in assume_test_silo_mode
  • Factory methods used — never Model.objects.create()
  • pytest-style assertions only (assert x == y)
  • Correct base class (TestCase for most tests; TransactionTestCase only for threading/concurrency)
  • Imports are correct and minimal
  • Test file at correct mirror path
  • Test methods have descriptive names (test_<action>_<scenario>)
  • Run command: pytest -svv --reuse-db tests/sentry/path/to/test_file.py

Key Imports Quick Reference

# Silo decorators
from sentry.testutils.silo import (
    all_silo_test,
    control_silo_test,
    cell_silo_test,
    no_silo_test,
    assume_test_silo_mode,
    assume_test_silo_mode_of,
    create_test_cells,
)

# Base classes
from sentry.testutils.cases import TestCase, TransactionTestCase, APITestCase

# Cross-silo utilities
from sentry.testutils.outbox import outbox_runner
from sentry.testutils.hybrid_cloud import HybridCloudTestMixin
from sentry.silo.base import SiloMode

# RPC testing
from sentry.hybridcloud.rpc.service import dispatch_to_local_service

# API gateway testing
from sentry.testutils.helpers.apigateway import ApiGatewayTestCase, verify_request_params

# Outbox models
from sentry.hybridcloud.models.outbox import ControlOutbox, CellOutbox, outbox_context
from sentry.hybridcloud.outbox.category import OutboxCategory, OutboxScope

Context Manager Quick Reference

# Use ONLY for direct ORM queries — never for factory calls
assume_test_silo_mode(SiloMode.CONTROL)     # Switch to control silo for ORM access
assume_test_silo_mode(SiloMode.CELL)        # Switch to cell silo for ORM access
assume_test_silo_mode_of(ModelClass)        # Switch to silo matching model's silo mode

outbox_runner()                             # Drain all pending outboxes on exit
outbox_context(flush=False)                 # Create outboxes without flushing
override_cells(cells)                       # Override active cell config
override_settings(SILO_MODE=SiloMode.X)     # Override Django settings
override_options({"key": value})            # Override Sentry options

FAQ

What does the hybrid-cloud-test-gen skill do?

Generate hybrid cloud tests for the Sentry codebase. Use when asked to "generate HC test", "create hybrid cloud test", "write HC test", "add HC test", "write RPC test", "test RPC service", "silo test", "cross-silo test", "outbox test", "API gateway test", or "endpoint silo test". Covers RPC service tests, API gateway tests, outbox pattern tests, and API endpoint tests with silo decorators.

How do I install hybrid-cloud-test-gen?

Run npx skills add https://github.com/getsentry/sentry --skill hybrid-cloud-test-gen in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/hybrid-cloud-test-gen/ (personal) or .claude/skills/hybrid-cloud-test-gen/ (project).

Which AI agents can use hybrid-cloud-test-gen?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is hybrid-cloud-test-gen safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains hybrid-cloud-test-gen?

It is published by getsentry in getsentry/sentry, and it is an official skill from the maker of the technology it covers. It has 69 recorded installs.

More from getsentry/sentry

View all →

design-system

getsentry/sentry

Guide for using Sentry's layout and text primitives. Use when implementing UI components, layouts, or typography. Enforces use of core components over styled components.

OfficialFrontend & Design111 installs

sentry-security

getsentry/sentry

Sentry-specific security review based on real vulnerability history. Use when reviewing Sentry endpoints, serializers, or views for security issues. Trigger keywords: "sentry security review", "check for IDOR", "access control review", "org scoping", "cross-org", "security audit endpoint".

OfficialSecurity100 installs

sentry-javascript-bugs

getsentry/sentry

Review Sentry React and TypeScript changes for bug patterns drawn from real production issues. Use when reviewing a frontend diff or PR, checking Warden findings, auditing the current branch, reviewing production-error patterns, or looking for common regressions in static/.

OfficialDevOps & Cloud92 installs

generate-migration

getsentry/sentry

Generate or review Django database migrations for Sentry. Use when creating or reviewing migrations and data migrations, adding/removing columns or tables, adding indexes, or resolving migration conflicts.

OfficialCode Quality & Workflow90 installs

generate-frontend-forms

getsentry/sentry

Guide for creating forms using Sentry's new form system. Use when implementing forms, form fields, display-only form content, validation, or auto-save functionality.

OfficialFrontend & Design86 installs

sentry-backend-bugs

getsentry/sentry

Review Sentry Python and Django changes for bug patterns drawn from real production issues. Use when reviewing a backend diff or PR, checking Warden findings, auditing the current branch, reviewing production-error patterns, or looking for common regressions in src/ and tests/.

OfficialBackend & APIs84 installs

Popular testing & qa skills

View category →

tdd

mattpocock/skills

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Testing & QA1.2M installs

grilling

mattpocock/skills

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Testing & QA996.2K installs

migrate-to-shoehorn

mattpocock/skills

Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.

Testing & QA484.1K installs

run-train

lllllllama/rigorpilot-skills

Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.

Testing & QA337.8K installs

test-driven-development

obra/superpowers

Use when implementing any feature or bugfix, before writing implementation code

Testing & QA261.8K installs

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Testing & QA216.8K installs