temporalio / sdk-go / 6287105222
61%

DEFAULT BRANCH: master
Ran
Jobs 2
Files 95
Run time 3s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 72.282% (-0.006%) from 72.288%
6287105222

push

github

web-flow 
Expose SetContinuedAsNewRunID in the TestWorkflowEnvironment (#1246)

* Export SetContinuedAsNewRunID in the TestWorkflowEnvironment

When building some workflows ("actors" like ones are a good example),
you sometimes want to be able to distinguish when a workflow is starting
and when it's being continued as new. This allows you to execute
different behavior like restoring some state from an external system.

One way to check if your current workflow execution has been continued
as new is to inspect the workflow info ContinuedAsNewRunID field. When
it's set, then you now you are not starting fresh.

When testing such workflows though, you may want to test behavior only
after a first ContinueAsNew call. The easiest way to do that is to
setup the test environment to fill up the workflow info
ContinuedAsNewRunID field.

This is what this commit is doing, it extends the
TestWorkflowEnvironment to expose a SetContinuedExecutionID field to an
arbitrary value.

This way in workflow unit tests, we can skip the code paths we don't
care about and don't resort to mocking activities and child workflows
for nothing leading to easier to implement and easier to read tests.

* Renamed SetContinuedAsNewRunID to SetContinuedExecutionRunID

Let's be consistent with the workflow info field name.

Co-authored-by: Chad Retz <chad.retz@gmail.com>

---------

Co-authored-by: Chad Retz <chad.retz@gmail.com>

14225 of 19680 relevant lines covered (72.28%)

23458.26 hits per line

Jobs
ID Job ID Ran Files Coverage
1 6287105222.1 0
72.18
 GitHub Action Run
2 6287105222.2 0
72.23
 GitHub Action Run
Source Files on build 6287105222
Detailed source file information is not available for this build.