Describe the bugTestWorkflowEnvironments with custom interceptors don't seem to execute them on child workflows at the moment. I can see the ExecuteWorkflow hook of my interceptor being called for the tested main workflow, but if that workflow calls workflow.ExecuteChildWorkflow internally, the interceptor's ExecuteWorkflow hook isn't called in the context of the child workflow.
In production code, I can observe how when calling ExecuteChildWorkflow the identically-named interceptor method is called and then once the child workflow was scheduled, the interceptor's ExecuteWorkflow is called in the context of the child workflow.
Describe the bug
TestWorkflowEnvironment
s with custom interceptors don't seem to execute them on child workflows at the moment. I can see theExecuteWorkflow
hook of my interceptor being called for the tested main workflow, but if that workflow callsworkflow.ExecuteChildWorkflow
internally, the interceptor'sExecuteWorkflow
hook isn't called in the context of the child workflow.In production code, I can observe how when calling
ExecuteChildWorkflow
the identically-named interceptor method is called and then once the child workflow was scheduled, the interceptor'sExecuteWorkflow
is called in the context of the child workflow.To Reproduce Is the issue reproducible? Yes
Steps to reproduce the behavior:
cadence_test.go
from this Gist to a file.go test -v . -run=TestInterceptorTestSuite
start Interceptor.ExecuteWorkflow "child"
andend Interceptor.ExecuteWorkflow "child"
.Expected behavior Workflow Interceptors'
ExecuteWorkflow
method is also invoked for child-workflows.Additional context