Back to catalog / Developer tools
Temporal Python testing: separate deterministic workflows from activities
Cover workflow time-skipping, activity failure policy, and history replay compatibility.
Skills
Use the Temporal Python SDK test environment in pytest with a test clock instead of real waiting. Inject fake activities to validate workflow decisions and timer branches. Test activity timeouts, bounded retries, exception classification, and cancellation separately; keep I/O outside deterministic workflow code. Replay fixed histories after workflow changes to check compatibility. Use an isolated namespace/credential for integration tests. Report SDK versions, replay results, and external dependencies not simulated.
Permissions
Prerequisites
- For deterministic Temporal Python workflow/activity tests, time-skipping, and history replay.
- Needs workflow/activity definitions, test dependencies, and an isolated Temporal test environment.
Permissions
- May add tests and mock/fake activities without changing workflow behavior from production.
- Use SDK test environments; do not connect integration tests to a production namespace.
Limitations
Test workflow determinism separately from activity retry/timeout/cancellation; replay real or deterministic histories.
Pinned upstream source
- Repository
- wshobson/agents
- File path
- plugins/backend-development/skills/temporal-python-testing/SKILL.md
- Pinned commit
46891e7e60da0e52baf1050b7b6391b64e84c6d9- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Temporal Python SDK test environment · pytest time-skipping · Workflow replay
Main topic
Take a coding Agent change from context to verification