← Back to Skills Marketplace
wu-uk

temporal-python-testing

by wu-uk · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ✓ Security Clean
78
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install fix-build-agentops-temporal-python-testing
Description
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development s...
README (SKILL.md)

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:

  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
Usage Guidance
This is a coherent, instruction-only guide for testing Temporal Python workflows. Before using it: 1) Review any example scripts (especially scripts/export_histories.py and CI examples) — they show connecting to a production Temporal endpoint and exporting workflow histories, which can contain sensitive data; only run these if you have explicit permission and proper credentials. 2) Do not run examples that target production from an untrusted environment; secure exported .pb files and logs. 3) The documents contain small example bugs/typos (e.g., missing imports like 'workflow' in health_check.py, a truncated CI cleanup command), so treat the code as examples to adapt rather than copy-paste. 4) Verify Docker images and dependencies come from official sources (e.g., temporalio/*, postgres) before pulling. If you need higher assurance, request the author/source repository or a signed release before running scripts that interact with production.
Capability Tags
cryptocan-make-purchases
Capability Assessment
Purpose & Capability
Name/description (Temporal Python testing) match the provided instructions and resource files: unit, integration, replay, and local setup guidance. Examples and CI patterns are coherent with testing and replay use-cases.
Instruction Scope
Instructions include legitimately sensitive operations for replay testing: connecting to a production Temporal endpoint and exporting workflow histories. Those steps are within the stated purpose (replay/determinism testing) but they entail handling potentially sensitive data and require production access — the guide doesn't provide or request credentials, so users must supply and protect them.
Install Mechanism
Instruction-only skill with no install spec and no code files to be written or installed by the platform. Lowest-risk install profile.
Credentials
The skill declares no required environment variables or credentials, which is consistent for an instructional guide. However example scripts connect to 'production.temporal.io:7233' and call client.list_workflows / fetch_history; those operations require production access/credentials in practice. The absence of declared creds is not malicious but users should be aware they must provide appropriate credentials and guard exported history files.
Persistence & Privilege
always is false, no install actions, and the skill does not request persistent privileges or try to modify other skills or system-wide settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install fix-build-agentops-temporal-python-testing
  3. After installation, invoke the skill by name or use /fix-build-agentops-temporal-python-testing
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Bulk publish from all-task-skills-dedup
Metadata
Slug fix-build-agentops-temporal-python-testing
Version 0.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is temporal-python-testing?

Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development s... It is an AI Agent Skill for Claude Code / OpenClaw, with 78 downloads so far.

How do I install temporal-python-testing?

Run "/install fix-build-agentops-temporal-python-testing" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is temporal-python-testing free?

Yes, temporal-python-testing is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does temporal-python-testing support?

temporal-python-testing is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created temporal-python-testing?

It is built and maintained by wu-uk (@wu-uk); the current version is v0.1.0.

💬 Comments