Habilidades temporal-python-testing
📦

temporal-python-testing

Baixo Risco ⚙️ Comandos externos

Master Temporal Python Workflow Testing

Também disponível em: wshobson

Testing Temporal workflows is complex due to time-dependent operations and distributed execution. This skill provides proven pytest patterns with time-skipping, activity mocking, and replay testing to achieve reliable test coverage.

Suporta: Claude Codex Code(CC)
🥉 72 Bronze
1

Baixar o ZIP da skill

2

Upload no Claude

Vá em Configurações → Capacidades → Skills → Upload skill

3

Ative e comece a usar

Testar

A utilizar "temporal-python-testing". Test a workflow with a 7-day approval timeout

Resultado esperado:

  • Workflow test completes in 50ms using time-skipping mode
  • All approval path branches tested with parameterized inputs
  • Coverage report shows 92% workflow logic coverage

A utilizar "temporal-python-testing". Replay test against 50 production histories

Resultado esperado:

  • 48 workflows replayed successfully - deterministic
  • 2 workflows failed - non-deterministic random number usage detected
  • Recommendation: Replace random module with workflow.random()

Auditoria de Segurança

Baixo Risco
v1 • 2/25/2026

Static analyzer detected 140 patterns flagged as security concerns, but all are false positives from Markdown documentation containing Python code examples. The 'Ruby/shell backtick execution' patterns are Python code fences in markdown. URLs are localhost development references. Network, filesystem, and cryptographic findings are documentation examples, not executable code. Safe for publication as educational content.

5
Arquivos analisados
1,975
Linhas analisadas
2
achados
1
Total de auditorias
Problemas de Baixo Risco (1)
resources/local-setup.md:58-76resources/local-setup.md:372
Documentation Contains Shell Command Examples
Markdown documentation includes shell command examples for Docker and debugging (docker-compose, lsof). These are educational examples in code blocks, not executable code within the skill.

Fatores de risco

⚙️ Comandos externos (16)
SKILL.md:22 SKILL.md:55 SKILL.md:67 SKILL.md:79 SKILL.md:90 SKILL.md:103-129 SKILL.md:129-133 SKILL.md:133-140 SKILL.md:140-163 SKILL.md:163-164 SKILL.md:164-165 SKILL.md:165-166 resources/integration-testing.md:11-418 resources/local-setup.md:9-546 resources/replay-testing.md:27-453 resources/unit-testing.md:11-281
Auditado por: claude

Pontuação de qualidade

38
Arquitetura
100
Manutenibilidade
87
Conteúdo
50
Comunidade
88
Segurança
91
Conformidade com especificações

O Que Você Pode Construir

Backend Developer Testing Workflows

A Python developer needs to test Temporal workflows that include month-long sleep durations. Use this skill to implement time-skipping tests that complete in milliseconds, achieving fast feedback during development.

QA Engineer Validating Determinism

A QA engineer must verify workflow changes do not break existing executions. Use this skill to set up replay testing that validates determinism against production workflow histories before deployment.

DevOps Engineer Setting Up CI/CD

A DevOps engineer needs automated testing for Temporal workflows in CI/CD pipelines. Use this skill to integrate pytest with coverage tracking and automated history export for regression testing.

Tente Estes Prompts

Basic Workflow Test Setup 
Help me write a pytest test for a Temporal workflow that includes a 30-day sleep. Show me how to use WorkflowEnvironment with time-skipping so the test completes instantly.
Mock External Dependencies 
I have a workflow that calls payment and inventory APIs through activities. Show me how to mock these activities in integration tests to test the workflow orchestration logic without calling real external services.
Validate Workflow Determinism 
I modified my workflow code and need to verify it is backward-compatible with running workflows. Show me how to export production workflow histories and replay them with the new code to validate determinism.
CI/CD Integration for Testing 
Set up a GitHub Actions workflow that runs pytest tests for Temporal workflows, including Docker Compose for the Temporal server, coverage reporting with 80% threshold, and automated history export for replay testing.

Melhores Práticas

  • Use time-skipping WorkflowEnvironment for all unit tests to achieve fast feedback - month-long workflows should test in milliseconds
  • Mock all external dependencies in integration tests - never call real APIs during test execution to ensure reliability and speed
  • Run replay tests against production histories before every deployment - this validates determinism and prevents breaking running workflows

Evitar

  • Using datetime.now() or random module directly in workflows - these break determinism and cause replay failures
  • Writing end-to-end tests with real Temporal server for every test - this is slow and brittle; prefer time-skipping unit tests
  • Skipping replay testing before deployment - workflow code changes may break existing executions without proper validation

Perguntas Frequentes

Why do my replay tests fail after refactoring workflow code?
Replay tests fail when code changes alter the sequence of workflow decisions. Ensure you use workflow.now() instead of datetime.now() and workflow.random() instead of random module. Avoid changing activity IDs or conditional branching logic that affects which activities are scheduled.
How do I test workflows with long sleep durations without waiting?
Use WorkflowEnvironment.start_time_skipping() which automatically advances time when workflows sleep. A 30-day sleep completes instantly in tests. For manual control, use env.sleep(timedelta(hours=1)) to advance time by specific amounts.
Should I test activities with ActivityEnvironment or in a Worker?
Use ActivityEnvironment for isolated unit tests of activity logic - it is faster and does not require a Temporal server. Test activities within a Worker when you need to verify workflow-activity integration, retry behavior, or heartbeat handling.
How often should I export production workflow histories for replay testing?
Export histories weekly or after major workflow changes. Keep at least 100 representative histories covering different execution paths. Automate export with a scheduled job that queries recent completed workflows and saves histories to your test fixtures directory.
What coverage target should I aim for with Temporal workflows?
Target 80% or higher coverage for workflow logic and critical activities. Use pytest-cov with --cov-fail-under=80 to enforce the threshold in CI. Focus on testing all branching paths, error scenarios, and retry behavior rather than achieving 100% line coverage.
Can I use this skill with Claude, Codex, or Claude Code?
Yes, this skill is compatible with Claude, Codex, and Claude Code. All three AI assistants can help implement the testing patterns, write pytest tests, set up Docker Compose configurations, and integrate replay testing into CI/CD pipelines.

Detalhes do Desenvolvedor

Autor

sickn33

Licença

MIT

Repositório

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/temporal-python-testing

Referência

main

Estrutura de arquivos

📁 resources/

📄 integration-testing.md

📄 local-setup.md

📄 replay-testing.md

📄 unit-testing.md

📄 SKILL.md