You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After adding in caching for the Workflow Ids we may want to add in consideration of this to the RenderTester so that the ids of any children that are not used (since they are passed in via expectWorkflow) don't have their ids cached (or at least do so harmlessly).
Use case, we had a testRender where the Workflow-under-test had child workflows passed in as mocks. These mocks had cachedIdentifier set and accessed even though they shouldn't be used at all by the RenderTester.
The text was updated successfully, but these errors were encountered:
steve-the-edwards
changed the title
Account for cachedWorkflowIdentifier in RenderTester
Account for cached WorkflowIdentifier in RenderTester
Mar 20, 2023
After adding in caching for the Workflow Ids we may want to add in consideration of this to the RenderTester so that the ids of any children that are not used (since they are passed in via
expectWorkflow
) don't have their ids cached (or at least do so harmlessly).Use case, we had a
testRender
where the Workflow-under-test had child workflows passed in as mocks. These mocks hadcachedIdentifier
set and accessed even though they shouldn't be used at all by the RenderTester.The text was updated successfully, but these errors were encountered: