
Temporal Python Testing
Write pytest tests for Temporal Python workflows, activities, and replay checks
- Repository
- wshobson/agents
- Stars
- 42,095
- Licence
- MIT
- Files
- 5 files
What it does
When installed, the agent can help you test Temporal workflows written in Python. It knows the recommended pattern of using pytest with time-skipping so long-running workflows finish in seconds, mocking activities to isolate workflow logic, and replaying production histories to catch non-deterministic changes before deployment. It also loads reference notes on local Temporal server and Docker Compose setup, and on coverage tooling.
Great for
- Python developers building Temporal workflows who want a test suite
- Teams adding replay tests to check workflow changes before deploying
- Engineers debugging a failing Temporal workflow test
Skip it if
- Projects that do not use Temporal (the guidance only applies to Temporal workflows and activities)
- Teams using Temporal from languages other than Python, since the examples and fixtures are Python-specific
Try asking
- “Write pytest unit tests with time-skipping for my Temporal workflow”
- “How do I mock activities in my Temporal integration tests?”
- “Set up a local Temporal server with Docker Compose for pytest”
- “Help me set up replay testing to validate determinism before deploying a workflow change”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 5 original files, the MIT licence and an attribution note.
temporal-python-testing.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip temporal-python-testing.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip temporal-python-testing.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Name the specific scenario (unit, integration, replay, or local setup) so the agent loads the matching resource file.
- Share your workflow and activity code so the agent can tailor fixtures and mocks rather than giving generic examples.
- Check the generated test code against the current temporalio SDK version, since API names can change between releases.
What's inside
- resources/integration-testing.md
- resources/local-setup.md
- resources/replay-testing.md
- resources/unit-testing.md
- SKILL.md
Redistributed unmodified from wshobson/agents under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.