temporal-python-testing
wshobson/agents
Test Temporal workflows with pytest, time-skipping, and mocking strategies.
What is temporal-python-testing?
Comprehensive testing approaches for Temporal Python workflows using pytest, time-skipping, and activity mocking. Use this skill when implementing unit tests, integration tests, replay tests, or setting up local Temporal development environments.
- Unit test workflows with time-skipping for fast feedback on long-running processes
- Integration test workflows with mocked activities to isolate workflow logic
- Replay test against production histories to validate determinism before deployment
- Mock activities and inject errors to test error handling paths
- Set up local Temporal server with Docker Compose and pytest fixtures
- Achieve ≥80% test coverage for workflows and activities
How to install temporal-python-testing
npx skills add https://github.com/wshobson/agents --skill temporal-python-testing- Python 3.7+
- temporalio Python SDK installed
- pytest and pytest-asyncio
- Docker and Docker Compose (for local Temporal server setup)
How to use temporal-python-testing
- 1.Install the skill using the provided npx command
- 2.Review the testing philosophy section to understand recommended approaches
- 3.Load unit-testing.md resource for testing individual workflows and activities
- 4.Load integration-testing.md resource for mocking activities and testing error paths
- 5.Load replay-testing.md resource for validating determinism before deployment
- 6.Load local-setup.md resource to configure Docker Compose and pytest
- 7.Run tests with pytest and aim for ≥80% coverage on workflows and activities
Use cases
- Testing individual workflows in isolation with WorkflowEnvironment and time-skipping
- Testing workflows with mocked external dependencies and error injection
- Validating workflow determinism against production event histories before deploying changes
- Setting up CI/CD automated testing pipelines for Temporal workflows
- Debugging test failures and coverage gaps in workflow implementations
- Backend engineers implementing Temporal workflows
- QA engineers building automated test suites
- DevOps engineers integrating Temporal testing into CI/CD pipelines
- Developers debugging workflow determinism issues
temporal-python-testing FAQ
Unit tests use WorkflowEnvironment with time-skipping to test workflows/activities in isolation (fast). Integration tests use Workers with mocked activities to test workflow logic with dependencies. End-to-end tests run against a full Temporal server with real activities (slow, use sparingly).
Time-skipping allows WorkflowEnvironment to advance time manually instead of waiting real time. This lets you test month-long workflows in seconds, providing fast feedback during development.
Use integration testing patterns with mocked activity implementations. Replace real activities with test doubles that return predetermined results or inject errors to test error handling paths.
Replay testing executes a workflow against its production event history to validate determinism. Use it before deploying workflow changes to ensure the new code produces the same results as the original.
Aim for ≥80% logic coverage on both workflows and activities. Include critical integration paths with mocked activities and replay test all workflow versions before production deployment.
Full instructions (SKILL.md)
Source of truth, from wshobson/agents.
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 workflow tests or debugging test failures.
Temporal Python Testing Strategies
Comprehensive testing approaches for Temporal workflows using pytest, progressive disclosure resources for specific testing scenarios.
When to Use This Skill
- 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
Related skills
More from wshobson/agents and the wider catalog.

terraform-module-library
Build reusable Terraform modules for AWS, Azure, GCP, and OCI following infrastructure-as-code best practices.

threat-mitigation-mapping
Map threats to security controls and mitigations for effective defense planning.

trace-to-training-data
Convert graded evaluation traces into SFT examples and DPO preference pairs for model training.

track-management
Create and manage Conductor tracks—logical work units for features, bugs, and refactors.

turborepo-caching
Configure Turborepo for efficient monorepo builds with local and remote caching.

typescript-advanced-types
Master TypeScript's advanced type system: generics, conditional types, mapped types, and utility types for type-safe applications.