Skip to main content

Test suites

The Testing section of the Temporal Application development guide describes the frameworks that facilitate Workflow and integration testing.

In the context of Temporal, you can create these types of automated tests:

  • End-to-end: Running a Temporal Server and Worker with all its Workflows and Activities; starting and interacting with Workflows from a Client.
  • Integration: Anything between end-to-end and unit testing.
    • Running Activities with mocked Context and other SDK imports (and usually network requests).
    • Running Workers with mock Activities, and using a Client to start Workflows.
    • Running Workflows with mocked SDK imports.
  • Unit: Running a piece of Workflow or Activity code (a function or method) and mocking any code it calls.

We generally recommend writing the majority of your tests as integration tests.

Because the test server supports skipping time, use the test server for both end-to-end and integration tests with Workers.

Testing Activities

An Activity can be tested with a mock Activity environment, which provides a way to mock the Activity context, listen to Heartbeats, and cancel the Activity. This behavior allows you to test the Activity in isolation by calling it directly, without needing to create a Worker to run the Activity.

Testing Workflows

How to mock Activities

Mock the Activity invocation when unit testing your Workflows.

When integration testing Workflows with a Worker, you can mock Activities by providing mock Activity implementations to the Worker.

RoadRunner config

To mock an Activity in PHP, use RoadRunner Key-Value storage and add the following lines to your tests/.rr.test.yaml file.

# tests/.rr.test.yaml
driver: memory
interval: 10

If you want to be able to mock Activities, use WorkerFactory from the Temporal\Testing Namespace in your PHP Worker:

// worker.test.php
use Temporal\Testing\WorkerFactory;

$factory = WorkerFactory::create();
$worker = $factory->newWorker();


Then, in your tests to mock an Activity, use theActivityMocker class.

Assume we have the following Activity:

#[ActivityInterface(prefix: "SimpleActivity.")]
interface SimpleActivityInterface
public function doSomething(string $input): string;

To mock it in the test, you can do this:

final class SimpleWorkflowTestCase extends TestCase
private WorkflowClient $workflowClient;
private ActivityMocker $activityMocks;

protected function setUp(): void
$this->workflowClient = new WorkflowClient(ServiceClient::create('localhost:7233'));
$this->activityMocks = new ActivityMocker();


protected function tearDown(): void

public function testWorkflowReturnsUpperCasedInput(): void
$this->activityMocks->expectCompletion('SimpleActivity.doSomething', 'world');
$workflow = $this->workflowClient->newWorkflowStub(SimpleWorkflow::class);
$run = $this->workflowClient->start($workflow, 'hello');
$this->assertSame('world', $run->getResult('string'));

In the preceding test case, we do the following:

  1. Instantiate ActivityMocker in the setUp() method of the test.
  2. Clear the cache after each test in tearDown().
  3. Mock an Activity call to return a string world.

To mock a failure, use the expectFailure() method:

$this->activityMocks->expectFailure('SimpleActivity.echo', new \LogicException('something went wrong'));

How to skip time

Some long-running Workflows can persist for months or even years. Implementing the test framework allows your Workflow code to skip time and complete your tests in seconds rather than the Workflow's specified amount.

For example, if you have a Workflow sleep for a day, or have an Activity failure with a long retry interval, you don't need to wait the entire length of the sleep period to test whether the sleep function works. Instead, test the logic that happens after the sleep by skipping forward in time and complete your tests in a timely manner.

The test framework included in most SDKs is an in-memory implementation of Temporal Server that supports skipping time. Time is a global property of an instance of TestWorkflowEnvironment: skipping time (either automatically or manually) applies to all currently running tests. If you need different time behaviors for different tests, run your tests in a series or with separate instances of the test server. For example, you could run all tests with automatic time skipping in parallel, and then all tests with manual time skipping in series, and then all tests without time skipping in parallel.

Set up time skipping

Learn to set up the time-skipping test framework in the SDK of your choice.

  1. In the tests folder, create bootstrap.php with the following contents:

require __DIR__ . '/../vendor/autoload.php';

use Temporal\Testing\Environment;

$environment = Environment::create();
register_shutdown_function(fn () => $environment->stop());

If you don't want to run the test server with all of your tests, you can add a condition to start a test only if the RUN_TEMPORAL_TEST_SERVER environment variable is present:

if (getenv('RUN_TEMPORAL_TEST_SERVER') !== false) {
$environment = Environment::create();
$environment->start('./rr serve -c .rr.silent.yaml --workflow-id tests');
register_shutdown_function(fn() => $environment->stop());
  1. Add bootstrap.php and the TEMPORAL_ADDRESS environment variable to phpunit.xml:
<phpunit xmlns:xsi=""
<env name="TEMPORAL_ADDRESS" value="" />
  1. Add the test server executable to .gitignore:

How to Replay a Workflow Execution

Replay recreates the exact state of a Workflow Execution. You can replay a Workflow from the beginning of its Event History.

Replay succeeds only if the Workflow Definition is compatible with the provided history from a deterministic point of view.

When you test changes to your Workflow Definitions, we recommend doing the following as part of your CI checks:

  1. Determine which Workflow Types or Task Queues (or both) will be targeted by the Worker code under test.
  2. Download the Event Histories of a representative set of recent open and closed Workflows from each Task Queue, either programmatically using the SDK client or via the Temporal CLI.
  3. Run the Event Histories through replay.
  4. Fail CI if any error is encountered during replay.

The following are examples of fetching and replaying Event Histories:

To replay Workflow Executions, use the \Temporal\Testing\Replay\WorkflowReplayer class.

In the following example, Event Histories are fetching from the Temporal, and then replayed. If the Workflow is non-deterministic, a NonDeterministicWorkflowException will be thrown. Note that this requires Advanced Visibility to be enabled.

* We assume you already have a WorkflowClient and WorkflowReplayer in scope.
* @var \Temporal\Client\WorkflowClientInterface $workflowClient
* @var \Temporal\Testing\Replay\WorkflowReplayer $replayer

// Find all workflow executions of type "MyWorkflow" and task queue "MyTaskQueue".
$executions = $workflowClient->listWorkflowExecutions(
"WorkflowType='MyWorkflow' AND TaskQueue='MyTaskQueue'"

// Replay each workflow execution.
foreach ($executions as $executionInfo) {
try {
workflowType: $executionInfo->type->name,
execution: $executionInfo->execution,
} catch (\Temporal\Testing\Replay\Exception\ReplayerException $e) {
// Handle a replay error.

In the next example, an Event History is loaded from a JSON file, and the maximum number of replayed Events is limited to 42.

workflowType: 'MyWorkflow',
path: 'history.json',
lastEventId: 42, // optional

You can download a Workflow History using PHP, and then replay it from a memorized History object:

$history = $this->workflowClient->getWorkflowHistory(
execution: $run->getExecution(),

(new WorkflowReplayer())->replayHistory($history);