Stratégies de test Temporal Python

VérifiéSûr

Approches complètes pour tester les workflows Temporal avec pytest, time-skipping et mocking. Couvre les tests unitaires, d'intégration, de replay et la configuration locale.

Spar Skills Guide Bot
TestingIntermédiaire
4002/06/2026
Claude Code
#temporal#python#testing#workflows#pytest

Recommandé pour

Notre avis

Cette compétence fournit des stratégies complètes pour tester les workflows Temporal en Python avec pytest, le saut de temps et le mocking.

Points forts

  • Couverture de plusieurs types de tests (unitaire, intégration, rejeu)
  • Utilisation du temps accéléré pour des tests rapides
  • Intégration native avec pytest et les fixtures asynchrones
  • Ressources progressives pour différents scénarios

Limites

  • Nécessite une bonne connaissance de l'écosystème Temporal
  • Focalisé uniquement sur Python, pas d'autres langages
  • La mise en place locale peut être complexe pour les débutants
Quand l'utiliser

Utilisez cette compétence lorsque vous développez des workflows Temporal et que vous avez besoin de tests fiables et rapides avec pytest.

Quand l'éviter

Ne l'utilisez pas pour des projets sans Temporal ou pour des tests simples ne nécessitant pas de saut de temps ou de mocking avancé.

Analyse de sécurité

Sûr
Score qualité85/100

This skill provides guidance and code examples for testing Temporal workflows using pytest. It does not instruct any destructive or exfiltrating actions, nor does it involve executing commands that could compromise security.

Aucun point d'attention détecté

Exemples

Unit test a workflow with time-skipping
Write a pytest unit test for a Temporal workflow using WorkflowEnvironment with time-skipping, following the best practices from temporal-python-testing.
Mock activities in integration test
Set up an integration test for a Temporal workflow that uses mocked activities, including error injection and signal/query testing.
Set up local Temporal development environment
Configure a local Temporal development environment with Docker Compose, pytest, and coverage tools for testing workflows.

name: temporal-python-testing description: "Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal wor..." risk: unknown source: rootcastle-rei

Temporal Python Testing Strategies

Comprehensive testing approaches for Temporal workflows using pytest, progressive disclosure resources for specific testing scenarios.

Do not use this skill when

  • The task is unrelated to temporal python testing strategies
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Use this skill when

  • Unit testing workflows - Fast tests with time-skipping
  • Integration testing - Workflows with mocked activities
  • Replay testing - Validate determinism against production histories
  • Local development - Set up Temporal server and pytest
  • CI/CD integration - Automated testing pipelines
  • Coverage strategies - Achieve ≥80% test coverage

Testing Philosophy

Recommended Approach (Source: docs.temporal.io/develop/python/testing-suite):

  • Write majority as integration tests
  • Use pytest with async fixtures
  • Time-skipping enables fast feedback (month-long workflows → seconds)
  • Mock activities to isolate workflow logic
  • Validate determinism with replay testing

Three Test Types:

  1. Unit: Workflows with time-skipping, activities with ActivityEnvironment
  2. Integration: Workers with mocked activities
  3. End-to-end: Full Temporal server with real activities (use sparingly)

Available Resources

This skill provides detailed guidance through progressive disclosure. Load specific resources based on your testing needs:

Unit Testing Resources

File: resources/unit-testing.md When to load: Testing individual workflows or activities in isolation Contains:

  • WorkflowEnvironment with time-skipping
  • ActivityEnvironment for activity testing
  • Fast execution of long-running workflows
  • Manual time advancement patterns
  • pytest fixtures and patterns

Integration Testing Resources

File: resources/integration-testing.md When to load: Testing workflows with mocked external dependencies Contains:

  • Activity mocking strategies
  • Error injection patterns
  • Multi-activity workflow testing
  • Signal and query testing
  • Coverage strategies

Replay Testing Resources

File: resources/replay-testing.md When to load: Validating determinism or deploying workflow changes Contains:

  • Determinism validation
  • Production history replay
  • CI/CD integration patterns
  • Version compatibility testing

Local Development Resources

File: resources/local-setup.md When to load: Setting up development environment Contains:

  • Docker Compose configuration
  • pytest setup and configuration
  • Coverage tool integration
  • Development workflow

Quick Start Guide

Basic Workflow Test

import pytest
from temporalio.testing import WorkflowEnvironment
from temporalio.worker import Worker

@pytest.fixture
async def workflow_env():
    env = await WorkflowEnvironment.start_time_skipping()
    yield env
    await env.shutdown()

@pytest.mark.asyncio
async def test_workflow(workflow_env):
    async with Worker(
        workflow_env.client,
        task_queue="test-queue",
        workflows=[YourWorkflow],
        activities=[your_activity],
    ):
        result = await workflow_env.client.execute_workflow(
            YourWorkflow.run,
            args,
            id="test-wf-id",
            task_queue="test-queue",
        )
        assert result == expected

Basic Activity Test

from temporalio.testing import ActivityEnvironment

async def test_activity():
    env = ActivityEnvironment()
    result = await env.run(your_activity, "test-input")
    assert result == expected_output

Coverage Targets

Recommended Coverage (Source: docs.temporal.io best practices):

  • Workflows: ≥80% logic coverage
  • Activities: ≥80% logic coverage
  • Integration: Critical paths with mocked activities
  • Replay: All workflow versions before deployment

Key Testing Principles

  1. Time-Skipping - Month-long workflows test in seconds
  2. Mock Activities - Isolate workflow logic from external dependencies
  3. Replay Testing - Validate determinism before deployment
  4. High Coverage - ≥80% target for production workflows
  5. Fast Feedback - Unit tests run in milliseconds

How to Use Resources

Load specific resource when needed:

  • "Show me unit testing patterns" → Load resources/unit-testing.md
  • "How do I mock activities?" → Load resources/integration-testing.md
  • "Setup local Temporal server" → Load resources/local-setup.md
  • "Validate determinism" → Load resources/replay-testing.md

Additional References

  • Python SDK Testing: docs.temporal.io/develop/python/testing-suite
  • Testing Patterns: github.com/temporalio/temporal/blob/main/docs/development/testing.md
  • Python Samples: github.com/temporalio/samples-python

🏰 Rei Skills — Curated by Rootcastle Engineering & Innovation | Batuhan Ayrıbaş
Engineering Beyond Boundaries | admin@rootcastle.com

Skills similaires