Automated summary
Testing guide for Python Temporal workflows using pytest, covering unit tests with time-skipping, integration tests with mocked activities, and replay testing.
Strengths
- Covers all three test levels (unit, integration, end-to-end) with concrete pytest examples
- Explains time-skipping that turns month-long workflows into seconds-long tests
- Offers progressive disclosure through per-scenario resource files
- Addresses determinism validation via replay of production histories
Limitations
- The main content is mostly an index; details live in resources/ files not included here
- Does not cover non-Python workflows or TypeScript/Go SDKs
- Assumes prior familiarity with Temporal and pytest-asyncio
Reach for it when writing or structuring pytest suites for Python Temporal workflows and activities.
Avoid it for tasks unrelated to Temporal or for testing async systems that don't use Temporal.
Security analysis
SafeThe skill contains only Temporal Python testing guidance and pytest examples. It does not request or instruct destructive commands, credential access, network exfiltration, obfuscated payloads, or safety-disabling behavior.
No concerns found
How this analysis is madeExamples
Write a pytest test for my Temporal workflow that uses WorkflowEnvironment.start_time_skipping so a 30-day timer resolves instantly.Show me how to test a Temporal workflow with mocked activities and inject failures to verify my error-handling branch.Help me add a replay test that validates my workflow changes against a production history JSON in CI.name: temporal-python-testing description: "Comprehensive testing approaches for Temporal workflows using pytest, progressive disclosure resources for specific testing scenarios." risk: unknown source: community date_added: "2026-02-27"
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:
- Unit: Workflows with time-skipping, activities with ActivityEnvironment
- Integration: Workers with mocked activities
- 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
- Time-Skipping - Month-long workflows test in seconds
- Mock Activities - Isolate workflow logic from external dependencies
- Replay Testing - Validate determinism before deployment
- High Coverage - ≥80% target for production workflows
- 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
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/temporal-python-testing-mrx3xyrn/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/temporal-python-testing-mrx3xyrn' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/temporal-python-testing-mrx3xyrn/download' --output '.skill-downloads/temporal-python-testing-mrx3xyrn/SKILL.md.part' && mv '.skill-downloads/temporal-python-testing-mrx3xyrn/SKILL.md.part' '.skill-downloads/temporal-python-testing-mrx3xyrn/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/temporal-python-testing-mrx3xyrn/SKILL.md' && test -s '.skill-downloads/temporal-python-testing-mrx3xyrn/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/temporal-python-testing' && cp -R '.skill-downloads/temporal-python-testing-mrx3xyrn' '.claude/skills/temporal-python-testing'Cursor
test -f '.skill-downloads/temporal-python-testing-mrx3xyrn/SKILL.md' && test -s '.skill-downloads/temporal-python-testing-mrx3xyrn/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/temporal-python-testing' && cp -R '.skill-downloads/temporal-python-testing-mrx3xyrn' '.cursor/skills/temporal-python-testing'Codex
test -f '.skill-downloads/temporal-python-testing-mrx3xyrn/SKILL.md' && test -s '.skill-downloads/temporal-python-testing-mrx3xyrn/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/temporal-python-testing' && cp -R '.skill-downloads/temporal-python-testing-mrx3xyrn' '.agents/skills/temporal-python-testing'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/temporal-python-testing-mrx3xyrn'openskills read 'temporal-python-testing-mrx3xyrn'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/temporal-python-testing-mrx3xyrn/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.