The Temporal Go client library provides a test framework to facilitate testing workflow implementations. The framework is suited for implementing unit tests as well as functional tests of the workflow logic.
The following code implements unit tests for the
To run unit tests, we first define a "test suite" struct that absorbs both the
basic suite functionality from testify
suite.Suite and the suite functionality from the Temporal test framework via
testsuite.WorkflowTestSuite. Because every test in this test suite will test our workflow, we
add a property to our struct to hold an instance of the test environment. This allows us to initialize
the test environment in a setup method. For testing workflows, we use a
Next, we implement a
SetupTest method to setup a new test environment before each test. Doing so
ensures that each test runs in its own isolated sandbox. We also implement an
where we assert that all mocks we set up were indeed called by invoking
Finally, we create a regular test function recognized by "go test" and pass the struct to
A Simple Test
The most simple test case we can write is to have the test environment execute the workflow and then evaluate the results.
s.env.ExecuteWorkflow(...) executes the workflow logic and any invoked activities inside the
test process. The first parameter of
s.env.ExecuteWorkflow(...) contains the workflow functions,
and any subsequent parameters contain values for custom input parameters declared by the workflow
Note that unless the activity invocations are mocked or activity implementation replaced (see Activity mocking and overriding), the test environment will execute the actual activity code including any calls to outside services.
After executing the workflow in the above example, we assert that the workflow ran through completion
via the call to
s.env.IsWorkflowComplete(). We also assert that no errors were returned by asserting
on the return value of
s.env.GetWorkflowError(). If our workflow returned a value, we could have
retrieved that value via a call to
s.env.GetWorkflowResult(&value) and had additional asserts on that
Activity mocking and overriding
When running unit tests on workflows, we want to test the workflow logic in isolation. Additionally, we want to inject activity errors during our test runs. The test framework provides two mechanisms that support these scenarios: activity mocking and activity overriding. Both of these mechanisms allow you to change the behavior of activities invoked by your workflow without the need to modify the actual workflow code.
Let's take a look at a test that simulates a test that fails via the "activity mocking" mechanism.
This test simulates the execution of the activity
SimpleActivity that is invoked by our workflow
SimpleWorkflow returning an error. We accomplish this by setting up a mock on the test environment
SimpleActivity that returns an error.
With the mock set up we can now execute the workflow via the s.env.ExecuteWorkflow(...) method and assert that the workflow completed successfully and returned the expected error.
Simply mocking the execution to return a desired value or error is a pretty powerful mechanism to isolate workflow logic. However, sometimes we want to replace the activity with an alternate implementation to support a more complex test scenario. Let's assume we want to validate that the activity gets called with the correct parameters.
In this example, we provide a function implementation as the parameter to
Return. This allows us to
provide an alternate implementation for the activity
SimpleActivity. The framework will execute this
function whenever the activity is invoked and pass on the return value from the function as the result
of the activity invocation. Additionally, the framework will validate that the signature of the “mock”
function matches the signature of the original activity function.
Since this can be an entire function, there is no limitation as to what we can do here. In this example, we assert that the “value” param has the same content as the value param we passed to the workflow.